It's a tool, our job is to collect tools in our toolbox and use them appropriately

TDD is great for when you want a really, really tight interface - whether it's your exposed surface to customers or you've got a lot of people working on something, it makes sense to write the standard and code to it, instead of documenting after the fact

Otherwise... Well, in practice it's an idiot proof methodology. That's useful, but it is a lot of work