Evangelizing the SRE mindset

on YouTube ↗20m

" summary

Claims concrete numbers and fixes: four nines (53 minutes downtime) as a reliability target, a Stripe-cited cost framing and 17 hours a week on maintenance split into 13 hours tech debt and 4 hours bad code, and three remediation patterns — carve out 10% capacity or one tech-debt ticket per engineer, dedicate a team or sprint, or accept catastrophic failure. Includes a 3am on-call case study showing missing docs, and a built product, Cortex, that maps services, ownership, runbooks and succeeds at reducing time-to-recovery.

AI-written summary · about

" chapters (10)

1. 0:00Evangelizing SRE mindset
2. 1:17Introduction
3. 2:19SRE role evolution
4. 4:05Reliability culture
5. 8:18Reliability in delivery
6. 12:29Incident response case
7. 14:10Cost of poor reliability
8. 15:53Addressing tech debt
9. 18:22Key takeaways
10. 19:05Closing & resources

" related talks

• 28mHow to Do SRE When You Have No SREJoan O'Callaghan · SREcon19 Europe/Middle East/Africa
• 27mGetting Started with SREStephen Thorne · DevOps Enterprise Summit London 2018
• 23mSite Reliability Evangelism: Practice Start-up within an Established...Piers Chamberlain, Catherine Matheson · SREcon22 Asia/Pacific
• 58mEnterprise Roadmap for SRESteve McGhee, James Brookbank · Devopsdays Boston 2022
• 43mThe SRE I Aspire to BeYaniv Aknin · SREcon19 Europe/Middle East/Africa
• 24mHow to Destroy an SRECarly Richmond · SREday London 2024
• 46mReliability EngineeringMary Poppendieck · Craft Conference 2019
• 25mUnleashing the potential of SRE for modern operationsMonzur Ahmed Chowdhury · KCD Dhaka 2024