Learning More from Complex Systems
summary
Four concrete takeaways: incidents are emergent novel events that teach more than root‑cause hunting; move from reductionist “one cause” analysis to cataloguing contributing factors across code, traffic, history and culture; stop blaming people — stop saying "human error" and instead run facilitated reviews with scribes to capture what signals operators saw and why they acted; use those richer timelines to prioritize removing haunted legacy components and to amplify existing resilience so systems and teams adapt rather than collapse.
AI-written summary · about
chapters (12)
- 0:00Introduction to complexity
- 1:02Evolution of tech systems
- 3:01Decentralization challenges
- 5:06Old vs. new incident response
- 7:37Socio-technical systems
- 9:05History of management theory
- 10:40Reductionism vs. systems
- 12:11Car example of systems
- 15:43Environmental impact on systems
- 19:10Characteristics of complexity
- 21:37Improving learning culture
- 24:14Engineering resilience
related talks
25mConvergence of Chaos Engineering and Revolutionized Technology Techniques
38mHolistic root cause analysis of software breakages through structural causal modeling
40mTrapped in the AI Error Loop: Why Smart Systems Keep Making Dumb Mistakes
43mIn defence of uncertainty
20mLearning at Scale Is Hard! Outage Pattern Analysis and Dirty Data
16mExistential Engineering or How Ethics Precedes Error Handling
31mHelp! There Are Humans in My Data!
48mPrinciples and Practices of Building Machine Learning Systems