>at least for anything actively being used and updated
This implies that the strength of the tests appears when it's modified?
Like the article says, TDD doesn't own the concept of testing. You can write good tests without submitting yourself to a dogma of red/green, minimum-passing (local-maximum-seeking) code. Debating TDD is tough because it gets bogged down with having to explain how you're not a troglodyte who writes buggy untested code.
And - on a snarkier note - this is a better argument against dynamic typing than for TDD.
This implies that the strength of the tests appears when it's modified?
Like the article says, TDD doesn't own the concept of testing. You can write good tests without submitting yourself to a dogma of red/green, minimum-passing (local-maximum-seeking) code. Debating TDD is tough because it gets bogged down with having to explain how you're not a troglodyte who writes buggy untested code.
And - on a snarkier note - this is a better argument against dynamic typing than for TDD.