[tieTYT]

OK but after you "Fake It Until You Make It" and you have to add a new feature to that class structure, aren't you just going to start over with all the failures he brings up?

---------

I haven't designed code the way he's advocating, but I have attempted TDD by starting with the leaves first. Here are the downsides to that:

1) Sometimes you end testing and writing a leaf that you you don't end up using/needing.

2) You realize you need a parameter you didn't anticipate. EG: "Obviously this patient report needs the Patient object. Oh crap I forgot that there's a requirement to print the user's name on the report. Now I've got get that User object and pass it all the way through".

Maybe these experiences aren't relevant. As I said, I haven't tried to "Fake It Until You Make It".

[s73v3r]

"1) Sometimes you end testing and writing a leaf that you you don't end up using/needing."

So what? Just delete it. Your version control system should have a record of what it was if you end up needing to go back to it.