Who is responsible for Chaos?
summary
Most chaos programs originate with people who get paged in production: SREs and Ops or anyone with deployment and uptime responsibility; job titles with “engineer” dominate and about a third come from security/ops/R&D. Chaos testing traces back to Netflix’s Chaos Monkey, and some organizations report testers automating chaos—SREs design experiments, testers run and integrate them earlier in the lifecycle. A few companies only start after catastrophes (one director lost $600M in 22 minutes), so expect iteration and cross-team buy-in.
AI-written summary · about
chapters (16)
- 0:00Preamble
- 0:50Who is responsible for chaos?
- 1:07Which job titles are doing chaos?
- 1:23By job title - diagram
- 1:53Quote by Kolton Andrus (CEO @ Gremlin)
- 2:18Resposibilities
- 4:14Roles
- 4:35Why aren't testers doing chaos? - Chaos Testing
- 5:00Software Development Lifecycle
- 5:14It was called chaos testing
- 5:45Quote by Abby Bangser (PTE @ MOO)
- 6:29Testers doing chaos?!
- 7:15Who can start a chaos program?
- 8:22Do I need to wait for a catastrophe
- 8:34Quote by Casey Rosenthal (CEO @ Verica)
- 9:02Final thoughts
related talks
15mChaos - Does It Need to Be Included in Test Strategy?
52mChaos engineering: Breaking things on purpose in production
36mChaos Engineering
46mDesigning a System for Chaos
21mThe Psychology of Chaos Engineering
18mChaos Engineering: Break It On Purpose
27mChaos Engineering: The Path to Reliability
49mChaos & Intuition Engineering at Netflix