Create a Learning Culture
summary
Claims a process-first approach beats blame and yields repeatable fixes and faster recovery. A cloud estate of 15,000 cores and 300 microservices drives changes: incidents get immediate fixes then a debrief within 24–72 hours and a two-week checkpoint. Built artifacts include a debrief template, a shared folder of reports and debrief ticket labels; controls used are feature flags, gradual rollouts, behavior‑driven changes and split deployments. An autoscale revealed how bad branch assumptions push buggy code into production.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:00About Amir
- 3:00Creating a healthy culture
- 4:12Problems
- 7:21Example
- 13:48Debrief
- 17:45Lack of Trust
- 22:00How to conduct a debrief
- 24:39Notable learnings
- 30:17Questions
related talks
45mMaking Learning Conscious — How and why to build a learning culture
25mWhat I Learned
32mThis is Not a Technology Problem: Leveraging Culture and Process to Make the Most...
52mSecrets of a Strong Engineering Culture
09mFostering a learning culture in coding teams
31mBuilding an Enduring Culture of Engineering Excellence
36mBlue Grass in a Brown Field...
05mHappy DevOps teams