Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses

Re: On Interfaces and APIs

by adrianh (Chancellor)
on Jun 05, 2006 at 13:34 UTC ( #553593=note: print w/replies, xml ) Need Help??

in reply to On Interfaces and APIs

This meditation reports the interface and API design references I've found useful and further presents some general interface design ideas and checklists in the hope that they may prove useful -- and that they might be improved upon by your insightful feedback.

For me the two greatest tools for interface/API design I've come across are Test Driven Development and Refactoring. Growing effective interfaces/APIs over time, rather than designing them all up front, is a stupidly useful technique.

API Design Checklist

Alan Shalloway and Ron Jeffries' list of features for a simple design is one that resonates for me:

  1. Runs all the tests.
  2. Contains no duplication.
  3. Expresses all the ideas you want to express.
  4. Minimizes classes and methods.
The three greatest experts in the human side of interface design that I'm aware of are: Donald Norman, Jakob Nielsen, Larry Wall

I know lots of people who would argue with Nielsen's place on that list - especially with the absence of Alan Cooper!

While Larry is a hugely talented programming language designer (in my opinion anyway :-) I'm not entirely convinced that this necessarily maps onto "human" interface design in general.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://553593]
[erix]: ( hm. that doesn't make sense really -- infallibility is a 19th century invention, the Inquisition quite a bit earlier )
[Your Mother]: The Inquisition? What a show!

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (5)
As of 2017-01-18 00:00 GMT
Find Nodes?
    Voting Booth?
    Do you watch meteor showers?

    Results (159 votes). Check out past polls.