The Evolution of Site Reliability Engineering
summary
Five generations of SRE evolution: starts as firefighters with 1500 minutes MTTR and manual scripts, slides into a harmful service guard whitelist gatekeeper phase, then becomes an advocate that builds monitoring/alerting and self-service deployment to empower developer ownership, moves to partner planning with shared on‑call and unified priorities, and reaches True North where core libraries (over 95% Python packaging adoption) and unified planning allocate reliability work across teams.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:44Founding Principles
- 6:00Fire Fighter
- 8:40Case Study
- 11:25Winston Churchill Quote
- 14:35Gatekeeping
- 16:21Human Gaming
- 17:57Release Team
- 20:08Tools for Gatekeeping
- 22:33How to Grow Past Gatekeeping
- 28:44The Advocate
- 31:47Monitoring and alerting
- 32:43The advocates
- 34:23How to be an advocate
- 38:31Partner Generation
- 41:02Roles and Responsibilities
- 42:48Tools
- 47:59The True North
- 49:31Outro
related talks
23mSite Reliability Evangelism: Practice Start-up within an Established...
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
25mSRE Guiding Principles & Transformational Framework
49mWhat SRE Could Be: Systems Reliability Engineering
18mDeploying Humans at the Edge of SRE
38m"Disorganizing" Your SRE Organization
45mClearing the Way for SRE in the Enterprise
33mChallenges of Starting an SRE Team from Scratch in an Enterprise