In Proceedings of the 2006 OOPSLA workshop on eclipse technology eXchange , Dr Bloch gives some maxims for API design (an accessible copy of them is here).

While some of the advice seems to be in the category of "Don't eat toads", e.g., "Overload with care", most of them seem pretty sensible, and applicable to just about any language.

emc

At that time [1909] the chief engineer was almost always the chief test pilot as well. That had the fortunate result of eliminating poor engineering early in aviation.

—Igor Sikorsky, reported in AOPA Pilot magazine February 2003.
  • Comment on Joshua Bloch's "How to Design a Good API and Why it Matters"

Replies are listed 'Best First'.
Re: Joshua Bloch's "How to Design a Good API and Why it Matters"
by eyepopslikeamosquito (Archbishop) on Dec 20, 2006 at 20:09 UTC

    I discuss Dr Bloch's seven characteristics of a good API, along with Dr Conway's seven S.A.T API design tips, in: