> This is what confuses me about monorepos. Their design requires an array of confusing processes and complex software to make the process of merging, testing, and releasing code manageable at scale (and "scale" can even be 6 developers working on 2 separate features each across 10 services, in one repo).
False. It is having multiple repos what creates those problems and a huge graph of versions and dependencies.
False. It is having multiple repos what creates those problems and a huge graph of versions and dependencies.
What "processes" are you talking about?