For me, refactors were the largest "aha" moment. On large scale projects you can move a lot faster if you don't have to maintain backwards compatible API's. W

For me, refactors were the largest "aha" moment. On large scale projects you can move a lot faster if you don't have to maintain backwards compatible API's. We use Facebooks version of a mono-repo (BUCK [1]) for iOS dev. It's really easy to change an API, see all of the upstream breakages, write tests, fix upstream and submit a diff (pull request). With a fragmented large code base you're in a world of hurt because you're dealing with versioning. There is no guarantee of when every other dependency will migrate to the latest code path. But again, if you're in a 1-10 person team working on some trivial codebase, a monorepo might not be helpful. If you have 500 engineers working on a single codebase, tradeoffs change. [1] - https://buckbuild.com https://buckbuild.com