> hours of CI testing time introduced by having to run tests on the whole monorepo at each commit instead of just the project that changed. This is rarely the

> hours of CI testing time introduced by having to run tests on the whole monorepo at each commit instead of just the project that changed. This is rarely the case. Most monorepos shard tests such that wall time is minimised and have dependency analysis that only runs tests affected by the changed code. More of a problem is that IDEs and LSPs often don't deal well with having to index and navigate very large codebases. I've maintained both monorepo and polyrepo environments and there are pros and cons to both, and they vary _wildly_ based on the language being used.