The artikel doesn’t bringa it up, but I’ve seen several places where repos has been cut according to company silos, where applikation code was in a monorepo for all teams, IaC was in one monorepo for all teams, and ops was in one monorepo for all teams. It was not good at all.
that isn't a mono repo, it is a polyrepo setup with the wrost features of a polyrepo. I use a polyrepo setup and it works well, but we need careful attention to the repo split - and repo where too many different teams work together gets the worst features of a monorepo combined with the worst features of a poly-repo. We have a lot of tooling around making the different repos stay in sync.
