Outline
From APIDesign
(Difference between revisions)
(→The content of TheAPIBook) |
(→Part 2: Practical Design) |
||
| Line 17: | Line 17: | ||
* Chapter 6: [[Code Against Interfaces, Not Implementations]] | * Chapter 6: [[Code Against Interfaces, Not Implementations]] | ||
* Chapter 7: [[Use Modular Architecture]] | * Chapter 7: [[Use Modular Architecture]] | ||
| - | * Chapter 8: [[Separate APIs for | + | * Chapter 8: [[Separate APIs for Clients and Providers]] |
* Chapter 9: [[Keep Testability In Mind]] | * Chapter 9: [[Keep Testability In Mind]] | ||
* Chapter 10: [[Cooperating with Other APIs]] | * Chapter 10: [[Cooperating with Other APIs]] | ||
Current revision
Contents |
The Outline of TheAPIBook
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
- Chapter 5: Do Not Expose More Than You Want
- Chapter 6: Code Against Interfaces, Not Implementations
- Chapter 7: Use Modular Architecture
- Chapter 8: Separate APIs for Clients and Providers
- Chapter 9: Keep Testability In Mind
- Chapter 10: Cooperating with Other APIs
- Chapter 11: Runtime Aspects of APIs
- Chapter 12: Declarative Programming
Part 3: Daily Life
- Chapter 13: Extreme Advice Considered Harmful
- Chapter 14: Paradoxes of API Design
- Chapter 15: Evolving the API Universe
- Chapter 16: Teamwork
- Chapter 17: Using Games to Improve API Design Skills
- Chapter 18: Extensible Visitor Pattern Case Study
- Chapter 19: End Of Life Procedures
Follow
