Terence Tao wrote up building apps with coding agents, and it hit #1 on HN

A Fields Medalist treating Claude Code as a Tuesday tool. That's the signal, and it's bigger than any model release this week.

Terence Tao posted a July 11 essay documenting how he rebuilds and creates small apps using modern AI coding agents. It hit #1 on Hacker News with 441 points and 130 comments (Terence Tao's Blog). Not a paper about AI. Not a take on whether AI is good or bad. A practitioner walkthrough from one of the sharpest mathematical minds alive, treating agents as ordinary tooling for getting real things done.

Why this matters more than a benchmark: adoption by serious technical practitioners is the hard part. Benchmarks measure capability. They don't measure whether people who could do it themselves choose to hand it to an agent. When Tao does it, and documents it carefully, and 441 HN readers argue about the details, agent-assisted coding has crossed from novelty into professional method. The people who'd be most justified in dismissing it aren't dismissing it.

I've felt this shift in my own work over the past year. The question stopped being "can the agent write this code" and became "is it faster to orchestrate the agent or type it myself." My design background is why I can tell the difference. I read the output for craft, not just whether it compiles. That's the skill that's actually scarce now, and watching a mathematician develop the same instinct for evaluating agent output tells me it generalizes past software.

What builders should do: read the essay for the workflow, not the endorsement. The valuable part is how a rigorous thinker structures the problem before handing it off, what he keeps for himself, and where he catches the agent being wrong. That's the orchestration skill, and it's learnable. Watch how he decides what to delegate. The delegation boundary is the whole game.

This also connects to the reality-check story below. Tao builds small apps successfully. The terminal benchmark says agents fail at 85% of long-horizon tasks. Both true. The delegation boundary is exactly the line between them.