The article has two parts: a refresher of what TDD is and what benefits it has, and an argument with some fictious TDD haters. I don't see much in the way of c

The article has two parts: a refresher of what TDD is and what benefits it has, and an argument with some fictious TDD haters. I don't see much in the way of confessions, nor do I understand who their discussion on why "some hate TDD" is aimed at? A better approach is to highlight cons of TDD and then argue why they still don't affect ROI (iow, pros outweigh the cons). FWIW, I love TDD in teaching people to get all the benefits article brings out. But today, I can write code that has all the properties of TDD-produced code without going through TDD. I believe you still need to go through the exercise to learn to write well structured, testable code (it also teaches you an important thing: refactoring is a day-to-day thing in software engineering, not some arcane tech-debt-resolution tool).