We Have a Complex Systems Problem…and We Need to Talk About It
summary
Argues that modern software is a bona fide complex system (cascading failures, emergence, nesting, dark debt) not merely complicated, so engineering choices change: favor continuous delivery and canary deployments, invest in observability (Prometheus, ELK, distributed tracing) and small frequent changes, and expect surprises. Gives concrete notes: Google Search Appliance is discontinued, federated-search idea is unimplemented, Release It is a recommended stability-patterns source, and an architecture guild at Comcast is working as a rules-based governance experiment.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:37The Welsh Framework
- 4:35Cascading Failures
- 5:48Open Systems
- 7:08Open Source
- 8:13Memory
- 9:33Meeting Minutes
- 10:44Google Search Appliance
- 12:06Nesting Behavior
- 13:11Conways Law
- 15:46Emergent Behavior
- 19:30Snowball Effects
- 26:36Chaos
- 28:58Operational Visibility
- 31:10Emergent Patterns
related talks
14mAntifragility or taming the hydra
28mSoftware-Defined Culture
01h 02mTools for simplified large scale systems
41mLessons from Mission-Critical Systems in Fast-Moving Industries
35mThe Dawn of Liquid Software
36mIt's Simple...
43mBetter Software Development Systems through Stress
48mHarnessing Chaos; the hidden ingredient behind building better systems