The Failures of "Intro to TDD"
The more I try to explain TDD, the more I realize that some of my favorite concepts, like the ability to mock functionality of an external process because the details of that process should be irrelevant...is just beyond the grasp of most beginners. That is, I thought/hoped that TDD would necessarily force them into good orthogonal design, because it does so for me...but it seems like they have to have a good grasp of that <i>before</i> they can truly grok TDD.<p>Has anyone else solved this chicken and the egg dilemma?