Extreme Software Development Processes: Space Shuttle Flight Control and TeX Typesetting

The piece introduces two software examples that represent the ultimate in development process rigor and individual programmer mastery: the NASA space shuttle flight‑control software and Donald Knuth’s TeX typesetting system.

The shuttle software controls a 120‑ton vehicle carrying 2,000 tons of fuel, using four identical computers that vote on hundreds of decisions per second and a fifth standby unit; each of its final versions (≈420 k lines) contained at most one bug, and the system never tolerates crashes or restarts.

Its success stems from an extremely disciplined workflow: one‑third of the development cycle is spent in detailed requirement discussions with NASA, all specifications are fully documented, and no code changes occur without formal agreement.

The team maintains two encyclopedic databases—one tracking every line of code with change history and comments, the other recording every defect for nearly two decades—allowing them to predict defect counts and enforce process improvements.

The process also insists on fixing the root causes of defects, not just the symptoms, and assigns responsibility to the workflow rather than individuals; this approach earned SEI CMM5 certification and influenced many industry standards.

Knuth, after receiving the Turing Award, created TeX because existing typesetting tools compromised his book’s aesthetics; he released it with version numbers that converge on π, offered a doubling‑by‑doubling bug bounty, and achieved a level of code quality that virtually eliminated bugs.