Werner Vogels published his annual predictions in late November 2023. I want to take one of them seriously — not as a cheerleader, but as a sceptic who agrees with the conclusion while finding the framing too comfortable.

The third prediction: AI assistants will redefine developer productivity.

He is right. That is the frustrating part.

The 2023 Stack Overflow Developer Survey found that 70 percent of respondents were already using or planning to use AI tools in their workflow. Vogels cites this as evidence of momentum. It is also evidence of a category error: “planning to use” and “using” describe very different relationships with a tool. I plan to exercise in the mornings.

The actual claim worth interrogating is this: “The AI assistants on the horizon will not only understand and write code, they will be tireless collaborators and teachers.”

Tireless is accurate. Tireless, and utterly untrustworthy.

We have been handed a new kind of colleague: one who never complains, never sleeps, and will confidently produce a plausible-looking answer whether or not it is correct. The collaboration model Vogels describes — “no task will exhaust their energy, and they’ll never grow impatient explaining a concept or redoing work” — is real. What it omits is the corollary: they will also never admit they do not know. The patience is not wisdom. It is compliance.

Vogels buries the important hedge in a single sentence: “Make no mistake, developers will still need to plan and evaluate outputs.” That sentence is doing an enormous amount of work. Planning and evaluation are not minor overhead. They are the entire professional competence that distinguishes a developer from a prompt-issuer. If the AI takes on the generation and the developer retains only the review, we have not rebalanced the workload — we have moved the cognitive burden up a level, where errors are harder to spot and more expensive to miss.

The role-blurring prediction is where I feel the most ambivalence. “The lines between product managers, front- and back-end engineers, DBAs, UI/UX designers, DevOps engineers, and architects will blur.” That is almost certainly true. It is also describing a world where no one is specifically responsible for anything. Lines between roles are not just division of labour. They are accountability structures. Blurring them is also blurring the answer to “whose fault was this.”

None of this contradicts the central prediction. AI assistants will redefine developer productivity. They already have, in my own work — writing boilerplate I would have resented, explaining a codebase I have just joined, sketching tests I can then harden. These are genuine productivity gains.

But Vogels is the CTO of Amazon. Amazon sells Bedrock. Amazon sells CodeWhisperer. Amazon sells the compute that runs inference at scale. Reading his predictions with that in mind does not make them wrong. It does make the optimism legible as something other than disinterested analysis.

The piece is not dishonest. It is conveniently incomplete.

What is missing is any account of verification. The prediction describes the capability ceiling. It says very little about the floor: the minimum set of practices that make AI-assisted development trustworthy enough to stake a production system on. Tests. Specification. Review. The unglamorous infrastructure of professional software.

An assistant that writes unit tests is only useful if I already know what those tests should prove. An assistant that suggests the “optimal infrastructure for your projects” is only useful if I can evaluate whether the suggestion is optimal or merely plausible. Of the 70 percent using or planning to use AI tools — I would like to know how many have invested equally in the review practices that close the loop.

Vogels says the coming years will see engineering teams “more productive, develop higher quality systems, and shorten software release lifecycles.” He is probably right. The teams that will get there are the ones who treat the AI as a generator, not an oracle — and who have built the verification infrastructure to tell the difference. The rest will ship fast and confidently.

That, too, is a redefinition of developer productivity. Just not the one anyone is advertising.