Fetching from the wire…
Top 5 · 2026-04-14 · source-backed
Steve Yegge shared a conversation with a Google tech director of 20 years. The breakdown: 20% agentic power users. 20% outright refusers. 60% still in basic chat mode. Simon Willison surfaced the thread, and Yegge's punchline was devastating: Google's internal AI adoption is "comparable to John Deere."
Google. The company that invented the transformer architecture. The company with Gemini, TPUs, and more AI PhDs per square foot than anywhere on earth. Their own engineers are using AI the same way farmers use it. Two out of ten go deep. Two refuse entirely. The other six treat it like a fancy autocomplete.
Yegge flagged something I haven't seen anyone else catch: there's been an industry-wide 18+ month hiring freeze. No external hires are arriving to flag how far behind internal practices have fallen. The people who've been inside Google for years don't know what they don't know, and nobody new is coming in to tell them.
This maps to what I see in my own work. The gap between someone who uses Claude Code as a chat assistant and someone who runs it as an agent with skills, worktrees, and CLAUDE.md context engineering is enormous. Same tool. Completely different output. The 60% in chat mode aren't lazy. They just haven't been shown what agentic usage looks like, and their organizations aren't structured to teach them.
The Stanford AI Index confirms this at macro scale: 88% organizational AI adoption, but "adoption" covers everything from "we have a ChatGPT license" to "agents run our SOC." The number is meaningless without depth metrics.
What to do about it: Audit your own team honestly. What percentage are in chat mode? Agentic power users? Refusers? The answer will surprise you. Then invest in the middle 60%. That's where the ROI is. One engineer going from chat to agentic usage is worth more than buying another AI tool.
Each link below shares sources, entities, or timing with this story.
The same man whose framework a model regression destroyed also published the most aggressive prediction of the week, and the tension between those two facts is the whole argument. "The Shape of Things to Come, Part 1: The Continuous Thunderdome" argues traditional CI/CD collap...
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...
I've been telling people for months that the agent code I review is *correct and awful*. Correct in the sense that it compiles, passes the tests, does the thing. Awful in the sense that a 400-line function does the work of 80, the same helper exists three times under different...
Anthropic released Claude Fable 5.1 on September 1. Claude Code v2.1.257 made it the default Fable model at 17:53 UTC that day, with a 1M-token context window, $10 per million input tokens, $50 per million output, and $0.25 per million on cache reads (claude-code CHANGELOG). B...
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...
Uber handed Claude Code and Cursor to 5,000 engineers, built an internal leaderboard ranking teams by AI usage, and hit 84-95% monthly adoption. Per-engineer cost ran $500 to $2,000 a month. The 2026 AI budget, all $3.4B of it, was gone by April. COO Andrew Macdonald said the...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.