I'm sure everyone who's heard of TDD has played through similar scenarios in their head. But even the most evangelized TDD proponents almost always end their t

I'm sure everyone who's heard of TDD has played through similar scenarios in their head. But even the most evangelized TDD proponents almost always end their talks with addressing the fact that some code can't or shouldn't be tested. And I think the fact that they wait until the end to say things like that turns a lot of people off of TDD. I have used TDD to develop libraries and services, and it works really well. You have to write code to test your work anyway, so it's not really a lot of extra work. And writing the tests first really helps (me) think more about how the user will use my library/service. I, in no way, think that EVERYONE should ALWAYS use it, in the way that a lot of people have preached. But it is frequently a good tool for the job, and I think a lot of people have abandoned the idea because of the way a few bad actors have presented it.