> I prefer to use a monorepo structure Worked at a company where that approach lead to huge unwieldy structure that no one dared to touch to not break anything

> I prefer to use a monorepo structure Worked at a company where that approach lead to huge unwieldy structure that no one dared to touch to not break anything other teams are working on. The problem was not so much the repo, but dependencies structure (like single requirements.txt for the whole repo) and build scripts. In theory it should've worked great -- you only need to update a dependency once and be sure all the code has the most recent security patches. In reality everyone was afraid to touch it, because it will break someone's else code. Monorepos work great only if you have serious NIH syndrome (Google). I actually started appreciating damned micro-services there, as long as each service just reflects organization team structure. https://en.wikipedia.org/wiki/Conway's_law https://en.wikipedia.org/wiki/Conway's_law