3 ms·
Because the focus should be on correct software and there's a sunk cost fallacy in arguing that you're almost there anyways so why not just buy in to TDD for so
by lllr_finger 8y ago
Because the focus should be on correct software and there's a sunk cost fallacy in arguing that you're almost there anyways so why not just buy in to TDD for some purported value.
It might help some developers, but it is not a panacea and should not be promoted as such.
- voodootrucker 8y agoSometimes I like to rely on gut-feelings while coding. Ever filled in that user-signup form for the thousandth time? Ever start with nice input: John Doe, 555 fake St Then after the 500th time you are just inputing: aaa abc wsdfg And clicking "sign up"? That is the point you should know in your heart: "I missed writing an automated test somewhere". If you can't relate to the above experience (and have never had your code broken by a coworker), then maybe for some reason you are in a position where you're fine without TDD.
- crdoconnor 8y agoThere's also the cost of building the automation to bear in mind https://xkcd.com/1319/ https://xkcd.com/1319/
- lllr_finger 8y agoThis implies that a) you can't rely on "gut feeling" without TDD and b) that you don't write tests without TDD. Both of which are incorrect.