I'm overall sympathetic to the opinions in this article, but I think he's gone astray in the section "Complaint: TDD freezes the API too early". One of the idea

I'm overall sympathetic to the opinions in this article, but I think he's gone astray in the section "Complaint: TDD freezes the API too early". One of the ideas of TDD is that writing tests guides the API, rather than forcing you into an API. That is, if you write tests based on the actual business requirements, and write them first, that process will lead you to discover the best design of the API. Note that for this to work, you have to be writing tests based on the real use requirements. Simple synthetic unit tests will not help you here, and may lead to exactly the problem the author is complaining about.