News for hackers. Stuff that matters.
Re:Benefits of a Monorepo by Cthulhu_ on Wednesday May 01, 2019 @07:22AM (#19796101)
> The outcome of multiple repos should be modular libraries.

Yes; also they should all be treated as separate, independent products. Where multi-repos go wrong is when a whole product spans multiple repos, and a feature of the product depends on features being added or altered in multiple projects.

Ideally, the split should be so that nobody has to work across multiple repos to finish a feature.

The github / NPM ecosystem is IMO a good way to look at it; libraries that are all independent of one another who have a (usually pretty good) adherence to semver.

Re:Benefits of a Monorepo by amelius on Wednesday May 01, 2019 @07:38AM (#19796168)
> Ideally, the split should be so that nobody has to work across multiple repos to finish a feature.

That does not sound realistic. Often I have to add a new function, and I think: where (in what library) does this function belong, and very often it's not the main library I'm working in at that moment.

Re:Benefits of a Monorepo by lmm on Wednesday May 01, 2019 @07:46AM (#19796196)
Adding a new function anywhere other than the leaf project where it's used is premature. Organize around user-facing functionality. Pull out common libraries as and when you have something common enough to factor out (and, crucially, test independently), not before.
Re:Benefits of a Monorepo by jacques_chester on Wednesday May 01, 2019 @08:00AM (#19796277)
So the answer to needing to open multiple PRs is to open multiple PRs.
Re:Benefits of a Monorepo by lmm on Wednesday May 01, 2019 @09:07AM (#19796661)
The answer is to adapt your working patterns so that you never have multiple PRs on the critical path. Long-term codebase quality may require multiple PRs, but delivering user-facing functionality doesn't.
Re:Benefits of a Monorepo by amelius on Wednesday May 01, 2019 @10:18AM (#19797189)
And what if I wanted to add a method to a class? Or a method and a data member?
Re:Benefits of a Monorepo by pjmlp on Wednesday May 01, 2019 @10:49AM (#19797487)
You get the library owner team to do it and bind to the new released version.

Microservices without network headaches.

Re:Benefits of a Monorepo by pjmlp on Wednesday May 01, 2019 @08:00AM (#19796279)
Usually libraries are owned by separate teams.