There are technical pros and cons to both, but monorepos in my experience can "fix" or at least sidestep many human/big organization issues: - NIH, teams re-cr

There are technical pros and cons to both, but monorepos in my experience can "fix" or at least sidestep many human/big organization issues: - NIH, teams re-creating instead of re-using other teams work either due to not knowing it exists or because they feel they cannot control it. - The gatekeeper: "just ask Bob to give you access", repeat for the next two to four weeks. Once you get really big, source code access is even used as a political tool between teams. - The internal customers: Team A works on a common framework, teams B, C, D all use it. Good luck getting anyone of them to take a new release more than once in a blue moon, and everyone will be on a different version too so you have to support them all. Fun times.