The History Of Fire Escapes: How To Fail (Keynote)
summary
Argues that surprise failures come from poor physical design and policy not from bad luck and shows concrete analogs that map to infrastructure: use fire partitions to limit blast radius, install smoke alarms for early detection, deploy sprinkler systems for automated mitigation, and enforce clear exits so people and traffic can escape predictably. Presents concrete procedures, retrofit examples, and measurable outcomes so a system can be tested, instrumented, and proven to fail in safe, observed ways.
AI-written summary · about
chapters (4)
related talks
37mY2K and Other Disappointing Disasters: How To Create Fizzle
32mStaying Alive: Patterns for Failure Management from the Bottom of the Ocean
10mDesigning for Failure using AWS: Resilient Systems
46mFire, Brimstone, and Bad Security Decisions
16mEngineering Failure-Resilient Systems
40mBuilding Resilience: How to Learn More from Incidents
29mLearning from incidents: how things went right
41m‘Failure’ as Success: The Mindset, the Methods, and the Landmines