David Yanacek on why it was never about coding
A senior engineer's framing of agentic coding as a shift from line-by-line programming to designing, operating, and continuously improving a software-development factory.
Logged at IST: 2026-09-22 09:32 IST
What it is: David Yanacek's argument that agentic coding is not an identity crisis for programmers because the job was never just typing code.
Gist: Yanacek frames software work as designing and improving a factory: intent becomes requirements and design, code moves through tests, reviews, merge gates, deployment, triage, rollback, and operational feedback. Coding agents make this more explicit. They are useful loops, but only when the surrounding system has deterministic checks, fast local feedback, sandbox boundaries, and well-timed human decisions.
His point is that the engineer's leverage moves from babysitting an agent's every tool call to nurturing the factory around it. That includes codifying process in docs and configuration, adding review and test agents, improving steering when agents get stuck, and using each manual intervention as evidence that the factory can be tuned.
The identity shift is less “AI writes code, humans review forever” and more “humans own direction, standards, architecture, quality gates, and process improvement.” It is a practical complement to the broader agentic-software-factory idea: execution gets cheaper, so direction, verification, and taste matter more.
Newsletter angle: Useful agents/developer-tools piece on the programmer as factory designer/operator rather than typist.