The article appears to be a tongue-in-cheek argument for Test Driven Design, but it does not give a very balanced view of the pro's and con's. I have been in t

The article appears to be a tongue-in-cheek argument for Test Driven Design, but it does not give a very balanced view of the pro's and con's. I have been in teams that tried to use it. Our general conclusion was that it invites you to make implementation decisions too soon, before you have good overview of the problem domain. So many tests turned out be tests of an implementation instead of tests of a specification.