Culture Trumps YAML
summary
Argues that fixing culture yields bigger wins than better YAML, showing a personal shift from coding to coaching and process work; implements an on-call rota with up-to-date runbooks, runs incident management training, and starts tracking DORA metrics so change failure rate is measurable. Results: reduced burnout, fewer single-point-of-failure heroes, faster delivery despite less firefighting, and measurable leverage by enabling engineers to move from solo fixes to repeatable, team-owned reliability practices.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:01Definition of Culture
- 1:43Architecture diagram
- 1:57YAML
- 2:54Bad Culture
- 3:15SocioTechnical Problems
- 3:58Who am I
- 4:19My dog
- 4:48Who is Brian Murphy
- 8:00What have I learned
- 9:27How do I do this
- 9:47Be enthusiastic
- 11:31Im sorry
- 12:02Dora Metrics
- 13:57On Call
- 16:54Incident Management Training
- 20:11One Item
- 22:27Resources
- 23:02Questions
related talks
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
14mA DevOps Mindset: Transforming Organizational Culture
43mSoftware Eats Culture For Breakfast
30mIf DevOps Is Culture, Why Does Everyone Only Talk About Tools?
05mDevOps Is Not a Department
32mTales from the DevOps Transformation Trenches
45mShift Your Leadership
44mDevops - What does devops culture mean for engineers?