• XanXic@lemmy.world
    51·
    9 months ago

    This happens so many times. I’m a pretty firm believer in walking away for 15 minutes is a crucial part of the debugging process. It’s just hard sometimes to know when to stop and stop trying shit for a bit.

    Also rubber duck debugging, I’ll talk to my dog but fuck it works so many times. Shes helpful.

    • SpaceNoodle@lemmy.world
      17·
      9 months ago

      I used to talk to the graphic designer next to me. I work from home now, so my wife gets to play the role 24/7.

  • riplin@lemm.eeEnglish
    31·
    9 months ago

    And then you fix the bug, test and it and it still doesn’t work and it turns out you weren’t even calling the function in the first place. I’ve had that happen several times.

  • Ddhuud@lemmy.world
    18·
    9 months ago

    And when you’re wide awake you notice it was a dream, and there’s no “behave” statement in python.

  • teclo@feddit.ukEnglish
    9·
    9 months ago

    My zombie brain is my pair programmer. This happens to me so frequently that it no longer surprises me and I now chill and let my sub conscious work it out.

    • BeigeAgenda@lemmy.ca
      6·
      9 months ago

      Code a bit, think a lot, code some more, sleep on it, get a really good idea in the shower…

  • henfredemars@infosec.pubEnglish
    8·
    9 months ago

    Remember to take care of yourself. Just because you have an idea doesn’t mean you have to test it right this second. You need breaks.

  • Alex@lemmy.ml
    5·
    9 months ago

    This is why I leave a couple of hours break between coding and going to bed. If I don’t I may well sleep but my dreams are full of repeating code that I don’t wake up rested. Any “insights” from the dreams are usually wrong as well ☹️

  • Bappity@lemmy.worldEnglish
    3·
    9 months ago

    this has happened to me after I spent weeks trying to fix a small thing it made me scream