Dealing With Complexity
summary
Defines complexity as whatever prevents doing the right thing now or later and argues simplicity is the prerequisite for agility, reliability and scale. Gives concrete numbers — 40 companies, 2–3 billion revenue, about 5,000 people — and concrete failures like the Java one‑URL session design that blocks Google indexing. Flags data, people and infrastructure as the main complexity sources, and points to a surprising concrete win: a 21-line python spell corrector that outperforms clever models with enough data.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:31Who I am and why I study complexity
- 4:26What complexity means
- 8:46Teams and growth
- 14:29Simplicity as solution
- 15:30Data as complexity source
- 17:16ML as simplifier
- 21:51People, process, infrastructure
- 24:22Communication protocols
- 25:50Q&A
related talks
29mEmbracing Complexity: Lessons From Product Teams
33mPractical Applications of Complexity in Software & Digital Products Development
43mDon't Walk Away From Complexity, Run
20mWhat Is Complexity and Why Digitalization Projects Often Fail Because of It
36mEngineering Luck: Essential and Accidental Complexity at GOJEK
29mComplexity: The Crucial Ingredient in Your Kitchen
29mDeprecating Simplicity
53mKeynote - Software Architecture, Team Topologies and Complexity Science