Move fast Build things… Safely!
summary
Compares Formula 1 safety measures to software practices and gives concrete actions: five pre‑crash and five post‑crash patterns including six‑point harness style automation for CI/CD, canary deployments for staged rollouts, mutual TLS for intra‑cluster encryption, and chaos engineering to find unknown failures. Cites a driver surviving a 2+ minute fire and a 1.82s pit tire change as motivation to replace and refresh nodes frequently, use hardware security modules, track reverse uptime and base‑image freshness, and notes breaches average $4M and 287 days to detect.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:03Speed versus security
- 3:09Speed vs traditional security
- 6:02DevOps vs DevSecOps
- 8:10Formula One’s speed and safety
- 17:39Pre-crash lessons for software
- 24:22Fault tolerance and resilience
- 28:38Chaos engineering adoption
- 31:30Pit crew for infrastructure
- 36:43Post-crash recovery patterns
- 41:24Defense in depth
- 44:30Security versus comfort
- 45:12Breach costs and urgency
- 45:56Q&A
related talks
36mMove fast Build things… Safely!
35mMove fast, build things… Safely!
41mLessons from Mission-Critical Systems in Fast-Moving Industries
27mEngineering Without a Safety Net: Where It Works and Where It Hurts
47mArchitecting for DevOps and Continuous Delivery
28m"TOGA: Checklists and Safety Measures for "Yoloing" in Prod"
22mFail Fast, Fail Often - Make Safety a Prerequisite for your Team
34mEmbarking on Your Security Journey