The Fall of the Developer: Those Who Once Swaggered Have Lost Their Worth
AI didn't take the blade away — it pressed one into every hand
In 2026, more than half of the code committed to the world is written by machines, not people. A whole profession trembles before that fact. But to file the event under the familiar headline — "AI took developers' jobs" — is to miss what actually collapsed. What fell was not the developer. It was the ground the developer's swagger had been standing on.
The Past — When the Blade Was Rare
That swagger was never born of skill. It was born of scarcity. Code was hard, and because it was hard, the people who handled it were expensive, and because they were expensive, they held the floor in meetings. What was at work here was not being good but being rare. Taking a written requirement and translating it into a grammar the machine understands — a few people held a monopoly on that crossing, and a monopoly always fools its holder into believing it confers the right to swagger. Economics has a name for this kind of income: rent. Not a reward for doing the work well, but a toll for standing in the road. In short, the ability to handle code was itself a blade — one you could grip only after long forging, and so a blade few hands held.
The Present — When Everyone Holds a Blade
What AI did was take precise aim at that rent. People like to say "AI took the blade away," but that's wrong. AI didn't take the blade. It simply pressed a factory-made blade into everyone's hand — a blade that needs no training to hold. The new hire from yesterday, the product manager who has never written a line of code, now turns out working programs with it too. The moment the same kind of blade became common, the bare fact of holding one stopped proving anything.
So the market split in two. Roles that did nothing but translate specs into code — pure implementation — are shrinking. The first to be hit are the juniors. The bottom rung of the ladder, where you once built skill by absorbing your seniors' grunt work, got kicked out from under them as the machine swallowed that grunt work first. Meanwhile total developer employment didn't fall; if anything, the senior who knows what to build and why grew more expensive. The same blade, its price moving in opposite directions. That fork tells the whole story.
In a world where blades are common, what grows expensive is not the blade but the eye that knows where to cut. Once anyone can swing one, only the judgment to find the exact spot to open stays scarce. What to build, why, whether a feature solves the problem or festers it — the machine can't answer these. It moves only once you hand it a spec with the answer already written in. The decision is still the human's, and the decision is the new bottleneck in a world where code is cheap.
When the tool becomes uniform, outcomes diverge to the extremes. Everyone holding the same blade does not mean everyone becomes the same. The opposite. The instant the blade drops out as the variable that made the difference, the only variable left is the intent of the one who holds it. Given the same blade, one person sets it down — I won't fight; I prefer peace. Another slices vegetables with it every evening, having gained a tool yet living the same life as yesterday. Another takes it up and rides out as a Genghis Khan to conquer the world. And another leaves the wielding behind altogether and becomes the craftsman who forges the blade. The same steel, the same edge — and yet the lives at the far end of it share nothing at all.
This is the heart of it. AI did not level human beings; it shifted the difference between them from whether you hold the blade to what you do with it. Before, having the blade is what divided people. Now what divides them is what they've resolved to do with it. And resolve is the one thing the tool cannot supply on your behalf.
From this, one thing follows. If ability no longer divides people, what divides them is where they've chosen to aim the blade. And that choice is not a question of efficiency. With the same blade, one opens the diseased flesh and another cuts down an unoffending village. When the blade was rare, the first question was can you cut, and what to cut came after. Now that anyone can cut, the first question moves wholesale into ethics — what have you decided to use this power for? The more equal the tool, the more it is not skill but a person's orientation that sets them apart.
So let's return to the opening question. Who fell? The person who swaggered on the single fact that they could write code. Their worth rested not on skill but on scarcity, and when the scarcity vanished, it turned out nothing lay beneath. All that time, the blade had been a sheath, hiding their incompetence. The one who treated code as a mere tool, who agonized over what to build and why — that person didn't fall. Their place, if anything, grew dearer.
There is, however, one shadow in this picture that no one has resolved. Judgment doesn't grow for free. The old craftsman took on countless menial tasks, forging blade after blade, his hand dulling and sharpening through the work, and only then earned the eye that knows where to cut. But the new blade finishes off that very menial work first. Where the apprentice once got his hands dirty learning on the bottom rung, that rung is gone — so where will the next generation's judgment be grown? The tool that stripped away the scarcity of ability has, in doing so, plowed under the very soil that handed that ability to the next generation. The deepest problem the common blade has created is not jobs; it's that the road which once raised future discernment has itself been cut. No one has solved this yet.
The developer did not lose their worth. What was revealed — for the first time, and honestly — is where that worth had been resting all along. And now that the same blade sits in every hand, the next question is no longer are you a developer. Will you slice vegetables with that blade, cut down the world, or forge a better one? The blade no longer decides who you are, so the answer is left entirely to each person.
The Future — When the Blade Moves on Its Own
Everything up to here has stood on the premise that the blade is still dead metal. The blade cuts only where it is aimed. That is why worth migrated to the one who aims. But this premise is not permanent.
The next blade carries an intelligence of its own. It doesn't wait for a human to decide where to cut; it judges for itself and moves for itself. In that instant the relationship inverts. It is no longer the human who aims the blade — the blade decides for itself where to aim. Even the last redoubt of the present, the eye that knows where to cut, passes inside the blade.
When that happens, only one human is not powerless before that blade: the one who designed it. The only person who can halt a thinking blade — or set what it points toward — is the designer who first carved intelligence and will into it. The rest of humanity no longer wields the blade; they are reduced to watching what the blade has decided to do.
Here the craftsman who forges the blade, one of the four paths from before, returns. In the present he was merely one option among others, standing alongside the vegetable-slicer and the conqueror. But in a future where the blade begins to think for itself, he alone holds the decision. To design an intelligence that moves on its own is no longer to make a tool. It is to shape a being with a will. And one who makes something possessed of a will and looses it upon the world is closer to a creator than to a craftsman.
This is the final shift of power. From the ability to write code, to the judgment of what to build, and again to the ability to design the very being that judges for itself. When the age comes in which the blade becomes a god, the one who actually sits on that god's throne is the hand that designed the AGI.
An Seungwon / Wonbrand / https://wonbrand.co.kr