#business #programming # [[Epistemic status]] #shower-thought # Automated testing in high velocity environment #to-digest I don't know what the common agreed way to call tests in [[Programming|programming]], for me it's just automated tests, i.e. tests done by machines rather than humans. In high velocity environment such as start-ups, where you have to build fast to reach [[Product market fit]] or to keep your product aligned with the market, it can be tempting to skip the testing part, but if you do, you will soon discover that preventing is better than healing and that we're intuitively blind to [[Philosophy/Rationality/Models/Black Swan|Black Swan]]s. So my take is that, especially in early stage start-ups, it can be a struggle to balance speed and tests. Because implemented automated test can be costly in time, especially for things like UI, integration, things that need multiple distributed components. Paul Graham in Hackers & Painters seems to advice to not mind too much with minor bugs/features and let the user discover it, then fix quickly (at least it's what they done in ViaWeb that became Yahoo store). Why not, in B2C, maybe less in B2B because you have less users and need to be highly respectful of your user, but in any case you want to ensure the building blocks works, the major features, the foundations of the house of cards. ![[house-of-cards.png]] Implement automated testing for major features! # External links