> A company of 100 engineers should probably have 10-20% of the team allocated to just internal tools and making things go faster. But beware of Jevons paradox

> A company of 100 engineers should probably have 10-20% of the team allocated to just internal tools and making things go faster. But beware of Jevons paradox. Say that eg. a software project has 10 developers, and each build takes ~15 minutes. Most developers would take at least some care to check their patches, understand how they work etc, before submitting. And then discuss follow-on steps with their team over a coffee. Now imagine near-instant builds. A developer could copy-paste a fix & hit "submit", see "oh that doesn't work, let's try something else", and repeat. You'll agree that probably wouldn't help to improve the codebase quality. It would just increase the # of non-functional patches that can be tested & rejected in a given time span. In other words: be careful what you wish for.