At Cookies, most of our code is managed and built in a monorepo pattern. We made this choice for a number of reasons, Bazel being one of them; it is at the core of how we build solutions and execute toward technical excellence.
Why Bazel changes the way you code Bazel makes it substantially easier to manage dependencies, and is able to detect and understand the inter-relations between these dependencies and your code. Furthermore, the dependency model of your own code is much more available to the computer with Bazel.
What results is a build which is both fast and correct - only the parts that have changed are re-built (like Makefiles on crack), and that build is (theoretically) provable to be byte-for-byte identical as your desired target.
It does this by understanding the state of each of those internal dependencies, the current version of them (regardless of language), and then applying that to your build graph as a dependency itself.
What Bazel does for us Bazel builds all of our code, and manages dependencies responsibly.
