What a Beautiful Disaster in a Perfect World
summary
The talk examines why software systems fail in production despite good intentions, blaming human factors and organizational issues as well as technical gaps. It presents architectural patterns and practices—such as fail-fast, circuit breaker, and supervisor—to build more resilient systems and discusses how team communication, deadlines, process pressure, and poor decisions contribute to outages and burnout.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:40Doomed systems
- 10:09Fail Fast theory and practice
- 16:11System dynamics theory
- 24:11Supervisors and hierarchy
- 25:57Circuit Breaker pattern
- 33:13Stage Driven Architecture
- 35:19Reactive Streams and back pressure
- 37:51Guaranteed message delivery
- 39:40Summary
- 41:07Why systems fail
related talks
48mHarnessing Chaos; the hidden ingredient behind building better systems
05mWho's to Blame?
54mRuin Your Systems By Making Them Perfect
39mConfessions of a Systems Engineer: Learning from My 20+ Years of Failure
46mSwiss Cheese, or Communication Errors That Lead to Disaster
25mBurnout: The Hidden Failure Mode of High-Performing Teams
52mRuin Your Systems By Making Them Perfect
31m"Failure" as Success: The Mindset, the Methods, and the Landmines