Paradoxes

From APIDesign

Revision as of 16:19, 1 October 2012 by JaroslavTulach (Talk | contribs)
Jump to: navigation, search

Soon after publishing Kant's Critique of Pure Reason, Kant realized that nobody is able to read it all and he released his Prolegomena to summarize and re-explain in more understandable style the thoughts of his Critique. I'd like my Paradoxes to do the same to TheAPIBook with the hope to attract wider audience to the topic of API design and convince part of them that it is worth to buy TheAPIBook.

Image:ParadoxesCover.png


There is nothing unnatural on paradoxes. Yet they attract human attention. They show where our expectation does not match reality. And that is exactly the place where we can learn something new. That is why let's concentrate on paradoxes.

A clasification of an API paradox is going to be 3 to 10 pages long and should contain:

  • name
  • description of the original expectation
  • explanation how it works in reality of API design
  • contra-opinion
  • advice what to do
  • warning what can go wrong, if you don't
  • link to additional sources of informations (books, chapters, URLs)

The list of paradoxes should mention following ones:

The above is your API design hand book reference. Deeper understanding of the topic can be obtained by reading TheAPIBook. Don't wait and get it here!

Personal tools
buy