The Best SREs Seem to Be the Ones without an SRE Title—And What We Can Do
summary
Argument: most effective reliability work lives outside the org chart, shown by a single incident where a fiber cut cascades into service failures, broken network diagnostics, seven teams and roughly 20 people reassigned before root cause is found. Cites a study where 90% mitigated immediately but the remaining 10% — messy dependency graphs, misleading symptoms, poor platform observability — demand different tooling and skills. Proposes platform competence: ownership of capacity, observability, incident tooling, coding skills for managers, and next‑gen NLP/automation to shorten time‑to‑repair.
AI-written summary · about
chapters (7)
- 0:00Start
- 5:38Any guesses on what the issue was?
- 14:33How did we get here? Contributing Factors
- 18:38Incomplete SRE Tooling
- 23:24Platform Competence
- 26:03Coding Goals for Everyone
- 28:19(SRE) Management 2.0
related talks
38m"Disorganizing" Your SRE Organization
49mWhat SRE Could Be: Systems Reliability Engineering
45m“Disorganizing” Your SRE Organization
45mClearing the Way for SRE in the Enterprise
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
18mDeploying Humans at the Edge of SRE
24mBeing Reasonable about SRE
13mWhat To Do When SRE is Just a New Job Title?