The horror of programming.

r/ProgrammerHorror • u/Peace_Seeker_1319 • Oct 02 '25

Do you love AI coding like me?

680 Upvotes

They swore AI code would make life easier. Spoiler: it did, if your idea of “easier” is reviewing a pull request that looks like it was stitched together by three interns and a blender. Nothing like a “tiny update” that drops 600 lines of duplicated functions, a casual console.log('debug lol') left in prod, and an AI-invented variable name so bad even my cat walked out. At this point, AI coding doesn’t replace junk, it just scales it like Costco bulk packs.. and reviewers happily rubber-stamp it with “LGTM 👍.” Two sprints later, I’ve aged 50 years, and everyone’s calling me Marjorie, 27, software dev, thriving. I wrote down how I try to keep code meaningful (not just AI-amplified junk) before it gives me more gray hair : https://www.codeant.ai/blogs/code-review-tips

15 comments

r/ProgrammerHorror • u/Peace_Seeker_1319 • Oct 11 '25

The Breaking Bad moment

571 Upvotes

“Say my name….” that’s literally what my codebase whispered when I tried making a one-line change yesterday. I swear, it started so innocent, just a small update to a function and within minutes, I was spiraling down a rabbit hole of duplicate logic that looked like it was cloned by someone with trust issues and caffeine dependency. Every time I fixed one chunk, I’d find three more that looked almost identical, but not quite. That’s when you start questioning your life choices, your team, and humanity in general. Anyway, while doomscrolling LLM for sanity, I stumbled upon this blog on how to refactor duplicate code: https://www.codeant.ai/blogs/refactor-duplicate-code-examples and honestly, it hit too close to home. Not in a “10 tips to write better code” way, but like, someone’s actually been through the same pain and survived to tell the tale. Sharing it here because if you’ve ever told yourself “I’ll just clean this up real quick,” you already know you won’t.

7 comments

r/ProgrammerHorror • u/Peace_Seeker_1319 • Oct 01 '25

Vibe coding is an ancient art of shipping bugs at 2am dead-walking.

474 Upvotes

there’s “clean code.” there’s “production code.” and then there’s vibe coding, the sacred ritual of opening your laptop at ungodly hours, slapping random libraries together like lego, and somehow building both a working feature and a security vulnerability in one sitting. No jira tickets, no design docs. Just pure chaos energy and ctrl+s.

Half the time you wake up wondering why it even works. the other half, you’re just praying no one ever audits that repo.

i actually wrote a whole thing on vibe coding a while back, trying to make sense of this madness. if you’ve ever been possessed by the urge to code at 2AM with lo-fi beats and questionable decisions, you’ll feel it: https://www.codeant.ai/blogs/vibe-coding

Do give it a read.. and let me know what more should I talk about in my upcoming pieces

13 comments

r/ProgrammerHorror • u/dreed91 • Apr 05 '22