10 Lessons Learned in 10 Years of SRE
summary
Ten years of SRE experience across Google and Azure yields concrete rules: write down goals and measure progress toward stated goals; staff with a mix of generalists and tech-depth people familiar with runtimes and pipelines; keep on-call for control-plane pieces like Azure Resource Manager to stay current; use 2:1–7:1 SRE:dev ratios as guidance; establish feedback loops with product and execs; avoid SRE-owned services unless funded or handed to platform teams; finish what you start.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:41My SRE Journey
- 4:10Know what you want from SRE
- 5:59Align with business goals / customer needs
- 7:43Expertise matters
- 9:06You cannot declare "SRE"
- 11:38Build trust
- 15:22Finish what you start
- 18:25Be wary of "SRE services"
- 21:58Be wary of "scaling SRE"
- 24:56Stay humble
- 27:12Talk more
related talks
41mAn Introduction to SRE at Google (with DevOps Focus)
52mThe Only Constant Is Change: Lessons from a 25 Year SRE Career
25mSRE Guiding Principles & Transformational Framework
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
28mEvolution of SRE and Rising Need of SRE Catalyzers
07mIGNITE: Metrics, Margins, Mutiny – How to make your SREs (not) run away
30mThe Path to SRE
35mCare and Feeding of SRE