API Days Paris just finished this Thursday, leaving me both sad and exhausted and happy and full of energy.

Sad and exhausted because this awesome and intense API conference is over.
Happy and full of energy because this awesome and intense API conference exists.

When watching a movie, have you ever noticed how characters interact with computers? If someone wants to destroy a computer, what does he or she smash?
The computer’s screen…

I’ve been interviewed by Lexy Mayko from API2Cart, you can read the interview here.

If you want to know why an existing IS is not a good API, you should read my last post on Nordic APIs blog How to Provide APIs With an Existing Information System.

My other self Arnaud Lauret writes about APIs too. This week you can read Should Every Company Consider Providing an API? on Nordic APIs blog.

A few weeks ago I’ve seen an interesting flock of tweets initiated by this question:

This question and the tweets that followed put my brain on quite an animated discussion…

When I look at hypermedia media-types and API definition languages I feel that the frontier between data and documentation is becoming thinner as my knowledge of the API world grows and as the API world evolves.

As I was writing my HAMM and ways of API smartness posts, I wanted more. As I was discussing with smart people about APIs, I wanted ever more. I want to delve deeply into the API ways.

An API must be smart to ensure that consumers will want to use it and remain dumb when they consume it.

Hypermedia is not only a conceptual and philosophical subject of interesting and animate debates among the API community, it’s also a concrete solution we can use to cover concrete needs. In this second part of hypermedia API maturity model (HAMM) series I will talk about my own experience to expose two missing (in my humble opinon) notions in common implementations and include these missing links in an updated version of the HAMM.