Riding the wave of complexity
summary
Argues that software people must master complexity by keeping a brutally honest current-state, choosing a direction, and taking tiny repeatable steps; cites deployed work (HPC, autonomous inspection robots, digital twins at aquinor) and odd evidence like amoebae forming Tokyo‑like rail networks to show simple rules creating emergent order. Warns against cargo‑culting and big‑bang rewrites, promotes fast feedback loops, PDCA and retrospectives, treats technical debt is bank loan — small moves (even a spelling change) get into production and reveal reality.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:53Why complexity
- 3:18What we are doing now
- 4:51My claim
- 7:35Most common mistake
- 9:58Cargo culting
- 14:09Take small steps
- 17:04Be proactive
- 19:29Feedback loops
- 22:59Innovation
- 30:59Inclusion
- 33:12Navigating complexity
- 35:10Legacy code
- 39:22Trust
- 41:24Feedback
- 44:01Small steps
