I agree! We've been building a CLI that uses an SDK [1] against our new API and so far it's been tremendously helpful in identifying bugs and other problems -- if we hadn't gone through that exercise then we would have inadvertently shipped some of those issues out to our users.
I think SDKs are great. The intent of the article was to document why I will sometimes opt out of using them.
It's also good to have a test client application that the service provider supplied to be able to demonstrate that problems are with the service rather than with the client code.
Agree.
APIs which don't also maintain SDKs - in my experience - don't understand the cost of making breaking changes, and aren't as 'nice' to consume. When the SDK is built, these issues are discovered: I appreciate that it's not me that has to go through those pains.