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
- CFML on Google App Engine for Java - April 10, 2009
- 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
- Docker Container exited with code 137
- Why is my cron.daily script not running?
- Announcing FuseGuard Version 3
- CFSummit 2017
- Java Unlimited Strength Crypto Policy for Java 9 or 1.8.0_151
- Java 9 Security Enhancements
- Upcoming CFML Conferences in April 2017
- CFSummit 2016 Slides