Making Chaos Engineering Boring: Debunking Myths Hampering Adoption
summary
Argues Chaos Engineering must become routine to reduce outages and on‑call pages, cites a LinkedIn poll where over 50% name buy‑in as the main blocker, and uses the Chaos Monkey origin to show randomness is only one end of a spectrum. Demonstrates concrete techniques — blocking system calls, tampering with containers, injecting failures into Kubernetes, JVM bytecode and browser JS — and claims these experiments, applied safely outside or in production, lower uncertainty and meaningfully cut incidents.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:05Agenda
- 1:54The definition of chaos engineering
- 3:00Innovation adoption lifecycle curve
- 6:21Chaos engineering myths
- 15:54Getting chaos engineering on the roadmap
- 20:08Chaos engineering books
- 22:11Outro
related talks
36mChaos Engineering in 2021
21mThe Psychology of Chaos Engineering
29mThe Psychology of Chaos Engineering
18mChaos Engineering: Break It On Purpose
27mChaos Engineering: The Path to Reliability
48mChaos Engineering: The Path to Reliability
26mBreaking Systems for Resilience
35mChaos Engineering – from destructive monkeys ...
