Outline
From APIDesign
(Difference between revisions)
(→Part 3: Daily Life and the Future) |
(→Part 1: Theory and Justification) |
||
| Line 7: | Line 7: | ||
== Part 1: [[Theory and Justification]] == | == Part 1: [[Theory and Justification]] == | ||
| - | * [[The Art of Building Modern Software]] | + | * Chapter 1: [[The Art of Building Modern Software]] |
| - | * [[The Motivation to Create an API]] | + | * Chapter 2: [[The Motivation to Create an API]] |
| - | * [[Determining What Makes a Good API]] | + | * Chapter 3: [[Determining What Makes a Good API]] |
| - | * | + | * Chapter 4: [[Ever Changing Targets]] |
| - | + | ||
== Part 2: Practical Design == | == Part 2: Practical Design == | ||
Revision as of 08:24, 27 June 2008
This is the content of the book.
Contents |
Prologue
Part 1: Theory and Justification
- Chapter 1: The Art of Building Modern Software
- Chapter 2: The Motivation to Create an API
- Chapter 3: Determining What Makes a Good API
- Chapter 4: 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
