>TDD requires you to commit to an API before you fully understand what you want from it. Unless you're running a spike that's actually a good idea. TDD doesnt

>TDD requires you to commit to an API before you fully understand what you want from it. Unless you're running a spike that's actually a good idea. TDD doesnt force a complete commitment, but by forcing you into a semi-commitment to your API before building it it often ends up drawing out questions and critical assumptions about the API design which helps prevent a lot of design and requirements mistakes up front. It's an instance of shift left - "testing" your api before even writing a line of code. So, what youve characterized as a bad thing is actually a very good thing, provided you're TDD'ing at a high level.