Move Fast Build Things… Safely!
summary
Compares ten concrete F1 safety practices to software operations and lists actionable equivalents: automated vulnerability checks and adversarial CI/CD pipelines, canary deploys, mutual TLS and micro‑segmentation, chaos engineering for production fault hypotheses, modular components that can be removed, least privilege plus HSMs, and fast replaceable instances to reduce dwell time. Announces metrics that matter: 1.82s tyre change record, drivers must exit in under 5s, average breach cost ~$4M and mean detection ~287 days, arguing reverse uptime and base image freshness cut exposure.
AI-written summary · about
chapters (14)
- 0:00Start
- 3:56The Drive To Survive
- 9:12Pre-Crash Measures
- 14:05Mutual Tls
- 16:39Chaos Engineering
- 18:05Constant Monitoring and Replacement of the Tires
- 20:27Reverse Uptime
- 22:36Post Crash Measures
- 24:36Load Balancers
- 26:28Least Privileged Principle
- 27:28Hardware Security Modules
- 28:55Fire Suppression System
- 30:09Data Records
- 31:37Refueling
related talks
36mMove fast Build things… Safely!
23mThe Cost of Speed: Rethinking "Move Fast" in DevOps
40mMove Fast and Ship Things
29mEconomies of Speed
33mBattle Tested Application Security
28mPick any Three: Good, Fast, and Safe. DevOps from Scratch
43mEffective CI/CD for Large Systems
57mBuilding a Modern Security Engineering Organization