Every few weeks someone posts the same screenshot: an AI writing a whole app from a one-line prompt, captioned "devs are cooked." And every few weeks I close my laptop, open a real client codebase, and remember that the prompt was never the hard part.
I use AI every day. It drafts my boilerplate, explains unfamiliar stack traces, and rubber-ducks my architecture decisions at 1am. I'd genuinely hate to give it up. But I've stopped believing it's coming for me, and I want to explain why — without the comforting hand-waving you usually get from people who feel threatened.
The honest part first
AI is going to replace a lot of tasks. It already has. The hour I used to spend wiring up a CRUD form, writing regex, or translating an error message into a Stack Overflow search — gone. If your job is only those tasks, that's a real problem, and pretending otherwise helps no one.
So when I say "AI won't replace humans," I don't mean nothing changes. I mean the thing being automated is the typing, not the deciding.
The hard part of software was never the code
Most of my actual work isn't writing code. It's figuring out what a client means when they say "it should just sync automatically." It's noticing that the integration they asked for was quietly deprecated two versions ago and choosing a different path. It's deciding which 20% of the feature request is worth building this month.
An AI can write the sync code beautifully. It cannot sit in the room, read the half-finished sentence, the budget anxiety, and the thing the client didn't say, and decide that the right move is to talk them out of the feature entirely. That's not a prompt. That's judgment, and judgment is built from consequences you've personally lived through.
Someone has to be accountable
Here's the part I think gets skipped. When the migration corrupts production data at 2am, the AI doesn't get the call. I do. When the architecture choice locks the company into a year of pain, no model is in the retro explaining itself.
Software runs on trust and accountability, and you can't delegate accountability to something that can't be held responsible. As long as that's true, there's a human in the loop — not as a babysitter, but as the person who owns the outcome.
We've done this before
We are spectacularly bad at remembering this, but every tool that was going to "replace programmers" instead made programmers more valuable:
- Compilers were going to make assembly experts obsolete. They created a thousand times more programmers.
- High-level languages, IDEs, autocomplete, Stack Overflow, open-source frameworks — each one removed grunt work, and demand for developers went up, not down. When you make something cheaper to produce, you usually get more of it, not less. Cheaper software means more software gets built — more startups, more internal tools, more ambitious projects that weren't worth the cost before. That demand has to land on someone who can steer the machine.
What I think actually happens
AI doesn't replace the developer. It raises the floor and moves the bottleneck. When generating code is nearly free, the scarce skill becomes knowing what's worth generating, spotting when the confident output is quietly wrong, and integrating it into a messy real system that has history, constraints, and humans attached.
In other words: the job gets less about production and more about taste, verification, and judgment. We become pickier. The developers who struggle won't be the ones who refused to use AI — they'll be the ones who used it without ever developing the judgment to know when it's lying to them.
So, am I worried?
Not about being replaced. I'm worried about people who think the skill is "prompting" instead of "deciding." I'm worried about juniors who never build the intuition because the AI always answered first. Those are real problems worth talking about.
But the human in software? We're not going anywhere. We just get a very fast, very confident, occasionally hallucinating intern who never sleeps — and someone still has to decide whether to trust what it hands us.
That someone is the job.
What's your take — is "AI replaces tasks, not people" too optimistic, or about right? I'd genuinely like to hear where you think this breaks down.
Top comments (8)
calibrating what to hand off is harder than the actual handoff - kept delegating judgment calls along with the boilerplate. still working out where the proxy ends.
Even from the perspective of a beginner vibe coder, I agree. My intern (Claude Code) writes code based on briefs written by the CEO (Claude on claude.ai) after brainstorming together, but the hardest and most demanding part is still the human's review. I can't review the code (I'm not capable of it), so I have to check the results in the field, often after harmless damage has already happened :-D but the human check, where you take responsibility, is fundamental.
And AI is a tool for programmers that in my opinion they should learn to use like any new tool that comes along in any field. Let me try a comparison with my own work: I started drawing by hand, and when the first CAD software came along, despite many people's skepticism, I adopted it right away. But if you didn't know how to design before, you couldn't design with CAD either. CAD is just a tool that speeds things up and helps, but human skill remains fundamental, and I believe the same goes for AI for you programmers.
translated by Claude
This is the part people underestimate. AI raises the floor for output, so taste and review get more important, not less. The bottleneck moves from making something to deciding what is actually worth keeping.
The "raising the floor" point is the one I keep coming back to. I have no formal development background and I build full-stack web apps entirely with AI assistance. Which sounds like it proves the "devs are cooked" argument until you realize how much of my time is still spent on things no model handles well — figuring out why the app works locally but crashes on Railway, deciding which feature to cut so the demo doesn't look half-finished, or just choosing whether a product idea is worth building at all before I spend a weekend on it.
The AI writes the code. I still make every decision that matters. And honestly the decisions got harder, not easier, because now I can build things that used to require months of learning — which means I have to be a lot more deliberate about which things are worth building.
The "junior who never builds intuition" concern is real though. I wonder about this for myself sometimes.
This mirrors what I've seen integrating AI APIs into real products. The models get better every quarter, but the real value comes from how you design the human-AI handoff. We found that presenting AI suggestions as draft options rather than final answers keeps users engaged and more critical — which ironically leads to better outcomes than fully automated pipelines.
AI won't replace professionals.
Professionals using AI will replace professionals who don't.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.