Mayday Mark 2! More Software Lessons From Aviation Disasters.
summary
Deep dives into cases deliver actionable lessons: Air France 447 shows Pitot tube icing and conflicting airspeed cause autopilot disconnect, alternate-law flight control removes anti-stall protections and contributes to 228 fatalities; design choices (Airbus fly-by-wire laws) and ambiguous alerts confuse crews. A RabbitMQ cluster of three nodes with >1,000,000 queued messages causes an 8‑minute outage during node resync, exposing hidden sync costs. Emphasize crew resource management, redundancy tradeoffs, and deadly UX when automating.
AI-written summary · about
chapters (14)
- 0:00Introduction and context
- 2:04The evolution of safety
- 3:33Analyzing crash data
- 5:42Technological advancements
- 10:45Automation philosophies
- 13:03Air France 447 case study
- 17:10Human factors in complex systems
- 23:41Redundancy and failure
- 29:31Human cognitive limitations
- 36:09Consistency versus correctness
- 39:07Assumptions and irrationality
- 41:06Habituation and complacency
- 44:29System design challenges
- 46:49Conclusion and takeaways
related talks
53mMayday Mark 2! More Software Lessons From Aviation Disasters.
01h 15mSystem Crash, Plane Crash: Lessons from Commercial Aviation and Other Engineering Fields
01h 01mSwiss cheese, teamwork and other things we should learn from the aviation industry
01h 08mFighting the controls: madness and tragedy for programmers
36mIce, confusion, and the 38,000ft crash
51mThe Boeing 737 MAX: When Humans and Technology Don't Mix
34mTaking the 737 to the Max
37mDelivering fast and slow - Ethics of quality