Developing a Culture of Reliability & Resilience through Chaos
summary
Argues that speed and reliability coexist: high performers deploy frequently, have low change lead time and much lower MTTR (Accelerate data), so invest in resilience rather than slowing releases. Build four capabilities—anticipate, synchronize, respond, learn—by defining SLOs/SLIs, observing outcomes, then running chaos engineering experiments and game days to explore, fix, verify, learn. Targets dark debt across infra, code and runbooks, use continuous verification of chaos tests, and treat resilience as an ongoing practiced muscle with empathy for users and operators.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:34Who am I?
- 7:42Speed vs. Reliability?
- 12:14Speed and Reliability
- 16:36Learning from "Surprises."
- 21:07Failures are inevitable
- 28:20Resilience?
- 36:15Resilience.
- 39:10Decision-making tools.
- 39:22Define "what matters"
- 40:03Open to everyone
- 43:32Continuous Verification
- 45:364 Capacities to Develop
- 46:06Practice!
- 46:53One last thing...
related talks
44mDeveloping a Culture of Reliability and Resilience through Chaos
48mChaos Engineering: The Path to Reliability
27mKickoff + Keynote
19mFireside Chat with Jason Yee
25mCombining Chaos, Observability & Resilience to get Chaos Engineering
29mImprove Resilience with automated chaos engineering
51mWithout Resilience, Nothing Else Matters
32mThe culture of Site Reliability Engineering