With constrained resources, you realize the value of the marginal hour very quickly. You can’t just goof around with science projects, open-ended explorations, and play time with new whiz-bang technology. Instead, you have to deliver real value, real soon. Otherwise the project is simply going to languish as it loses out to the “real work” of paying clients.
For us, that meant we had to build something for ourselves, something we needed, and something that was valuable enough that we’d assign resources to it over getting billable hours done. It meant racing to running software, deciding that a lot of stuff just doesn’t matter, and building half, not half-assed.
The initial start of extreme resource starvation lead to many of our thoughts on software development. It also lead me to believe that the best work is done when there’s not enough time, not enough money to do it “right”.
Doing it right is a pie in the sky. It’s a misnomer for second-system syndrome and it’s never going to happen anyway. So stop aiming for perfect, start aiming for good enough.
[Always a good reminder.]
Source: SIGNAL VS. NOISE
