How to Design a Good API and Why it Matters
From Technical Presentations
| |
| Presenter(s): | Joshua Bloch, Google |
|---|---|
| Where: | Library-Centric Software Design 2005 (description) |
| When: | October 16, 2005 |
| Topics: | API |
| Download: | |
[edit] Description
Presentation about API design principles and importance of API design for internal and external use.
[edit] Quotes
- Public APIs are forever - one chance to get it right
- Good code is modular–each module has an API
- Thinking in terms of APIs improves code quality
- Easy to use, even without documentation
- Don’t let implementation details “leak” into API
- Make classes and members as private as possible
Facts about How to Design a Good API and Why it MattersRDF feed
| Date | October 16, 2005 + |
| PDF Document URL | http://lcsd05.cs.tamu.edu/slides/keynote.pdf + |
| Presented at | Library-Centric Software Design 2005 + |
| Presenter | Joshua Bloch + |
| Presenter Company | Google + |
| Screenshot | How to Design a Good API and Why it Matters.jpg + |
| Topic | API + |


