TDD can give you higher quality code... which really only delays the inevitable refactor once the true specs and user needs are discovered. I usually write quic

TDD can give you higher quality code... which really only delays the inevitable refactor once the true specs and user needs are discovered. I usually write quick and dirty implementations (after doing some API design on paper) and see if it has sticking power... then write tests and often times rewrite the code entirely in TDD style once more is understood about the problem.