Hacker News Reader

I get that it's not a universally applicable solution. I guess at a certain point of scale your organisation would grow out of complete co-location.

But I don't think we have to go with the 100% co-location approach as well. A large monorepo could be organized into domain specific mini-monorepos with co-location benefits.

View on HN

It's not applicable at all once you get beyond a few teams.

A mono-repo makes decisions for your teams.

I think Google, Meta, Microsoft, Twitter, Uber [1] and the thousands of engineers that these companies (and many other companies) employ, would disagree with you.

[1] https://en.wikipedia.org/wiki/Monorepo

Those companies largely made the decision for monorepos before there was tooling to support a proper multi-repo existence.

Reply on news.ycombinator.com