pf » How to Design a Good API and Why it Matters
March 20, 2006
How to Design a Good API and Why it Matters


Joshua Bloch has a good presentation outline called How to Design a Good API and Why it Matters. Joshua is a Principal Software Engineer for Google, before that an architect in Sun's Core Java Platform Group (he designed several of the standard java API's). Josh also wrote Effective Java.
Here are a few points from the presentation that I found interesting...
- If you program, you are an API designer
- If you keep the spec short, it?s easy to modify
- API Should Do One Thing and Do it Well
- API Should Be As Small As Possible But No Smaller
- Names Matter - API is a Little Language
- Fail Fast - Report Errors as Soon as Possible After They Occur
Permalink | Add Comment |
add to del.icio.us
| Tags: api, design, architecture, bloch, google, sun, java
add to del.icio.us
| Tags: api, design, architecture, bloch, google, sun, java
Related Entries
- Cheat Sheet Roundup - Over 30 Cheatsheets for developers - September 1, 2005
- REST vs SOAP Web Services - August 3, 2005
- Designing from the outside in - April 27, 2005
- Google Code - March 17, 2005
Trackback Address: 551/672ADC7F165719F3E80AB2E9F3BF0527
Spell Checker by Foundeo
- Dear SQL Server Enterprise Manager Developer
- PostalMethods - Web Service for Snail Mail
- Mastering CFQUERYPARAM
- Google Code Search for ColdFusion
- Speaking at CFUNITED 2008
- Getting ColdFusion SQL Statements from SQL Server Trace
- CFSCRIPT Cheatsheet
- 3 New Image Effects for ColdFusion 8
Subscribe to my RSS Feed:
RSS
RSS
Pete Freitag is a software engineer, and web developer located in









