Antifragility or taming the hydra
summary
Argues that software should be built to get stronger after shocks rather than to predict them, applying Taleb’s antifragility to development: add observability, avoid centralization, slice services, and favor incremental BDD steps that deliver value and let reality guide the next decision. Cites Fukushima to justify small deep underground reactors and complexity limits, uses cloud autoscaling and monitoring as practical tools, and describes a concrete CI/CD pattern—delivery pipeline with manual approvals then automated scripts—that progressively automates and improves resilience.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:40The Black Swan
- 2:15Antifragility
- 3:22Damocles
- 4:05Phoenix
- 4:32Hydra
- 4:54Real life applications
- 7:24Complex systems
- 8:30Small incremental steps
- 9:22Naive interventionism
- 11:04Benefit from the crisis
related talks
50mBecoming antifragile is more important than ever in disruptive times
48mUnbreakable by Design: The Secret Tech of Antifragile Software
36mBecoming antifragile is more important than ever in disruptive times
43mBetter Software Development Systems through Stress
22mResilience Is Not Enough
16mSAG Expert Interview #12: The Art of Resilient Software Architecture
57mBuilding Systems that are #neverdone
01h 02mPractical Chaos Engineering breaking things on purpose to make them more resilient against failure