Congratulations, you Failed!
summary
Argues failure is inevitable so induce it on your schedule using concrete practices: failing-tests-first (TDD), frequent small deployments (blue/green or canary), chaos experiments with tools like the chaos monkey and staged chaos game day, and observability via metrics tracing and logs. Recommends infra as code (Terraform, Ansible), circuit breakers and health checks, and dedicating 10–20% learning time. Cites a real incident where a GitLab deleted production database leads to fixing unsafe tooling rather than firing the engineer.
AI-written summary · about
chapters (21)
- 0:00Dev Days and DevOps Pro Europe
- 1:49Keynote speaker: Mikhail Rook
- 2:31Defining failure
- 9:16Failure as growth
- 13:12Failure in complex systems
- 17:47Safe-to-fail organizations
- 21:19Test Driven Development
- 23:05Adaptive resilient orgs
- 25:57Continuous delivery
- 27:23Frequent releases reduce risk
- 31:17Observability and operability
- 32:43Chaos engineering
- 37:42Closing keynote
- 38:47Q&A: Fear of failure
- 41:37Q&A: Learning journey
- 43:45Q&A: Small experiments
- 46:34Q&A: Selling failure resilience
- 49:19Q&A: Learning vs doing
- 53:09Q&A: Perfect planning myth
- 58:03Q&A: Blameless failure learning
- 1:01:15Q&A: Avoiding gambler's mentality
related talks
29mLooking under the rug: the art of learning from failure
41m‘Failure’ as Success: The Mindset, the Methods, and the Landmines
01h 04mTrust and Confidence through Chaos
50mDevOps Project Failures - Lessons Learned and Strategies for Recovery
32mBuilding for Gracious Failure
17mDevOps Leadership in practice. True stories
31m"Failure" as Success: The Mindset, the Methods, and the Landmines
48mHarnessing Chaos; the hidden ingredient behind building better systems