The Most Bizarre Software Bugs in History
summary
A sequence of concrete failures decides whether to watch: a flight-control single AoA sensor forces nose-down commands and contributes to crashes after certification work is self-reviewed; a Mars orbiter misinterprets imperial units as metric by a factor of 4.45 and burns up; Google marks every site dangerous from one stray “/”; an automated pricing loop lists a book at $23.7 million; JP Morgan hides risk and loses $6 billion because spreadsheets average wrong; a script with an extra space runs rm -rf / and nukes a system.
AI-written summary · about
chapters (17)
- 0:00Welcome to bizarre bugs
- 1:02Lion Air Flight 610 crash
- 3:10Boeing 737 Max MCAS
- 7:31MCAS sensor failure cause
- 8:56FAA certification flaws
- 10:20Swiss cheese model failures
- 11:23Combinatorics and hidden bugs
- 12:29Google’s site blacklist typo
- 13:53NASA Mars Climate Orbiter
- 17:10NASA integration test failure
- 18:12Database bug Steve Null
- 19:40Edge cases in user inputs
- 20:48Amazon pricing disaster
- 22:14Excel gene autocorrect errors
- 23:42JP Morgan $6B spreadsheet error
- 25:30Bumblebee rm -rf bug
- 27:16Q&A
related talks
22mBugs That Made Headlines – and What They Reveal About How We Build Software
26mThe software bug all stars - and what we can learn from them
01h 04m#FAIL
26mThe top IT failures in history
53mMayday Mark 2! More Software Lessons From Aviation Disasters.
32mOpening Keynote: The Good Bad Bug: Fail Your Way to Better Code
34mWhy Good Software Goes Bad
56mBeyond the Known Knowns