> Bonus points if it's your own 1 night effort. :-)

Are you really a serious developer/architect/sysadmin/devops/engineer if you haven't muttered "what was this idiot thinking?" about your own code at least once?

It's way better if you leave a place of work, go have a fun career, and come back 15 years later and get assigned some cleanup work. You can't even rant about it.

So much for letting that problem ride for the next sucker...

Or the wonderful week+ bugs where the fix turns out to be a single line. (Especially when it comes down to something that corrupts memory.)

We had this in c++ reading rfid tags. Solution was addig on character: ^

Typical off by on

What you did there. I see i

I spent two weeks once tracking down a kernel scheduler bug.

The fix was to swap two instructions. That was a hard one, hard-won.

Brendan Eich created JavaScript in ten days, and people have been trying to fix it for 27 years.

Hmm, I'm pretty sure it wasn't 1 night, but mostly because there's only so many bugs you can write in a single night.