• saplyng@kbin.social
    link
    fedilink
    arrow-up
    6
    ·
    1 year ago

    This also applies to coding! And I’m not currently dreading the fact I keep thinking of more and more convoluted solutions to my problem at work at all!

    • physcx@kbin.social
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      The overlap of things tried with logical reasons is far too great for programming. Have you tried speaking to your duck about it?

    • Minion3665@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I have spent the last two days on a networking issue. Certain images weren’t being transmitted over the network, even though they were being generated.

      It turns out that the image generation was actually silently failing because I was missing fonts.

      You’re not alone, we weep together

  • Mo5560@feddit.de
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    My colleague has had problems with his camera. He bought a new cable, started cooling the camera, reinstalled drivers, reinstalled the entire measuring software, anything half-reasonable you can think of.

    Well last week he was sick and another colleague took over his experiments. Turns out the camera works just fine on the 2nd monitor.

    We still have no idea why.

  • douglasg14b@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    Applies to software engineering as well!

    Often the “logical reasons why” are you fooling yourself into thinking you know all the invariants, when you really forgot or misunderstood at least one.