3 ms·
Problems don’t go away with fractured repos. They just change shape. Many repos maybe get you more reliable CI, but you pay for it with increased cost of integr
by dpark 7mo ago
Problems don’t go away with fractured repos. They just change shape. Many repos maybe get you more reliable CI, but you pay for it with increased cost of integrating dependencies and increased complexity with debugging breaks in production (assuming many repos mean many services).
In my experience, multiple small repos don’t even have better CI reliability than a mono repo as less is invested because it affects fewer people. 10 person repos regularly have flaky tests that never get addressed because “we’ll deal with it later”. The tolerance for flakiness goes up when you can attribute it to a close teammate you know is heads down on something critical instead of it feeling like a random test you don’t even care about.
- Havoc 7mo ago> Problems don’t go away with fractured repos. Not the problems but the part where broken CI cause everything to stop. Fractured repos have their own downsides but less chance of literally everyone sitting and waiting is greatly reduced
- dpark 7mo agoKind of? Almost tautologically, if you have multiple repos, it’s less likely that everyone will stuck at once. But it’s entirely possible that the total “stuck time” per engineer is no lower across a year. In my experience the only repos that never get stuck are ones with no checkin gates.