20 Years of SRE: Highs and Lows
summary
Starts from a concrete origin: production was managed by a forked cluster.py list, teams built babysitter to edit arrays at runtime, then evolved into Borg and workqueue; SRE grows by engineering the slightly-less-bad solution until the next problem is solvable. Claims include Gartner’s projection that 75% of enterprises adopt SRE practices by 2027. Notes what fails: poor junior career pipelines, scarce quantitative models tying effort to user value, and uneven program post‑mortems across large organizations.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:14Myths about Google SRE
- 8:40Early SRE challenges
- 10:48SRE growth and demand
- 15:24SRE's business impact
- 19:21SRE's social influence
- 21:47SRE career challenges
- 23:58Critiques of SRE models
- 26:07Future of SRE
related talks
25mSRE in the Third Age
33mMy Journey to SRE
28mEvolution of SRE and Rising Need of SRE Catalyzers
52mThe Only Constant Is Change: Lessons from a 25 Year SRE Career
29mZero to SRE
36mWhat Makes a Good SRE: Findings from the SRE Survey
13mWhat To Do When SRE is Just a New Job Title?
13mSucceeding as the Lone SRE in a Small Team