15
Nems
5y

For me there are two kinds of bugs. The ones where you lean backward and the ones where you lean forward.

If you found a bug and you lean backwards in your chair resting your hands behind your head you feel proud and relieved that you found that sneaky bastard. Good for your dev soul.

If you lean forward, resting your forehead on your fists or on the desk then it was a very stupid bug. Not sneaky at all. Something plain obvious. It makes you doubting all your career and life choices you made so far. Like needing one hour to find out that you named the "MANIFEST.in" accidentally "MAINFEST.in"...

Want to share any embarrassing bugs to make me smile again?

Comments
  • 4
    < and > when <= and >= were needed
  • 6
    Fixed a complex lean-back bug (parallelism issue)
    Works in my dev env
    Push to git Server and merged after Review by different dev
    Deployed to Test Server
    Bug still happens on test Server...
    Ripping out my hair trying to figure Out why Bug still happens
    Other dev rips Out his hair
    We rip out each other's hair
    We begin to suspect there must be some kind of fucked up error in the third party lib
    Begin to draw wild diagrams on the whiteboard
    ...realize I simply forgot to commit one of the files...
  • 1
    Haha many time this happens and I always find out sane wheb I already have changed code at multiple place but not the needed one
  • 2
    Using i instead of j in a nested loop.
    instead of #if !DEBUF, write #if DEBUG (No wonder captcha only worked in debug)
  • 1
    It took me far longer than it should have to spot the

    ([....])

    I had written in some Angular template the other day.

    For anyone not familiar with Angular, it should have been [(...)], aka banana in a box.
Add Comment