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.
Claude Code supports Bash / Shared entities / Shared topic / What happened next / Tension
Linked by a graph relationship (Claude Code supports Bash); both cover ChatGPT, Claude Code, SOC, Yegge; overlapping topics (agent, claude, same, yegge).
Claude Code uses Opus / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Claude Code uses Opus); both cover Claude Code, Simon Willison, Then, Yegge; reported by the same outlet (simonwillison.net).
Anthropic released Claude Code / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Anthropic released Claude Code); both cover Claude, Claude Code, Simon Willison, Then; reported by the same outlet (simonwillison.net).
Claude Code uses Axios / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Claude Code uses Axios); both cover Claude, Claude Code, ROI, Then; overlapping topics (adoption, claude, have, internal).
Claude Code benchmarked against GPT / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Claude Code benchmarked against GPT); both cover ChatGPT, Google, Same, Then; overlapping topics (agentic, claude, same).
OpenAI acquired Roi / Shared entities / Shared topic / What happened next
Linked by a graph relationship (OpenAI acquired Roi); both cover Claude, Claude Code, Google, Same; overlapping topics (agent, claude, same).
Anthropic released Claude Code / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Anthropic released Claude Code); both cover Claude, Claude Code, ROI, Then; overlapping topics (adoption, agent, claude).
Codex competes with Claude Code / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Codex competes with Claude Code); both cover CLAUDE, Claude Code, Google, Then; overlapping topics (agent, claude, google).