When Monorepos Go Bad
You’d like to believe that the contents of your monorepo are well constrained, you’ve followed Loose Coupling principles thoroughly, and it’s SOLID as far as the eye can see. And yet, yet , this happens It isn’t like it’s some #CowboyDeveloper deciding to go f**k around in the code-base, and send in all the changes to the 17 tickets that he (•) was working on at the same time. I mean of course yes, that happens. In this case though, it was that one change in a library module, that was needed, that trickled up through the code-base, and ended up affecting everything. We’re not perfect. It may have been “ SOLID as far as the eye can see”, but it turns out that the bug in the library module was actually over the horizon, and yeah, it affected everything. Sigh. I know what I’m doing for the next 6 hours… (•) Yes. It’s always He .