A single monorepo for an entire company rarely makes sense
A single monorepo for an entire company rarely makes sense.
A separate repo for every team also rarely makes sense.
The happy middle-ground? Put *related* code in a monorepo.
Benefits:
✅ Enforces consistency
✅ Fosters collaboration
✅ Makes it easy to share code
My rule: If our mission is to create a single, cohesive user-experience, we should favor a monorepo for all related code.
This way, the repo structure matches the goal.