Under "When to Use Bazel - Jason’s Opinion", that is not a particularly good description of how builds (especially code generation) worked at most of Amazon. At

Under "When to Use Bazel - Jason’s Opinion", that is not a particularly good description of how builds (especially code generation) worked at most of Amazon. At least he sort of gestures at the non-universality of his experience by mentioning his experience was in Prime Video and only for 8 months. I have no trouble believing that various pockets of the company found various different wrong ways to do things, I've seen some of those wrong ways myself. But taking a dependency on shared code (for better or for worse) rather than copying something yourself should not have been hard or infrequently done, and wouldn't be for most people using the standard tools. Generating code and having multiple downstream builds depend on that same generated code (e.g. the output artifact in the form of a .jar, in the case of Java) should also be very straightforward, though it was also possible (if a bad idea) for each consumer to run the same generator. Builds at Amazon were definitely not problem-free, but they were different problems that don't really resemble that description.