For thirty years, every slow-shipping company had the same alibi: we don’t have enough engineers. Hiring was the constraint. Capacity was the constraint. Implementation was the constraint.
That alibi just expired.
David Heinemeier Hansson — the man who wrote Ruby on Rails, who spent two decades arguing that beautiful hand-chiselled code was the whole point — has not written a single line of the code shipped in his new operating system by hand. Not one. In three months, he merged over a thousand pull requests into it. Three days after release, the plugin marketplace had 330 extensions. He rewrote a Python graphics library into Rust, a language he openly hates, in forty-five minutes, without reading the output. He calls his current state delirium, and he means it as a compliment.
So here is the question that should keep every founder awake: if one person can now do that, why is your team of forty shipping the same four features a quarter it shipped last year?
The answer is not your engineers.
The human in the middle
The most useful thing Hansson says in five hours has nothing to do with code. It is this: to get the 10x, you have to talk to the agent yourself, and you cannot put another human in the middle of that conversation. The bandwidth collapses. A product manager relaying intent to a designer relaying it to an engineer who then prompts the model is three lossy translations of a thing you could have said directly in nine seconds. When you have a PM, two designers, a VP above them and a CTO above them, and everyone needs to be in the shaping process to justify their existence — that, in his words, is where all the productivity goes to die.
Read that again as an org-design statement, because that is what it is.
The scarce resource changed identity
The second thing worth stealing: most companies are not bottlenecked on building. They are bottlenecked on knowing what to build. Hansson’s example is Microsoft — decades of effectively unlimited engineering capacity, and the output speaks for itself. Writing a lot of code has never produced great software. What produces great software is someone with taste deciding what should exist, in what order, for whom. Make a lot of bad ideas real, very fast, and you have simply industrialised being wrong.
Which means the scarce resource in your company just changed identity. It is not engineering hours. It is judgement. Hansson puts it flatly: software is product management. What should it do? Who for? What ships in version one? Those skills were never evenly distributed across your engineers, and now they are the only ones that price.
Where it breaks. He is honest about this, and the failure is instructive. At 37signals they let the designers loose on an existing product with agents. Every individual pull request looked defensible. Taken together, they destroyed the architecture, and humans had to clean it up by hand. Greenfield is where the miracle happens. A large system with years of accumulated decisions still punishes people who cannot see structure. If you are running a real codebase, that distinction is worth more to you than any productivity statistic.
Stop specifying harder
Then the part most managers will get wrong. The instinct, when you hand work to something powerful, is to specify harder — longer briefs, tighter constraints, more rules. That instinct is now actively destructive. Anthropic shrank the system prompt for its newest model by roughly 80% because the model was being damaged by over-prescriptive humans. Hansson’s analogy is the pointy-haired boss who walks in, understands nothing, and starts telling you how to code. You sulk. You do worse work. Why would an agent be different?
The discipline is the opposite of what you were trained on: say the vaguest thing that produces something real, then react to the real thing. Nobody knows what they want until they hold it. That was the whole insight of the agile movement, and agents have finally made it cheap enough to actually practise.
The strategic read
Now the part that matters for anyone building a business rather than a side project.
There is no accumulated advantage here. Hansson’s claim is that if you had spent the last year backpacking, untouched by any of this, you could reach the frontier in two weeks. Nothing compounds. No one is building a lead in tooling. So the moat is not who adopted agents first — it is who is structurally capable of using them, and that is a question about your management layers, not your stack. Incumbents are supertankers tuned for a world that stopped existing. That is the innovator’s dilemma arriving on a schedule measured in months instead of decades.
And the opportunity is smaller and more specific than the AI discourse suggests. The old joke about Microsoft Office was that everyone only uses 5% of it — the catch being that we all use a different 5%. Hansson’s answer to that: build your own 5%. He replaced his writing app in twenty minutes and had abandoned the original within two days. Every internal tool your team tolerates because the good one is too expensive or the vendor won’t build your workflow is now a weekend.
None of this is a prediction. It has already happened; the distribution is just uneven. The companies that will look stupid in eighteen months are not the ones that were late to the models. They are the ones that bought the models, plugged them into an approval chain built for 2015, and then concluded the technology was overhyped.
No comments:
Post a Comment