'. '


From APIDesign

Revision as of 18:38, 19 September 2011 by JaroslavTulach (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

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 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:

Personal tools