He's probably not a NULL fan, but he is like a broken clock always showing TDD. At least if one recommended a "testing strategy", with multiple types of tests

He's probably not a NULL fan, but he is like a broken clock always showing TDD. At least if one recommended a "testing strategy", with multiple types of tests, checkpoints, etc it would be somewhat acceptable. Quality assurance is a process consisting of several parts, among them compilers with powerful type systems, static and dynamic verifiers, coding standards and code reviews, model-based code generation and yes, multiple types of testing. How can all that be replaced with TDD? Anyone working on anything that has to be high quality would know it's ridiculous.