Harness Engineering

In short: AI coding agents are changing the status of code. In mature agentic workflows, code is no longer only written by humans; it is repeatedly generated, tested, corrected, and selected by an optimization loop. That makes tests look like loss functions, production failures look like generalization failures, architecture look like inductive bias, and harness engineering look like optimizer design. Introduction: A Shift We Have Not Yet Named Precisely Over the past eighteen months, software development has undergone a quiet but forceful restructuring. Tools such as Cursor, Claude Code, and Codex are pushing us away from the old workflow of “humans write code, machines assist with completion” toward something structurally different: humans describe intent, define constraints, and provide feedback, while agents repeatedly generate, run, and revise code until some convergence condition is met. Most industry commentary still frames this shift in productivity terms: “AI makes us write code N times faster.” That framing misses a more basic ontological question: in this new workflow, what has happened to the nature of code itself? ...

Last year, the AI coding conversation had a clear hero: Spec-Driven Development (SDD). This year, people are talking about harness engineering instead. That looks like a trend. It is a signal that the bottleneck moved. SDD is about making intent explicit so an agent can start in the right direction. Harness engineering is about building the environment, constraints, feedback, and governance that keep the agent on track after the 50th or 100th step. If you have ever watched an agent do impressive work for 20 minutes and then slowly degrade into a mess, you already understand why the vocabulary changed. TL;DR SDD helps agents start correctly Harness engineering keeps them correct over time The bottleneck moved from generation to verification Long-running reliability is now the real problem The SDD moment: why it caught on Early “agentic coding” had a predictable failure mode. You’d say: “Add user auth,” or “Make a dashboard,” or “Fix onboarding.” The agent would produce something that looked plausible. It might even compile. Then you’d try to use it, and realize half the work was guesswork. ...