The Biases Confronting SREs
summary
SRE originates at Google in 2004 and the talk argues that real practice splits into three buckets: on-call or production reliability, collaborations with engineering, and team-built tooling; on-call time is non-discretionary and routinely consumes discretionary work. Claims include that treating Google SRE as sacred creates origination bias, that production readiness often becomes a wall thrown over to ops, and that organizational structure, job code equity and reporting protections materially change whether reliability work succeeds.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:33My Bias Journey
- 1:40Google SRE
- 2:31Bias
- 3:02Cognitive Bias
- 3:59Stereotypes
- 4:48The man himself
- 5:23What is SRE
- 6:17Why is SRE hard
- 8:14Is SRE an instance of DevOps
- 8:51Team Topologies
- 10:43Production Readiness
- 11:36Workplace Equity
- 13:06Organizational Bias
