I've always found TDD to be best when used as a learning tool. Not learning how to write better tests, but in learning to write better code. Looser coupling, be

I've always found TDD to be best when used as a learning tool. Not learning how to write better tests, but in learning to write better code. Looser coupling, better designed APIs and signatures were some key areas where I found improvement along with finding that having tests as I wrote meant that I could use a rapid-prototyping style for every part of the code, iterating on the code+tests together so I run it whenever I want with whatever inputs I want in an easily repeatable way. TLDR; TDD makes you a better programmer, even if you don't use it long term.