TenYears

From APIDesign

Ten years ago, on July 29, 2008, TheAPIBook was published. Isn't that a date to remember and celebrate? Yeah, may be it is. It certainly deserves at least a little note. Thus let me write one...

TBD

The language that I used for most of the examples, Java, is no longer as popular as it used to be. It is no longer taught at basic university courses. It is no longer the choice of those who want to use good technology with all its three essential components (coolness, time to market and cost of ownership). Does that mean TheAPIBook advises are no longer valid? Not that all! I always expected Java to evolve into something different - the language was just a tool - the core ideas still remain valid.

Kidnapped by REST guys. TBD.

TwoYearsWithTruffle - designing API as a service.

On the other hand, the feeling I described in the MidlifeCrisis essay are still valid. The impact of TheAPIBook should have been bigger. It is clear there are a lot of people attempting to design an API that would benefit from some of TheAPIBook advises.

Don't you need a skilled API designer? Don't you want to improve your API Design skills with a funny game-like training? Talkback to me. That'd be the best way to celebrate the 10th anniversary of TheAPIBook!