Both Bazel and Nix have some powerful features to them. (Though, oddly, they don't quite mix). I think they both also have downsides where, if your software do

Both Bazel and Nix have some powerful features to them. (Though, oddly, they don't quite mix). I think they both also have downsides where, if your software does things in ways they don't like, it's difficult to use them. -- And, your team is going to have a tough time using the tool without sufficient expertise. As I understand it, Bazel's emphasis is more about compilation, where the big win is building projects where you've got a team big enough (& a project complex enough) that dealing with Bazel saves more time than it costs. Whereas with Nix.. I think one good use case is "declare & lock the dependencies for this toy project", which then allows picking the project up without having to update your code following updates to the system package manager.