I’ve been a backend dev for about four years, and lately, I feel like I'm attending the funeral of my own profession every single morning at the daily stand-up. I am grieving a job that, technically, still exists. My title hasn't changed, my salary is the same, but the day-to-day reality of what I actually do is completely unrecognizable. We used to be the ones who built things from the ground up. We were engineers. Now, I spend half my day babysitting a machine, acting as a glorified editor for an LLM that hallucinates business logic.
When I first started in this industry, the absolute best part of the job was getting stuck. That sounds masochistic, but anyone who actually likes coding knows exactly what I mean. You'd hit a wall with a weird race condition or a database deadlock. You'd spend hours digging through the official docs, reading obscure GitHub issues, and maybe arguing with a senior dev over Discord about whether we should use Redis or set up a dedicated message queue. And then, finally, you’d get that 'aha' moment. You wrote the fix, you understood exactly why it worked, and you felt like a god. That friction, that deep investigation—that was the whole point of the job.
Now? You paste the stack trace into an AI window. It spits out a patch in two seconds. You glance at it, paste it into your IDE, run the tests, and merge the PR. It works. The Jira ticket gets moved to 'Done'. Management is thrilled because our sprint velocity is off the charts. But my brain feels completely numb. I'm just checking boxes on an endless conveyor belt of autogenerated syntax.
And it’s destroying the way we work together. I used to love code reviews. Now, I spend my days dodging what I call the "AI slop grenade." New devs will just ask Copilot or Claude, get a massive wall of code or a giant prompt response, and just paste it into a PR for you to read. I absolutely refuse to spend my time reviewing something that you didn't even spend the time to read or understand yourself. The whiteboard sessions, the architecture talks, the deep dives into conventions—they are vanishing.
I read a quote the other day that perfectly nails what is happening to us1:
"AI lowers the cost of producing an answer. It does not lower the cost of understanding the consequences."
This is the ticking time bomb of our industry. AI is incredibly good at writing locally optimal code, but it is utterly blind to global architecture. It doesn't know why we chose a specific microservices boundary three years ago. So we end up stitching together thousands of lines of "good enough" code that nobody actually understands.
And that brings me to the liability. The executives love the speed. But when that same autogenerated code causes a silent memory leak, or when an AI-written SQL query does a full table scan and crashes production at 3 AM on a Saturday, the AI isn’t on PagerDuty. I am. I am expected to wake up and debug a 600-line concurrent mess that I didn't write. I am assuming 100% of the technical responsibility for code written by a probabilistic text generator.
Then you go on LinkedIn and see all these tech bros celebrating how coding is dead, how anyone can build a SaaS in a weekend. Honestly, the people celebrating this never actually liked the engineering part to begin with. Prompting a quick web prototype in 30 minutes isn't software engineering. It’s a parlor trick. Knowing how to write a prompt doesn't teach you why your ORM is choking your database when 500 concurrent users hit the server at once.
If a 20-year-old asked me for advice on becoming a backend dev today, honestly? I'd tell them to find another job. I am terrified for the new generation. The entry-level stepping stones are gone. Why hire a junior when an AI can write a CRUD app in ten minutes?
These new devs will never have to wrestle with the raw logic. They will never stare at a syntax error for 30 minutes, feeling like an idiot, only to build the mental compiler that makes them a real engineer. In three years, we are going to have a wave of "seniors" who can answer complex interview questions by prompting Claude, but who won't understand the consequences of a single word they are pasting. They are just tourists in their own codebase. When the real senior devs burn out, who is going to rescue these AI-generated Frankenstein systems when they inevitably collapse?
I'm not an anti-AI purist. It's a crazy powerful tool when I use it to write bash scripts or generate test boilerplate. But being forced to let it write the core business logic is turning us into lazy, apathetic reviewers. Nobody investigates anymore. We are trading the actual joy of the craft for the cheap illusion of speed. We are building faster than ever, but I've never felt more empty doing it.
(And yes I know this was written with AI help, just to reword a bit, as said I'm not an anti-AI, I just don't like Agentic AI and the world we're creating on this)
