Some features that I find elegant in Bazel, but probably don't have that much impact on small projects/teams is the whole concept of "visibility"[1]. For large

Some features that I find elegant in Bazel, but probably don't have that much impact on small projects/teams is the whole concept of "visibility"[1]. For large projects, being able to control who can take a dependency on your code is really nice. This mixes really well with automatically adding Required reviewers in Pull Requests based on which folder gets modified [2][3]. [1] https://docs.bazel.build/versions/master/be/common-definitions.html#common-attributes https://docs.bazel.build/versions/master/be/common-definitio... [2] https://docs.microsoft.com/en-us/azure/devops/repos/git/branch-policies?view=vsts#automatically-include-code-reviewers https://docs.microsoft.com/en-us/azure/devops/repos/git/bran... [3] https://help.github.com/articles/about-codeowners/ https://help.github.com/articles/about-codeowners/