Architecting Apollo: Systems Design Lessons from the Golden Age of Spaceflight
summary
Covers concrete failures and fixes: Apollo guidance uses 12-word core set prioritization so a rendevu radar glitch sending 6,400 spurious commands/sec triggers 121/122 priority alarms and the computer resets five times while dropping low‑priority jobs to keep navigation alive; Apollo 13 loses oxygen tanks but uses the LM as lifeboat with a jury‑rigged CO2 adapter; Gemini 8 ends early after pulling a circuit breaker on a stuck thruster; Ariane 5 FL-501 explodes from a 64→16 bit conversion bug; Mars Climate Orbiter is lost from a 4.45 unit conversion error; Voyager fixes take four months to locate old docs.
AI-written summary · about
chapters (18)
- 0:00Space Race and Apollo intro
- 2:34Space Race milestones
- 8:18Analog to digital tech
- 13:59Murphy’s Law in aerospace
- 16:25Humans fix problems
- 19:56Automation levels
- 20:38Apollo 11 software
- 27:17Task prioritization threads
- 28:22Data persistence importance
- 29:25Ariane 5 failure lessons
- 31:30Gemini 8 failure analysis
- 37:50Failure mode selection
- 39:58Voyager 1 documentation
- 42:24Mars Climate Orbiter error
- 45:32Proton M sensor failure
- 46:57Apollo design lessons summary
- 48:43Learning from failures
- 50:24Q&A on root causes
related talks
45mCalling Voyager: Interface Design for NASA’s Deep Space Network
01h 01mArchitecture: The Stuff That's Hard to Change
34mBalancing Early Testing with Real-World Reliability
31mDeep Dive into Apollo Client
16mYou Can't Outrun Complexity - But You Can Orchestrate It.
46mWhy We All Build Bad Architectures and How to Stop
47mWe don't make mistakes
26mArchitecting for scale