To me, TDD means: 1. No functionality is coded without a failing test. 2. Only code the minimum functionality to make the test pass. It does not mean 'test m

To me, TDD means: 1. No functionality is coded without a failing test. 2. Only code the minimum functionality to make the test pass. It does not mean 'test more' or 'write tests'. So I'm not sure more than 10% of this 'defence' bolsters the method at all. Seems like the normal rhetorical bait and switch - you pretend that your opponent is criticising testing and respond by defending some more or less vague notion of tests, with no substantive defence of TDD beyond "you didn't try hard enough." The example of the pacemaker, for example, has no relevance to TDD whatsoever.