Posts Tagged: dx

Writing Microservices in Go Part II – When Not to Use Go

In Writing Microservices in Go pt. 1, we highlighted a whole bevy of reasons for coding in Go, the novel, forward-thinking language developed at Google. However, there are two sides to every coin; the benefit of a language or system can often be a drawback in other use cases, and a host of hidden faults can make what was once an awesome idea significantly less awesome. Read more

Functional vs. Useful: What Makes a Useful API?

It’s a very easy thing to say that if an API exists, then it’s useful. After all, if a developer creates an API, they must have created it for some purpose. However, what is functional isn’t always useful, and conversely, what is useful isn’t always functional. Read more

Reactions to Using The Twilio API

Missed Part One? Check out our Twilio API integration walkthrough here.

Within the API space Developer Experience (DX) matters more than ever. The best way to gauge an API’s usability is through actual implementation with an integration.

In a previous article Building a Better Voice Mail Using Twilio, we consumed the Twilio API to implement a voice mail project and to better understand how a developer interacts with their API. Read more

API Strategy Must Balance Developer and User Experience

We recently talked about how people and software must change if you are to grow your API. We also looked at a case study of Apple which highlighted the importance of a UX-focused API strategy. The Apple example is interesting because it shows that you must strive to delight your API developers’ consumers as if they were your own. Read more