This IS NOT Fine: Putting Out (Code) Fires

on YouTube ↗27m

" summary

Argues for adopting firefighting-style incident management: formalize an incident commander role, a comm chief who records timestamps and schedules the post incident review, and rotate incident teams so juniors run real incidents. Cites FireScope→NIMS principles: flexibility, consistency, standardization, budget, and gives concrete tooling options (PagerDuty/VictorOps, Slack + video, public status page). Uses Netflix’s regional-availability strategy and the S3 outage to justify chaos-aware design and pre-warned standby engineers.

AI-written summary · about

" chapters (16)

1. 0:00Start
2. 2:51EMILY FREEMAN Developer Advocate
3. 5:58FIREFIGHTING hos come a long way.
4. 6:43FASHION FAUX PAS
5. 6:53POLITICAL UPHEAVAL
6. 7:10DESTRUCTIVE FOREST FIRES
7. 8:03ORGANIZATIONS MUST BE FLEXIBLE
8. 8:43CONSISTENT SYSTEMS
9. 9:28STANDARDIZE EVERYTHING Make it easy to understand.
10. 11:523. STANDARDIZE EVERYTHING
11. 13:244. KEEP THE PRICE DOWN
12. 14:48FIRESCOPE WORKED
13. 21:28HOP ON A VIDEO CALL
14. 23:15Stay focused on fixing the issue and communicating with your team.
15. 24:27COMMUNICATE WITH LEADERSHIP And everyone else
16. 24:58PROVIDE COVER FOR ENGINEERS