writing5 min read
The quiet case for monorepos
Not the Google-scale argument. The two-engineer argument: one repo, one CI, one shared types package, no coordination problem.
#tooling#monorepo
Most monorepo writing assumes you have a problem at scale. I want to make the smaller argument: if you are two engineers and three services, a monorepo removes more friction than it adds, full stop.