I am building a foundational layer for building C++ apps using Bazel.
I am working on creating a standardized set of paths and third party libraries that work seamlessly across multiple developer teams. Allowing library upgrades to happen transparently in the background. This will enable developers to focus on business specific logic and not have to worry about the intricacies of the build system and allowing to "magically" work in the background. This is allow foray into Bazel and using it as a learning exercise to master it.
It's not JeanHeyd Meneide's (PhD) first time rage quitting. He has a history of this. He previously rage quitted from the C++ community and moved to the C community. I wonder where he's moving to next.
https://youtu.be/vaLKm9FE8oo
Is the code for the Search project in the mono repo as well? How does Google handle access control for their mono repos? Where's the secret sauce stored?
I am working on creating a standardized set of paths and third party libraries that work seamlessly across multiple developer teams. Allowing library upgrades to happen transparently in the background. This will enable developers to focus on business specific logic and not have to worry about the intricacies of the build system and allowing to "magically" work in the background. This is allow foray into Bazel and using it as a learning exercise to master it.