2023-11-08 · Technical Discussion
Monorepo or multi-repo: choose with trade-offs, not vibes
Ownership, CI cost, and release coupling weighed for a team of twelve.
Introduction
Neither option is the professional default. We score both against a concrete team setup, then land on the boundary conditions that should actually flip your decision.
The uncomfortable middle
Most advice here is written for the extremes: brand-new teams and enormous organizations. Real teams live in the middle, where the pragmatic answer is rarely the textbook one.
Notes from the middle
- Process is what makes a bad day survivable, not what makes a good day efficient.
- The person who writes the summary owns the decision — so rotate it.
- “We should” statements rot; dated commitments don’t.
Questions worth asking
- What would we do if we had half the time?
- Which part of this would we defend in an incident review?
- What are we pretending not to know?
Closing
Disagree, commit, and put the date on it. Then move on to the actual work.