Part 1: AI, Rockets, and the Return of Hard Contracts | Essays | Noumena<br>Skip to contentEssays/The Engine Shop<br>The claim you hear everywhere that "AI makes software cheap" is wrong in most of the ways that matter. What AI makes cheap is implementation: the act of turning a decision into working code.

Everything around that act has kept its old price, and so far AI models still haven't delivered "intelligence too cheap to meter" (they meter it quite well, and charge accordingly). Someone still has to decide what the system is supposed to do, define how the pieces fit together, draw the security boundaries, and judge whether the thing that came back actually works. An agent can now write an implementation, rewrite it, produce four alternatives, and throw them all away for relatively little cost. Judgment, taste, and experience still cost what they always cost.

That mismatch is the central economic fact of AI-assisted development. Agents can produce code far faster than humans can meaningfully evaluate it, and most of what they produce will be plausible but mediocre. Some of it will be subtly wrong. Some will solve the local problem while quietly damaging the system around it. And buried in the flood, every so often, will be an implementation better than the one you would have written yourself. The potential is real, but only if we stop treating every generated artifact as a finished piece of work awaiting human approval, one careful reading at a time. (I am mostly writing this essay to myself. This is hard for me to hear.)

To see what an alternative could look like, we should start somewhere altogether unexpected: with rocket engines.

Two ways to buy confidence

One of my favorite documentaries of all time (every engineer should watch it) is called Cosmodrome. It tells the story of the engines built for the Soviet N1 lunar program, and underneath the Cold War history is a contrast between two ways an engineering organization can operate and come to trust a complex machine.

Apollo bought its confidence the traditional, expensive way. The United States had money, industrial depth, armies of specialists, purpose-built test infrastructure, and a political mandate to reach the Moon by the end of the decade, before the Soviets, without killing astronauts on national television.

So NASA poured almost all of its resources into a vast preflight apparatus: modeling, review, documentation, component qualification, static firing, integration testing, mission rehearsal. It built facilities specifically to fire Saturn V engines and stages, and the flight hardware was static-tested and certified before it ever reached Kennedy Space Center. (NASA History) Apollo 4 was the first "all-up" test of the complete three-stage Saturn V, an aggressive flight-test strategy that combined systems NASA's earlier practice would have flown incrementally. (NASA) That aggression rested on an extraordinary foundation of ground work. The launch was still a test. It was just a very expensive test that the institution had arranged and very much expected to pass.

The Soviet program had brilliant engineers and little else. They didn't have the funding, the infrastructure, the coordination, or the schedule control. So they leaned on the one resource they did have, and at the engine level that meant direct contact with hardware. Build, fire, inspect, modify, fire again. Nobody read the welds, they pressurized them. Less simulation, more ignition: fire it up, see if it explodes, fix what broke, do it again, baby. And the process worked, at least at the component level. Boris Chertok's history of the program records that the N1's NK-15 first-stage engines achieved substantially higher chamber pressure and specific impulse than the Saturn V's F-1. (Chertok, Rockets and People Vol. IV) These were sophisticated engines built by people who had learned to use failure as an input and a guide.

The N1 also shows exactly where the approach runs out. Its first stage, Block A, clustered thirty of those engines into a single system of staggering complexity, and that complete stage was never static-fired on the ground. The reliability of the whole was supposed to follow from the reliability of the parts, but individual engine firings could not reveal the interactions among engines, plumbing, structure, wiring, and vehicle dynamics. Chertok later described each N1 launch as walking into a minefield without a minesweeper. (Chertok) The Soviet engineers built superb components, but they didn't build a way for the integrated system to fail cheaply before flight. All four N1 launches ended in failure, and the program died.

The lesson is not that the Soviet program was better than Apollo (it wasn't), and not that one side was reckless while the other was careful (both did their best inside their constraints). The useful contrast is narrower. Apollo converted resources into preflight confidence. The engine shop converted repeated contact with hardware into...