from what author is writing, he present his understanding of TDD as being "writing ALL the test before the implementation." And that would indeed be crazy. But TDD is not that. And again the author doesn't want to write unit test at the end of his project because he would have to "split the project into unit". Should your code be written using good practices you will be able to test it without having to split anything. Not being able to unit-test your code is a proof of bad design.