Conscious Coupling for Anti-fragile Engineers
summary
Argues that fragile systems come from modular and social coupling interacting, quantifies instability as efferent dependencies over total, and points to the NPM left-pad incident that unpublishing ~200 modules (and ~10,500 daily left-pad downloads) broke large webs of software. Recommends concrete tools and tactics: run npm-check and CI audits, consider yarn or npm shrinkwrap, fork or host critical packages, rehab via focused refactors, or isolate with private registries; frames work as sensing, learning, acting loops with reversible experiments.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:19Motivations
- 5:11Yarn
- 7:28Modular Coupling
- 18:26The Zeitgeist
- 21:58Envisioning
- 46:19Conclusion
related talks
29mThe Social Coding Contract
25mOn left-pad and empathy: understanding human connection
19mDevOps, but you don't need to be an enterprise
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
43mBetter Software Development Systems through Stress
01h 04mPredictably Unpredictable