Can Resilience Engineering be sufficiently described in 5...?
summary
Asserts the title question is answered: “no” — resilience engineering is a 20-year multidisciplinary field now being applied to software, not reducible to high availability or chaos engineering. Gives concrete examples of practices that count as resilience work: automated tests and code review and feature flags as investments that pay for handling fundamental surprises. Mentions links and next resources and emphasizes this is a long-term, hard-to-see capability rather than a quick checklist.
AI-written summary · about
related talks
05mWhat is resilience engineering
30mResilience Engineering Mythbusting
43mResilience Engineering Mythbusting
11mResilience engineering mythbusting
44mFrom here to resilience - a travel guide
33mChaos Engineering, how to increase resilience by injecting chaos
51mWithout Resilience, Nothing Else Matters
22mResilience Is Not Enough