A 25-year software engineer is banned from writing, testing, or reviewing code because his company wants to ship 'AI slop' faster. Time to quit or cash in?
Imagine coding for 25 years. You wrote your first "Hello World" at age 6, lived and breathed software architecture, and then one random Tuesday, management tells you: "Stop coding. Let the machine do it." Suddenly, you're locked out of the codebase, banned from doing the very thing you were hired to do, all to make way for autogenerated AI garbage. Is it time to pack up and leave, or just shut up and collect the paycheck?
The drama started on Reddit when a seasoned dev dropped a bomb about his current existential crisis. He’s been a professional software engineer for nearly 25 years. Coding is his job, his hobby, his whole identity.
But his current company recently caught the generative-AI bug real bad. Apparently, traditional software engineering practices like "Code Review" and "Testing" are just annoying roadblocks preventing them from shipping "AI slop" at lightning speed.
The new company policy? The OP is no longer allowed to write code. No testing. No code reviews. It's basically an extreme sport of 'Merge and Pray'. Burnt out and feeling useless, this senior dev took to the internet to ask for career pivot ideas.
The post blew up with over 900 upvotes, and the developer community rushed in with a mix of cynical pragmatism and top-tier dad jokes:
1. The Pragmatists: Shut up and take the money Users like Keilly and Cresneta dropped the harsh truth: The US job market is an absolute bloodbath right now. If the company wants to pay a senior dev salary to sit on their hands, take the money. Keep your head down, ride out the storm, and don't jump ship without a lifeboat.
2. The Escapists: Let's go chop wood ErnieBernie10 suggested what every dev thinks about during a production outage: "We should start a settlement in the woods... live in harmony and chop wood all day." Of course, VideoGameCookie couldn't resist the pun: "What are we chopping? AlpineJS, RedwoodJS, TimberPHP?" Once a dev, always a dev.
3. The Hardcore Pivot: Where bugs equal death User scandii provided the most solid career advice: Pivot to industries where bad code literally kills people. Think aerospace, medical ventilators, or nuclear energy. These fields are bound by strict legal compliance and safety standards. They absolutely cannot afford the "move fast and ship AI slop" mentality.
4. The Ticking Time Bomb: Run before it blows Others like Krigrim and jameson5555 pointed out the obvious flaw: If no one is reviewing PRs, who is approving this mess? They advised the OP to start interviewing immediately. Get out before the codebase turns into an unmaintainable nightmare of spaghetti code that the OP will inevitably be asked to fix.
Look, the AI hype-train is real, and some management teams are driving it straight off a cliff. AI is a fantastic tool, but entirely removing human testing and review loops is corporate suicide.
So, what’s the takeaway here? First, never tie your entire ego to your employer's tech stack or policies. If management wants to burn the house down while paying you a premium, let them. Second, use this "downtime" wisely. Upskill, build side projects, and silently prep for interviews. The AI bubble will eventually stabilize, and when these companies realize their code is a dumpster fire, they're going to need real human developers to clean it up.
Stay sane out there, folks. And maybe keep a wooden axe handy just in case.
