Double, Double, Toil and Trouble!
summary
Claims concrete operational rules: an SRE model that enforces a 50% toil cap so half of engineers time is spent automating, clear SLIs and SLOs that feed SLAs, and an error budget (for example 0.1–1% allowable failure) that gates release velocity. A operational handback or production readiness review pauses feature work until runbooks and tests reduce alert noise. Describes building a core SRE team with embedded engineers and reports that automation plus these rules enables sublinear people growth as services scale.
AI-written summary · about
chapters (14)
- 0:00Start
- 2:30about Veracity Solutions
- 2:59About me and my DevOps journey..
- 6:37My Teams' Standard Texts
- 7:29Free online copy of SRE book....
- 10:36Hire or Re-skill for Software Engineering
- 11:58Eliminate Toil Through Automation
- 12:53Limit Operational Load to 50%!
- 14:38Understand SLIS, SLOS, and SLAs
- 16:21Use and Adapt to Error Budgets
- 18:48PRR + Operational Handbacks
- 22:04Perform Blameless Post-Incident Reviews
- 23:52Centralized & Embedded SRES
- 24:52Make SRE Your Own!
related talks
27mGetting Started with SRE
25mUnleashing the potential of SRE for modern operations
30mWhen Is SRE Right For You?
05mSRE: What’s The Big Idea?
42mDemystifying SRE and DevOps
43mWhere SRE Can Go Wrong
34mDouble, Double Toil and Trouble; SRE Transform...
25mSRE Guiding Principles & Transformational Framework