Fetching from the wire…
Public story · 2026-07-19 · high
Nik Suresh says inflated AI productivity claims survive because vendor executives can't contradict clients without risking their contracts.
Why now: Willison linked Suresh's essay on July 19, pushing an incentive-structure argument past the usual AI hype cycle takes.
An executive wrote a $2 billion company's AI strategy without ever using an AI tool, according to an essay by Nik Suresh that Simon Willison linked on July 19.
Suresh's sharper point isn't about that one executive. It's about how AI productivity numbers get inflated in the first place. Customer-side executives report 100x gains. Vendor executives who know better can't contradict them, because doing so torches contract credibility and, often, their own jobs. Nobody in that chain is lying exactly. Nobody has an incentive to correct the number either. The inflation just perpetuates itself through people protecting their positions.
The detail that lands hardest: engineers rewriting working codebases in different languages, not because the rewrite serves the product, but "to keep my job." That's a narrower failure than an executive skipping the tools, and a more useful one. It's what AI adoption pressure looks like when people get rewarded for appearing productive instead of being productive.
Every 100x productivity claim you hear secondhand is probably a number nobody checked, because nobody in the reporting chain gets rewarded for checking it. Vendors profit from the inflated figure holding. Customers who reported it don't want to walk it back. Engineers under pressure to show AI usage will optimize for looking busy with it over shipping with it. Watch whether the gap between reported and audited AI gains widens before anyone with the incentive to close it shows up.
Willison linked the essay on July 19, giving an incentive-structure argument more reach than a typical hot take about AI hype.
Each link below shares sources, entities, or timing with this story.
Simon Willison highlighted Sophie Alpert's short internal policy on AI-assisted writing, whose load-bearing rule is accountability: "You must stand behind every idea and every sentence in your docs," because you can't excuse a bad passage by blaming the LLM, and doing so waste...
Steve Yegge built a Go-based multi-agent orchestrator called Gas Town that ran 20 to 30 parallel Claude Code instances. It worked. Then it didn't. His postmortem, surfaced by Simon Willison on August 4, is blunt: Gas Town "fell apart at the seams with Opus 4.7. Up through 4.6...
The Pragmatic Engineer published a deep read on August 25 of Inspect, the coding agent Ramp built instead of standardizing on Claude Code or Cursor. The numbers: Inspect authors 75% of Ramp's merged PRs, 90% of PRs in its own repository, passed 1 million total sessions in July...
Satya Nadella said companies routing everything through a single proprietary lab may not survive. His argument: you hand that lab your most sensitive business context, and the lab can turn it against you as a competitor. His prescription is an orchestration layer — keep the ha...
Willison launched datasette-apps (0.1a2) on June 18, hosting self-contained HTML+JS apps in a sandboxed iframe that run SQL against your data, read-only by default. He frames it as "Claude Artifacts reimagined for Datasette," artifacts backed by a JSON API to a relational data...
On July 16 there was a wave of backlash calling the Bun Zig→Rust rewrite unreviewed AI slop. On July 19, Simon Willison went and checked. (Simon Willison) Jarred Sumner claimed Claude Code v2.1.181 and later ship the Rust port. Willison verified it independently rather than ta...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.