On API Usability

style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> href="http://blogs.gotdotnet.com/stevencl/">Steven talks about href="http://blogs.gotdotnet.com/stevencl/permalink.aspx/d9a60366-19f4-4eda-a99c-636546d7f7b4">API
Usability and even asks you href="http://blogs.gotdotnet.com/stevencl/permalink.aspx/2fa015b9-439f-4c67-a38c-15afbaa2db5a">to
sign up to go to API usability tests. 
He makes a point that I use often… style="mso-spacerun: yes"> I call it the “design in reverse”
principle.  Before you write
any of your framework, write a simple app that uses it… What are the three lines
of code it takes to perform the common task? style="mso-spacerun: yes"> Then just build the API to make that
possible. "urn:schemas-microsoft-com:office:office" />

Comments (1)

  1. Tor says:

    That’s one of the nice aspects of test first development; you usually come up with better APIs because you have designed them "in reverse," in the unit tests.

    Speaking of which, it’d be very interesting if you could explain to which extent your group is unit testing the Framework when designing new APIs.

Skip to main content