I think of org-wide monorepos the same way I think of zealous microservice use, or microfrontends, or platform engineering, etc. It is a "shiny thing" that FAAN

I think of org-wide monorepos the same way I think of zealous microservice use, or microfrontends, or platform engineering, etc. It is a "shiny thing" that FAANGs use, which get a disproportionate amount of tech evangelist coverage, and then transition into becoming the perceived "best-practice" by bored devs (myself included) to then create some tech-debt work. The reality is that these are somewhat niche usecases for very high scale orgs and/or very high-scale developer workforces which can afford to reinvent the wheel. The way the vast majority of companies should go about developing their systems is not new at all, its just to pragmatically apply tried and tested technologies, and transition to new shiny things where there is a demonstrable need. Worth saying that I'm definitely a fan of team-scoped monorepos though. Being able to automate building and testing across all my apps, update dependencies across all apps, and deploy with a single merge/pull request is great.