Vibe Coder Turned Dev

The fresh-faced junior dev who believed the lie that "oncall isn't too bad" has clearly been transformed into a shell of his former self. Those promised "runbooks" for another team's systems? Yeah, they're either wildly outdated or just a single README file saying "good luck!" This is what happens when you're woken up at 3AM by cryptic alerts for systems you've never seen before, while the senior devs who actually built the monstrosity are peacefully sleeping with their phones on silent. The only documentation? A Confluence page last updated in 2019 that just says "TODO: finish documentation".

The pinnacle of technical specifications right here! Nothing says "master prompter" like the incredibly detailed bug report: "the whole app is buggy. Please fix everything." Developers absolutely LOVE these vague instructions that give them zero actionable information. It's like telling a doctor "my body hurts, cure me" and expecting a precise diagnosis. The TypeScript file extension (.tsx) makes it even better - someone's React component is apparently having issues, but good luck figuring out what they are! This is the digital equivalent of pointing at a car and saying "it's broken" without mentioning that it's out of gas.

Ah, corporate wisdom strikes again. Management thinks forcing developers to use cursor-based pagination will give them the energetic Duracell bunny—all that efficiency and power. What they actually get is just Bugs Bunny—endless bugs hopping around the codebase. Nothing says "I don't understand technical decisions" quite like mandating specific implementation details without understanding the consequences. The rabbit hole of debugging goes much deeper than expected.

Content What we say What we mean Horrible hack Horrible hack that I didn't write Temporary workaround Horrible hack that I wrote It's broken There are bugs in your code It has a few issues There are bugs in my code Obscure Someone else's code doesn't have comments Self-documenting My code doesn't have comments That's why it's an awesome language It's my favorite language and it's really easy to do something in it. You're thinking in the wrong mindset It's my favorite language and it's really hard to do something in it. I can read this Perl script I wrote this Perl script I can't read this Perl script I didn't write this Perl script Bad structure Someone else's code is badly organized Complex structure My code is badly organized Bug The absence of a feature I like Out of scope The absence of a feature I don't like Clean solution it works and lunderstand it We need to rewrite it it works but I don't understand it emacs is better than vi It's too peaceful here, let's start a flame war vi is better than emacs It's too peaceful here, let's start a flame war IMHO You are wrong Legacy code It works, but no one knows how XCquit ESCIESCJC I don't know how to quit vi

Content The Giant bug I still don't want to fix Me Fixing a typo in the README

That judgmental stare when someone posts about forgetting a semicolon like it's the end of the world. Sure, ten years ago we'd spend hours debugging only to find a missing semicolon, but modern IDEs highlight that stuff before you even finish the line. It's like panicking about quicksand when you're an adult – turns out it wasn't the massive threat everyone made it out to be.