Diamonds with Flaws: Examining the Pressures, Realities, and...
summary
Argues that SRE is overloaded with responsibilities—cites a 26-item list of tasks and the market full of CI/CD, observability, APM and Kubernetes solutions—claims big-company practices represent <1% of engineers and often don’t map to smaller orgs. Points out concrete expectations like 10 deploys per day are unnecessary for many services, and constraints include headcount, budget, compliance and ownership. Recommends choosing tools and processes that meet real needs, measure outcomes, and avoid chasing every shiny solution.
AI-written summary · about
chapters (6)
- 0:00SRE pressures and realities
- 3:38Overwhelming pressures on SRE
- 9:35SRE definitions and best practices
- 13:54One-size-fits-all SRE realities
- 17:21Future of SRE: meaningful decisions
- 20:51Embrace flaws to become a diamond
related talks
45mClearing the Way for SRE in the Enterprise
18mDeploying Humans at the Edge of SRE
27mThe curious case of the DevOps engineer and other things ...
31mConfessions of an SRE Manager
22mChallenges in delivering value using SRE, DevSecOps and Value...
35mThe Best SREs Seem to Be the Ones without an SRE Title—And What We Can Do
07mIGNITE: Metrics, Margins, Mutiny – How to make your SREs (not) run away
34mExploring Disconnects between Reliability Practitioners and Management