This is an actual advantage of test-driven design; unit tests are bad for their stated purpose (they aren't good at testing things and are expensive to maintain), but because they make you write clients for your APIs before implementing them, you actually have some hope of knowing they're useful.

I think you should consider writing unit tests before coding but then delete them and then write regression tests after. Though, haven't tried this approach yet.