Three Rules for Designing a Go SDK Other People Will Actually Use

I publish open-source Go libraries. Not many people use most of them, and I’ve spent a fair amount of time trying to figure out why. Some of it is distribution. Some of it is the unsexy truth that nobody needed the thing I built. But a real chunk of it — bigger than I want to admit — is that the API was designed for me , the author, and not for the developer arriving cold from a Google search at 2am with a deadline. This post is three rules I now apply when designing a Go SDK. They come from publishing post