Deploying Humans at the Edge of SRE
summary
Argues that SRE must expand beyond platform teams to include support, TAMs, deployment and integration engineers, and devrel, applying SRE practices to user-facing work; proposes measurable signals like API integration shapes (persona buckets), tracking non-incident support workarounds, retries, costs and incidents during high-value events, and uncommon checks called zero slos; warns against believing everything can be automated, endorses mission control rotations and residencies to build empathy and reduce user-facing toil.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:31Reliability is Perception
- 2:27Field Code
- 3:18Long Term Short Term
- 5:41The Fields
- 6:41Examples
- 10:39Everything can be automated
- 11:34SRE practices
- 12:52SRE roles
- 16:25Conclusion
related talks
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
25mSRE Guiding Principles & Transformational Framework
45mClearing the Way for SRE in the Enterprise
31mConfessions of an SRE Manager
24mBeing Reasonable about SRE
47mPersistent SRE Antipatterns: Pitfalls on the Road to Creating a Successful
38m"Disorganizing" Your SRE Organization
35mCare and Feeding of SRE