[duped]

At a startup, you're going to rewrite you're entire product multiple times because you don't know what it actually is when you start. Your job is to get shit done as fast as possible to prove out the idea before you run out of money, and to make a demo that can convince people to give you money to actually build it right with all the lessons learned.

Bazel gets in the way of this use case. It will help your small team not break each other's builds. But you'll burn a salary on someone as the "Bazel person," they're going to write a bash script or make file for everyone else to use anyway, and when you inevitably rewrite everything from scratch the third time all their work is going to be for nothing and they'll spend days getting it back.

Just write a bash script or python script that does what you need for today, and plan to deal with it later. The only thing startups can afford is tech debt.

Another way of thinking about this is that your product is the software and not the software to build the software. Don't waste time thinking about the tools.

[dlahoda]

I share my bash files glued and hosted by nix shell, so that they work on other machines and importable. So nix is bash package manager and host.