#FAIL
summary
Compilation of real failures shows concrete causes and fixes: public displays reveal ATMs on old Windows; a C time zero yields 1969 timestamps and PayPal refusing payments over zero; a NaN steering signal from MATLAB slams a race car; a 2014 paper finds three quarters of production failures reproducible by unit tests; Ariane 5 integer overflow from reused Ada code destroys a rocket; a Vostochny launch loses 19 satellites from a configuration mismatch; spreadsheets convert gene names and 20% of genomics supplements contain errors, with policy decisions once driven by a broken Excel model.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:00KevlinHenney Screens
- 8:01Time traveling
- 8:55Time function
- 12:52NaN
- 14:42Simple testing can prevent most critical failures
- 17:00Validate your data
- 18:40Programming pearls
- 24:32Muphry's law
- 26:11More programming pearls
- 35:45101 things I learned in architecture school
- 45:15Assumptions
- 47:30Configuration error
- 51:08GIGO: Garbage in, garbage out
- 53:02Excel: Worlds most popular FP
- 1:02:35Conclusion
- 1:03:20Outro
related talks
29mThe Most Bizarre Software Bugs in History
26mThe software bug all stars - and what we can learn from them
22mBugs That Made Headlines – and What They Reveal About How We Build Software
26mThe top IT failures in history
50mLearning in Production (or Why the Apollo 11 Landing Nearly Failed)
34mWhy Good Software Goes Bad
32mBuilding for Gracious Failure
32mOpening Keynote: The Good Bad Bug: Fail Your Way to Better Code