Wings of desire – future-proofing software architecture

(Note: this was originally posted on a since-archived company blog, so apologies for those who’ve read it before) Architects are never quite sure how their buildings and common spaces are going to be used once real people move in. Just as software developers are never quite sure how their software is going to be used. … More Wings of desire – future-proofing software architecture

Usable APIs follow-up

Following the Usable APIs guided conversation at CodeCraftConf, I wanted to capture some of the thoughts that came out. Starting an API (as a user or a developer) Does the API documentation include examples of usage (i.e. have they thought about the client) How mature is the API? How well maintained is it? How long … More Usable APIs follow-up

Developers are Users Too : Why the User Experience of Your API sucks #yourapisucks

Many thanks to those of you who came along to my talk on why your API sucks. There were some great discussions during and after, and I hope I’ll be seeing slightly fewer reasons to tear my hair out in the near future. A few things that people mentioned that I want to discuss again, … More Developers are Users Too : Why the User Experience of Your API sucks #yourapisucks

Your API sucks : foolish inconsistency

There are many ways that an API can be inconsistent. Different methods can follow different conventions, one method may have different results, or maybe a change introduces inconsistency between versions. Spatial Inconsistency When calling 2 different methods in what appear to be related domains require 2 very different calls and get 2 very different results. … More Your API sucks : foolish inconsistency