My understanding about google is that they approach the dependencies as trying to build one statically linked binary and they tend to try to put all of the depe

My understanding about google is that they approach the dependencies as trying to build one statically linked binary and they tend to try to put all of the dependencies together in the same repo. (Mono-repo). For a large organization, I'm not convinced that's a sane way to go. Individual groups should have the primary responsibility for the modules that they produce. What we need is: 1. Tools that will automatically upgrade for us and report back when there are failures. 2. Better automated tools on where our code is missing test coverage (automated upgrades should break our code when something changes) 3. Better CI/CD rejection support (Something breaks the build, force a revert of the code)