Outline

From APIDesign

Revision as of 11:15, 21 June 2008 (edit) JaroslavTulach (Talk | contribs) ← Previous diff		Revision as of 11:34, 21 June 2008 (edit) (undo) JaroslavTulach (Talk | contribs) (→Part 1) Next diff →
Line 5:		Line 5:
	* [[Yet Another Design Book?]]		* [[Yet Another Design Book?]]
-	== Part 1 ==	+	== Part 1: [[Theory and Justification]] ==
-	* [[Theory and Justification]]
	* [[The Art of Building Modern Software]]		* [[The Art of Building Modern Software]]
	* [[The Motivation to Create an API]]		* [[The Motivation to Create an API]]

---

Revision as of 11:34, 21 June 2008

This is the content of the book.

Contents 1 Prologue 2 Part 1: Theory and Justification 3 Part 2 4 Part 3 5 Epilogue

Prologue

• Yet Another Design Book?

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

• 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

• 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

Epilogue

• The Future