News for hackers. Stuff that matters.
Re:Why I avoid SDKs in production by justinsb on Tuesday February 04, 2014 @11:26AM (#7178396)
Even if I don't use the SDK, I greatly appreciate when the same company that writes the API also builds an SDK.

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.

Re:Why I avoid SDKs in production by brandur on Tuesday February 04, 2014 @12:23PM (#7178816)
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.

[1] https://github.com/heroku/hk

Re:Why I avoid SDKs in production by arethuza on Tuesday February 04, 2014 @11:32AM (#7178455)
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.
Re:Why I avoid SDKs in production by dclara on Tuesday February 04, 2014 @02:24PM (#7179689)
Agree.
Re:Why I avoid SDKs in production by Jare on Tuesday February 04, 2014 @06:05PM (#7180858)
The best of the best: build your API/service, build an SDK for it, and then build tools to manage the service using the SDK and service themselves. Not always possible, but very desirable.