• dan1101@lemm.ee
    link
    fedilink
    arrow-up
    38
    ·
    9 months ago

    I’m the last person I would have suspected, but I was looking for me all the time!

    • XTornado@lemmy.ml
      link
      fedilink
      arrow-up
      5
      ·
      9 months ago

      It could work if it was some important code that caused some castrophic event… and the end he sees he actually changed those lines…that ended up causing the thing to fail.

  • masterspace@lemmy.ca
    link
    fedilink
    English
    arrow-up
    18
    ·
    edit-2
    9 months ago

    In my experience coming up through Windows desktop development, more than half the time the murderer was a closed source, compiled, dependency, that only behaved oddly in extremely specific circumstances.

    • yesdogishere@kbin.social
      link
      fedilink
      arrow-up
      1
      arrow-down
      3
      ·
      edit-2
      9 months ago

      the worst part for me, was not only being unable to estimate the time to solve the bug, i found that often the problem was in syntax or shadings of understanding on how functions or bracket syntax worked. i could refer to all the biggest programming books off the shelves, and the answers they provided would not work. Programming is one of those professions where answers lay with people who had busted their brains or lucked it trying to make it work, and had collected over many years, snippets of code which they knew worked. If you weren’t chummy with these people, you would never find the answer. This isn’t really a worthwhile profession. Unlike physics, or maths, where there is an independent answer governed by forces outside of an individual human, programming is a profession which inherently depends on learning errors from another human. It’s a pointless profession and gets you nowhere in life at the end. Sadly. (Unlike say law, or accounting or physics, where at old age, you know more about the world around you.)

  • jetsetdorito@lemm.ee
    link
    fedilink
    arrow-up
    11
    ·
    9 months ago

    I spent like 2 hours on a really time sensitive bug today, I even resorted to asking chat gpt, the solution was… doing what I did in the first 5 minutes a second time… 😭

  • yesdogishere@kbin.social
    link
    fedilink
    arrow-up
    11
    arrow-down
    1
    ·
    9 months ago

    the worst part about debugging for me, is i have no idea how long it will be before i can solve a single bug. it could take me 2 hours, 1 day, a week, no idea. Because i have no idea where the bug came from. I have ti go through increasingly more detailed testing cycles. Then devise more laborious testing cycles. This is why i chose not to work as a programmer. In other professions, I know i can give an estimate of the time taken to complete the task. Debugging? No real idea. What if the boss says finish it by tomorrow? I might be there all night.

    • Venat0r@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      9 months ago

      What if the boss says finish it by tomorrow? I might be there all night.

      Looking for a new job I hope…

  • hiyayakk0@lemmy.ml
    link
    fedilink
    arrow-up
    9
    ·
    9 months ago

    To get the nuance right, it’s like if you lived your very normal average every day life, day after day, never intentionally hurting anyone or anything. Then found out you murdered someone weeks/months/years after the fact and were asked how you did it.

  • TDCN@feddit.dk
    link
    fedilink
    arrow-up
    4
    ·
    9 months ago

    It’s more like this: it feels like you are both the detective, the victim and the murdere