Simplicity Matters
summary
Argument: simplicity is an objective property—things are simple when they aren’t entangled—and complexity comes from braiding concerns together. Concrete prescriptions: prefer pure functions over methods, prefer use maps/hashes instead of wrapping data in classes, avoid positional arguments that encode order, use queues to decouple chained calls, avoid XML and eventual consistency unless required. The payoff: dramatically fewer cognitive knots, easier refactoring, and greater architectural agility.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:46Welcome
- 1:07Simplicity
- 1:33Simple
- 3:36Easy
- 7:31Change
- 9:33Agility
- 12:23Metaculture
- 13:22Foo Fighters
- 14:20Programming vs Programs
- 16:10Hairball
- 17:35How to make things easy
- 19:49Why Arent We
- 22:04Simplicity is Not About You
- 23:42Simplicity is Not an Objective
- 23:57Lists in Order
- 24:59Why Care About Order
- 26:04Positional Arguments
- 29:33Information Problem
- 30:40Encapsulation
- 31:21Can you move it
- 31:54Systems of systems
- 33:29Conclusion
related talks
01h 22mSimplicity: not just for beginners
26mThe Dilemma of Simplicity
26mThe Power of Simplicity: Crafting Durable Software Systems
41mSimplicity as a Superpower
51mEmbracing Simplicity
43mDon't Walk Away From Complexity, Run
46mAchieving an evolutionary architecture through simplicity
01h 08mMidnote: For the Sake of Complexity