Thanks for those of you who came to the APIs conversation. If you want to continue the discussion, these are the questions I had on my cards.
- What’s the worst thing an API has done to you?
- What’s the first thing you check when evaluating the use of a new API?
- What’s the first thing you do when developing a new API?
- Do you approach developing APIs internally differently to one for the public?
- How do you make an API foolproof?
- How much structure should an API have? Does it need a contract? (see SOAP vs REST)
- How should you change an API?
- How should you retire an API?
- Which stakeholders need input to API upgrades and changes, and how do you engage them?
- How do you keep an API consistent if you grow it via tests?
- Do bug fixes necessitate a new version?
- How do you isolate your application from an insecure API?
- How do you isolate your application from an unreliable API?
Craig Nicol 
2 replies on “Usable APIs @CodeCraftConf ”
Great questions. IMPO, every team should know the answers (for their environment) to each of those questions. The answers themselves will vary, of course. The key element is to avoid the “I don’t know” situation. If one does not think about this ahead of time, a world of pain is almost inevitable at some point in the future.
LikeLiked by 1 person
[…] the Usable APIs guided conversation at CodeCraftConf, I wanted to capture some of the thoughts that came […]
LikeLike