A survey of 900 plus engineers just said the quiet part out loud. The job is moving from how to build to what to build. Here is the part the survey buried. AI does not lower the risk of building the wrong thing. It raises it. Execution got cheap, so building the wrong thing faster is the new default failure mode.
The orthodoxy, named with the leaderboard
The discourse has one answer to almost everything right now: the bigger model is the edge. More throughput, faster shipping, the next flagship changes everything. Wait for the release. The release is the strategy.
Two headlines in one stretch carried that message. Fortune reported that Anthropic confidentially filed for an IPO at a 965 billion dollar valuation, with Claude Code cited as a main revenue driver. In the same window, Google said at I/O that Gemini 3.5 Pro was on the way, and by mid-June it was still sitting in limited preview, telling people to wait until next month.
A record valuation on one side. A delayed flagship on the other. The leaderboard and the cap table are the story everyone is watching. The assumption underneath both is that the model is the variable that decides who wins.
The data that breaks it
Then the orthodoxy's own audience reported back, and the report does not match the story.
The Pragmatic Engineer survey says it polled 900 plus engineers and sorted AI's effect into three types: builders, shippers, and coasters. The finding is that AI amplifies whatever tendency was already there. It does not level the field. It widens the gap that was already on it.
The shippers are the tell. The survey says they get to production faster, and in the same breath they add tech debt faster and build the wrong things faster. Speed went up. Direction did not. And the line the survey lands on is the one I keep coming back to: the craft is moving from how to build to what to build.
That is the orthodoxy's own readership reporting that the orthodoxy is tuning the wrong variable. The model is not the thing separating the builders from the shippers. The judgment about what to build is.
The thing I have been running for a year
I have been running this inversion in my own work since before the survey caught up to it.
The production line flipped. Execution compressed almost to nothing. The part before execution did not compress at all. So I spend almost no time on the build and almost all of it upstream.
What problem, stated precisely. Who it is for, with real personas built on real data, not a stock "our user." User stories from those personas, where feature X solves problem Y and there is a clear account of how it gets delivered.
Get the feature list, the user stories, and the designs done right, and the development runs about 95 percent smooth. Claude does the build, and the build is close to trivial once the upstream work is real. Get the upstream work wrong, and AI just builds the wrong thing faster and with more confidence. The documentation before the first design file is where the whole thing is won or lost.
Why AI punishes the skip instead of saving you from it
Here is where I want to push back on the dream the tooling sells.
I do not want a faster way to ship the wrong thing. I want to be more sure it is the right thing before a single line of code exists. Those are not the same goal, and AI is very good at the first one while pretending it solved the second.
Think about what slowness used to do for you. When building the wrong thing cost three weeks, the wrongness got caught in the three weeks. You felt the drag. Someone asked the question. The cost of being wrong was paid slowly enough that you could stop before you paid all of it.
Now the wrong thing ships in a day. The slowness that used to catch it is gone. The cost of skipping the upstream work did not disappear with it. It moved downstream, where it is more expensive to fix and harder to see, and it got bigger on the way.
Cheap execution did not remove the tax on building the wrong thing. It just deferred the bill and added interest.
Where the market is putting its money
If this were only my opinion, you could discount it. The market just made the same bet with real money.
SiliconANGLE says a new AI-native services firm, backed by Anthropic and two private-equity backers with a combined sum reported in the billions, acquired an embedded-engineers shop to be its delivery team. The pitch, in their framing: decks and roadmaps do not move a business. Engineers who go into the operation and rebuild the system around what frontier models can now do are what move it.
Read that again. A billion-dollar bet just priced judgment-in-the-room above execution speed. Not the model. Not the deck. The operator who decides what to rebuild and then rebuilds it.
That is the wedge I sit in, at a different scale. The difference is that they need a balance sheet and an acquisition to do across many clients what one operator can do for one client at a time. Same shape of value. They are buying the seat. I am the seat.
The honest limit
I will say the thing the confident version of this post would leave out.
I do not know what is coming with AI in future. The specific upstream method I run today, the personas, the user stories, the documentation pass before the design file, that might change shape entirely as the tools change. I am not going to pretend the method is permanent.
But the bet under the method is one I would make for the next few years without hesitating. The bottleneck moved from execution to judgment, and I do not see it moving back. I would rather be early to that than fast at the wrong thing.
The closer
The model got faster at building. It did not get faster at knowing what to build.
That gap is the whole job now.
