7 Deadly Traps of SRE
summary
Seven concrete failure modes: Hero trap (all‑nighters create single points), Tooling trap (adding Kubernetes and dozens of shiny stacks increases learning curves and YAML nightmares), Complexity trap (premature optimization and overengineering), Postmortem trap (make them blameless and actionable for learning), Nines trap (SLOs and error budgets are pointless for the wrong product), plus the big‑tech and reactive traps. Practical fixes: introduce on‑call quickly, enforce teaching/ownership, and reserve 10% time for tech debt. Notes one ironical metric: the slide lists eight points not seven.
AI-written summary · about
chapters (10)
- 0:00Introduction and Welcome
- 0:41Audience Interaction and Roles
- 1:26The Seven Deadly Traps of SRE
- 3:00Trap 1: The Hero Trap
- 6:34Trap 2: The Tooling Trap
- 8:25Trap 3: The Complexity Trap
- 13:15Trap 4: The Postmortem Trap
- 15:33Trap 5: The Nines Trap
- 17:42Additional Traps and Conclusion
- 20:38Event Information and Closing Remarks
related talks
51mCommon pitfalls in engineering teams and how to avoid them
48mThe 10 vicious circles at work: detecting and breaking them up
24mHow to Destroy an SRE
33mWhat are the common Anti Patterns of SRE?
47mPersistent SRE Antipatterns: Pitfalls on the Road to Creating a Successful
13mTen Ways to Doom Your DevSecOps
43mWhere SRE Can Go Wrong
29mThe Curious SRE: Cultivating a Mindset for System Resilience