DevOps, but you don't need to be an enterprise
summary
Argues that fragility splits into static issues and four dynamic risks: capacity of people, context of people, scale of the system, and dependencies, and that dynamic fragility usually goes unnoticed until a failure. Recommends practical moves: prefer one tool at a time, wear multiple heads so owners know full lifecycle, maintain actively, prioritize technologies by a value curve vs learning curve, and battle-test systems with small experiments because you cannot reliably track these risks until they break.
AI-written summary · about
chapters (4)
related talks
50mBecoming antifragile is more important than ever in disruptive times
56mKeynote: Defining and Embracing The Software Fragility
36mBecoming antifragile is more important than ever in disruptive times
01h 39mPostOps: A Non-Surgical Tale of Software, Fragility, and Reliability
22mDevOps is not a War
45mOpening Keynote: The Enterprise DevOps Mind Trap
11mDevOps Pitfalls, Beyond The Technology
36mHuman Factors and DevOps