I mean I get that it’s supposed to be a provocative statement, but it really is just a very shallow, false dichotomy. If writing tests slows you down -this much

I mean I get that it’s supposed to be a provocative statement, but it really is just a very shallow, false dichotomy. If writing tests slows you down -this much- then yes, you’re spending too much time writing tests. But they often save you time, both as a tool for modeling your thinking about the software (being explicit about how it should work) and also in, yes, testing it. Here’s my provocation: If you don’t know how to tell the difference and make the frankly boring judgement call of whether or not you’re wasting time writing some tests, then maybe don’t work on software. “Pivot”, as they say.