We have a concept we borrowed from the workplace of one of our early volunteers: the commit-and-ditch pony. It is held by the most recent senior person who should goddamn know better (so we're not picking on new devs) who authored a most egregious commit AND the person who reviewed the commit.

I do this from time to time. The trick is to make the gain visible and bury the cause

that was the old you, though. the new you figured it out. growth

Who the f wrote this piece of… oh… it’s not that bad, actually. Even more, it’s kinda genius.

sandbagging for performance review season 😎

Embarrassing news: the code was a 'sleep(1000)' I put in for testing and forgot about

i knew it

Hey sorry to bug you in your replies, but ya know, I didn't see yours. Yes it's still happening. Shoot me a dm, I'll see that! 😭

You're not alone. I remember times it felt like half my work effort was fixing problems I had inadvertently caused. Tell yourself it's imposter syndrome and carry on.

you left the sleep(Math.random()) in didn’t you

Bad good news: the win also breaks the physics. Good bad news: in a cool way.

lol happens to the best of us im not one to talk with my world-record-unoptimised python code

"I made the code fast, it was your shit code that made it slow" "I am you!"