34 years here, from embedded to suites of servers and transcontinental client-server suites.
As with all but the most fanatic responses I get to these articles, you are arguing for testing itself, not for TDD. I'm all for testing. I'm particularly for regression testing. I've spearheaded its introduction at several companies.
I think TDD is complete bullshit. The fundamental idea, writing tests before code, I have nothing more to say about. It's dumb, period.
I dislike unit testing, it's a lot of work and is rarely anywhere near worth it, and it involves compromising a code design to make it "testable."
But what really drives my opposition is what the kids are saying; developers should be solely responsible for their own testing, unit tests are the documentation, and the worst, only TDD is programming, anything else is illegitimate. These people are idiots.
The reason for this nutty shift of emphasis to testing is that nobody can concentrate, they write lousy code, and since they have never known focus they think the answer is tons of tests. It's still lousy code.