Mission Critical Mindset Building a Culture of Resilience in DevOps Teams
summary
Pager fires at 3:00 a.m. after a Friday deploy with irreversible schema changes, rollback fails and a manual SQL restore fixes production but exposes missing runbooks; 77% of engineers report burnout. Teams adopt checklists for DB migrations, automate Slack incident channels and email templates so logs and oncall lists appear instantly, apply SLOs from SRE practice, and ban context switching to cut troubleshooting time. Success looks like rehearsed, low-risk deploys—boring releases deserve champagne—and incremental habits that actually get done.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:09On-call disasters reality
- 5:45Human cost of firefighting
- 7:10Psychological safety
- 11:45High standards feedback
- 14:34Core habits for resilience
- 20:11Features versus system quality
- 22:17Boring releases over risky launches
- 25:08Adopting habits sustainably
related talks
21mBuilding A DevOps Culture in a Remote World
41mLessons from Mission-Critical Systems in Fast-Moving Industries
26mThe emotional chaos of deploying code
47mDevOps or DevX – Lessons We Learned Shifting Left the Wrong Way
26mHuman Trust in Continuos Deployment
29mThe Curious SRE: Cultivating a Mindset for System Resilience
42mHow to foster a Culture of Resilience
52mDevops @Scale