Book Overflow Is Strategy Worth It? - Crafting Engineering Strategy by Will Larson
Mar 30, 2026
A brisk dive into engineering strategy, covering when monoliths or microservices fit team structure and autonomy. They dissect Stripe’s API choices, long-lived APIs, and use of Sorbet. Practical tactics include piloting platform changes, documenting strategy, and running quarterly reviews. They also debate measuring strategy by speed versus correctness.
AI Snips
Chapters
Books
Transcript
Episode notes
Architecture Choice Is An Organizational Decision
- The monolith vs microservices choice is primarily organizational, not technical.
- Nathan Toups emphasizes team autonomy and cognitive load: distributed systems raise reasoning costs without clear boundaries.
Use Business Unit Monoliths For Team Autonomy
- Adopt a business unit monolith policy to give teams autonomy inside a bounded codebase.
- Carter Morgan describes an app context pattern with per-unit repos, CI/CD, and DB control to reduce cross-team coupling.
Strategy Value Changes With Context
- Strategies can be contextually good at conception and later become bad as business conditions change.
- Carter Morgan references Uber's decomposition: high initial value that decayed over time as scale and priorities shifted.
