The phase change
From spring it's obvious the way these things only ever are afterward: December was the month coding changed for good, and I felt it as the keystrokes leaving my hands
From here in spring it's obvious, the way these things only ever are afterward: December was when coding changed for good.
Three frontier models landed in a few weeks — Opus 4.5, Gemini 3, GPT-5.2 — and somewhere in that pile the coding agents stopped being demos you show people and became something you hand the work to. Opus 4.5 was the one for me. It was the first model to clear 80% on the standard coding benchmark, and it could hold a single task for the better part of a working day without losing the thread.
Karpathy called it a phase change, and the word is right: agents crossing from brittle to tenacious, taking an end-to-end job — set up the server, wire the deploy, fix what breaks — and grinding it to done with barely a nudge. The lead on Claude Code mentioned that for a whole month, every line he'd added to the tool had been written by the tool itself. Read that twice.
What it felt like from inside my own work: the keystrokes left my hands. I stopped writing code and started describing outcomes and reviewing what came back. The Opus releases kept coming after that, each a notch up, weeks apart. I'm burning through my Claude Code Max credits faster than I can think of things worth building — and that is the whole tell. The machine isn't the bottleneck now. I am. My taste, my judgment, my nerve about what deserves to exist.
Thirty years of building, and the rarest skill in the room is no longer typing. It's knowing what's worth making.