Software in Space: Lessons Every Developer Can Learn From
summary
Examines four mission failures and two rescues with concrete causes and fixes: a 16-bit signed integer overflow in Ariane 5 destroys a $7B launch; Cassini–Huygens is saved by slowing Cassini to remove relative Doppler error after an untested link would have lost 80% of packets; Mars Climate Orbiter is lost to a metric vs imperial unit mismatch that multiplies thrust by 4.5; Spirit and others survive by creative operational workarounds exposing a single point of failure and the need to handle Doppler-induced frequency shift and edge-case tests.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:07Ariane 5 failure lessons
- 15:25Numbers and data types
- 16:26Cassini-Huygens testing failures
- 29:09Mars Climate Orbiter unit mismatch
- 33:27Mars Polar Lander edge cases
- 34:28Conclusion and key takeaways for developers
related talks
44mFailure Is Always An Option
39mFailure is Not an Option! SRE Lessons 50 Years after the Apollo 13 Flight
58mProgramming and Technology in Amateur Space Exploration
01h 31mOn the Future of Flight Software
01h 07mContrasting Embedded Software Development for the Space Shuttle and the Orion MPCV
46mWhat the Soviet Space Program Taught Me About Digital Product Development
55mSpace Shuttle
54mThe Error of our Ways