'. '

Theory and Justification

From APIDesign

(Difference between revisions)
Jump to: navigation, search
Current revision (05:28, 29 July 2018) (edit) (undo)
 
(6 intermediate revisions not shown.)
Line 1: Line 1:
-
"In that case, developers using it will
+
Part 1 of the [[TheAPIBook]] is dedicated to [[Theory and Justification]].
-
create a feeling way different that conflicts with
+
-
the architect's intentions." does not make such sense.
+
-
--[[User:JesseGlick|JesseGlick]] 03:44, 25 March 2008 (UTC)
+
* 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]]
-
* There are no page numbers on this section
+
These observations are still valid even [[TenYears]] after [[TheAPIBook]] publication.
-
* Punc: Para 2: Delete comma after API - it's not necessary
+
-
* Content: Para 2: This is the perfect place to hint at some counter-examples of consistency in Java... unfortunately, I'm having some trouble coming up with examples right now!
+
-
* Spacing: Para "A Stable API" - is there an extra space before "API is stable" in italics?
+
-
* References: Para "If you believe" - "Part __" missing Part numbers (twice).
+
-
--[[User:Dmkoelle|Dmkoelle]] 20:50, 26 March 2008 (UTC)
+

Current revision

Part 1 of the TheAPIBook is dedicated to Theory and Justification.

These observations are still valid even TenYears after TheAPIBook publication.

Personal tools
buy