Outline
From APIDesign
(Difference between revisions)
(→Part 3) |
(→Part 3: Daily Life and the Future) |
||
| Line 24: | Line 24: | ||
* [[Declarative Programming]] | * [[Declarative Programming]] | ||
| - | == Part 3: Daily Life | + | == Part 3: Daily Life == |
* [[Extreme Advice Considered Harmful]] | * [[Extreme Advice Considered Harmful]] | ||
Revision as of 11:35, 21 June 2008
This is the content of the book.
Contents |
Prologue
Part 1: Theory and Justification
- The Art of Building Modern Software
- The Motivation to Create an API
- Determining What Makes a Good API
- How to Check the Quality of an API
- Ever Changing Targets
Part 2: Practical Design
- Do Not Expose More Than You Want
- Code Against Interfaces, Not Implementations
- Use Modular Architecture
- Separate APIs for Client APIs and Support APIs
- Keep Testability In Mind
- Cooperating with Other APIs
- Runtime Aspects of APIs
- Declarative Programming
Part 3: Daily Life
- Extreme Advice Considered Harmful
- Paradoxes of API Design
- Evolving the API Universe
- Teamwork
- Using Games to Improve API Design Skills
- Case Study of Writing the Extensible Visitor Pattern
- End Of Life Procedures
Follow
