Yikes hard no on this. I see the point it's trying to make, but, anecdotally, for me, it's very much the case that: 1. Writing tests is a forcing function on w

Yikes hard no on this. I see the point it's trying to make, but, anecdotally, for me, it's very much the case that: 1. Writing tests is a forcing function on writing better code. 2. Better code is significantly more maintainable and adaptable 3. Tests are a cheap way to invoke your code to just simply see it run. Definitely cheaper than you clicking/tapping around your product. 4. Tests suites are an extremely effective way to coordinate work with (at least) yourself. Pending and failing tests make for a great TODO list. It is absolutely possible - and easy - to write tests that get in the way. It's also easy (once you find The Way) to write tests that a force multiplier. It is a combination of writing both good code, and good test code.