Keynote: Shut Your Laptop and Go to Sleep!
summary
An SDN DevOps team enforces a 72-hour stand down and a no-checkins window from 23:00–07:00, then rebuilds test coverage by expanding the test harness to pull on a reference controller. Within days the team reproduces the failure, finds the bug lives in the partner controller, and restores normal communication and throughput. The incident costs about $300,000 and normalizes team velocity within two weeks, showing sleep and boundaries improve reliability.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:25Sleep deprivation in tech
- 3:13Personal burnout story
- 8:27Turning point
- 10:10Root cause analysis
- 14:23Lessons learned
- 17:39Call to action
related talks
36mGetting back to sleep as soon as possible for the on-call developer
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
15mKeynote: The Self Driving Company
26mPaid to Sleep
37mKeynote - You are Load Bearing
58mKeynote: Seven Habits of a (Mostly) Successful Team
30mLearning from Learnings: Anatomy of Three Incidents
41mKeynote: Is the Developer Lifecycle Dead?