Becoming antifragile is more important than ever in disruptive times
summary
Argues that systems should gain from disorder by using concrete practices not slogans: run Chaos Monkey/Simian Army (open source on GitHub) and escalate to chaos gorilla to harden systems, adopt continuous deployment and canary releases plus A/B testing and auto scaling to shift toward convex outcomes, measure and cut technical and organizational debt with a Four Color backlog and Kanban, focus on reducing MTTR, and enforce skin in the game because hierarchy and silos are the main blockers.
AI-written summary · about
chapters (17)
- 0:00Introduction and speaker background
- 1:03Risks and risk management strategies
- 2:27What is antifragility?
- 3:34Examples of fragility and resilience
- 5:24Chaos engineering and antifragility
- 7:32Antifragility and agility layers
- 7:53Non-linearity in antifragile systems
- 12:26Optionality and experimentation
- 16:00Via negativa and reducing complexity
- 19:37Transferring fragility and skin in the game
- 23:31Team alignment and antifragility
- 24:13Biological antifragility and hormesis
- 25:17Economies of scale in software
- 25:58Mean time to repair vs failure
- 27:02Organizational depth and Conway's law
- 29:55Reducing organizational depth
- 30:37Q&A session
related talks
50mBecoming antifragile is more important than ever in disruptive times
14mAntifragility or taming the hydra
48mHarnessing Chaos; the hidden ingredient behind building better systems
01h 04mTrust and Confidence through Chaos
01h 01mFrom 'Agile Hangover' to 'Antifragile Organisations'
38mWhy software developers should build a resilience culture based on chaos engineering
44mDeveloping a Culture of Reliability and Resilience through Chaos
45mDeveloping a Chaos Architecture Mindset