Reduced overhead for ci/cd, code review, code syncing and branching. No need to sync multiple repos and have complicated dependency versioning for in house lib

Reduced overhead for ci/cd, code review, code syncing and branching. No need to sync multiple repos and have complicated dependency versioning for in house libraries. In house libraries are easier to refactor as dependent code can be updated in a single PR. Code tends to be more reusable and you tend to make more reusable libraries as it is as easy as creating a new directory in the repo. Services and tools can still have separation of control with all the monorepo advantages. The only reason to not monorepo is if you are thinking of open sourcing the lib/tool you’re building but even then you can cut it out of the monorepo.