Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-06-15 · source-backed
Willison published "Why AI Hasn't Replaced Software Engineers, and Won't" (Simon Willison), and it's the cleanest articulation I've read of something I've believed from direct experience. His argument: the real bottlenecks in software work, deciding what to build, verifying correctness, and holding deep system context, are precisely the parts AI coding tools don't automate, even as they get scary good at raw code generation.
I shipped three solo products in the past year using Claude Code daily in my personal projects, and this matches the texture of the work exactly. The code generation stopped being the hard part a while ago. What stayed hard, what stayed mine, was knowing whether the generated thing was actually right, whether it solved the problem worth solving, and whether it fit the system it was joining. The model will happily write 400 lines of confident, well-structured, subtly wrong code. Catching that is the job now.
The takeaway Willison lands on: leverage compounds for engineers who own judgment and verification, not for those who only typed code. That's not a comforting "your job is safe" pat on the head. It's a redistribution. If the value was in your typing speed, the floor dropped out. If the value was in your taste, your ability to verify, your system context, AI is a force multiplier strapped to exactly that.
This is why I keep saying the design background is the engineering advantage and not a side quest. Twenty years of evaluating output for craft, not just correctness, turns out to be the rare skill when the correctness-ish output is suddenly free and infinite. The scarce resource is the human who can look at three plausible solutions and know which one is actually good.
Read this one alongside the cost stories above. DeepSeek and Fusion make generation cheaper. Willison reminds you that cheaper generation raises the value of the part you can't buy by the token. If everyone has access to near-free frontier-adjacent code, your edge is entirely in what you choose to build and your ability to tell good from plausible. Invest your taste there. Don't invest it in being faster at the part the machine already won.
Each link below shares sources, entities, or timing with this story.
Simon Willison uses Claude Code / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Simon Willison uses Claude Code); both cover Claude Code, Simon Willison, Willison; reported by the same outlet (simonwillison.net).
Linked by a graph relationship (Simon Willison uses Claude Code); both cover Claude Code, Simon Willison, Willison; reported by the same outlet (simonwillison.net).
Simon Willison uses Claude Code / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Simon Willison uses Claude Code); both cover Claude Code, Simon Willison, Willison; reported by the same outlet (simonwillison.net).
Simon Willison uses Claude Code / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Simon Willison uses Claude Code); both cover Claude Code, Simon Willison, Willison; reported by the same outlet (simonwillison.net).
Simon Willison uses Claude Code / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Simon Willison uses Claude Code); both cover Claude Code, Simon Willison, Willison; reported by the same outlet (simonwillison.net).
Vercel uses DeepSeek / Shared entities / Same source domain / Shared topic / What happened next / Tension
Linked by a graph relationship (Vercel uses DeepSeek); both cover Simon Willison, Willison; reported by the same outlet (simonwillison.net).
Simon Willison uses Fable / Shared entities / Same source domain / Shared topic / What happened next / Tension
Linked by a graph relationship (Simon Willison uses Fable); both cover Simon Willison, Willison; reported by the same outlet (simonwillison.net).
Simon Willison uses Claude Code / Shared entities / Same source domain / Earlier coverage / Tension
Linked by a graph relationship (Simon Willison uses Claude Code); both cover Claude Code, Simon Willison, Willison; reported by the same outlet (simonwillison.net).