3 ms·
Monorepos require much more care to be put into the integration/CI side of the process. This is worth a read: https://yosefk.com/blog/dont-ask-if-a-monorepo-is
by zdw 6y ago
Monorepos require much more care to be put into the integration/CI side of the process.
This is worth a read: https://yosefk.com/blog/dont-ask-if-a-monorepo-is-good-for-you-ask-if-youre-good-enough-for-a-monorepo.html https://yosefk.com/blog/dont-ask-if-a-monorepo-is-good-for-y...
- jeffbee 6y agoThat argument is super, super weird. I agree that if you are a complete jackass with a demonstrated tendency to make poor choices, a monorepo may not work well for you. On the other hand, software development is probably not the right career for such a defective person, or the right line of business for such a defective organization. The anti-pattern described at the beginning of the article is why you should adopt trunk-based development, not a good argument for why you should avoid monorepos. https://trunkbaseddevelopment.com/ https://trunkbaseddevelopment.com/
- zdw 6y agoTrunk based development is definitely the ideal, and the mode of operation forced on users of Gerrit/Repo, which tries to implement much of Google's internal monorepo workflow with multiple external standalone repos. The main point is the "better tooling than average" section near the end - you need tools that can understand relationships between different parts of the codebases, and test appropriately, which is where the integration process for monorepos starts to fall apart.