'. '

Yet Another Design Book?

From APIDesign

(Difference between revisions)
Jump to: navigation, search
Current revision (08:00, 6 June 2011) (edit) (undo)
(→Versioning)
 
(9 intermediate revisions not shown.)
Line 1: Line 1:
-
* Is there a space before [GoF]?
+
== [[Have You Ever Wondered]]...? ==
-
* Notice [book.effective] towards end of paragpraph
+
-
* Grammar: Page 1, 3rd paragraph, change to "Despite that, the API clients that compiled their code then are still able to execute their code TODAY, even with the latest versions of those libraries."
+
-
* Punctuation: Page 1, Paragraph 4 - should use dash instead of comma between "the code, that is"
+
-
* Spelling: Page 1, Para 4 - "Overtime" should be "Over time" ("Overtime" is what you get paid when you work too many hours)
+
-
--[[User:Dmkoelle|Dmkoelle]] 20:12, 26 March 2008 (UTC)
+
-
* I'd love to have one extra historical tidbit in the introduction somewhere: what's the origin of the term API? I first remember hearing it in the early 90's, but it's possibly older than that. I spent some time searching using Google, but came up empty-handed. Can you research this?
+
Have you read many books about design? Have you read some? Do you think you know everything about proper design? Are you asking why bother with yet another design book? This ''prologue'' shows you that you should care. Most design books are written for "in-house" development, however with the rise of code reuse caused mostly by proliferation of various open source libraries and frameworks, we are entering world of [[distributed development]]. The new coding life style needs slightly different designing approach. After reading "prologue", you'll find out that you need [[TheAPIBook]] if you want to code software for the 21st century.
-
* (spelling) I'd prefer seeing a hyphen in the term "object-oriented" throughout the text.
+
-
* (spelling) paragraph 3: "decade old" => "decade-old"
+
-
--[[User:AdamDingle|AdamDingle]]
+
 +
=== Versioning ===
-
* Third paragraph makes claims about backwards compatibility, which I mostly agree with. However, I got started with platform development just after 4.0 was released and tried to follow examples from the NetBeans Definitive Guide. I remember vividly that I could not get anything to work because of the NoClassDefFound errors on TopManager, so I would recommend making those claims a little less strong in case others remember as well.
+
The preface also contains a fable about the perception of the world evolved from ancient Greek's over [[wikipedia:Newton|Newton]], [[wikipedia:Einstein|Einstein]] to today. The primary motivation to create such metaphor was to explain that one can even change rules over a time, but it is important to do that in a [[BackwardCompatibility|backward compatible]] way - e.g. in a way that nobody notices that the rules changed. Maybe the physics really changed between 17th and 19th century? Maybe the God was just trying to tease mankind?
-
--[[User:TomWheeler|TomWheeler]]
+
-
 
+
-
* Grammar: last paragraph, your tenses are mixed. I would suggest: "Since then, I've known the need for information relating to API design is real. The memory of that presentation has encouraged me whenever I've begun to lose motivation while writing this book. It has helped to remind me that the rules for proper API design that we've discovered need to be documented.
+
-
--[[User:RichUnger|RichUnger]]
+

Current revision

Have You Ever Wondered...?

Have you read many books about design? Have you read some? Do you think you know everything about proper design? Are you asking why bother with yet another design book? This prologue shows you that you should care. Most design books are written for "in-house" development, however with the rise of code reuse caused mostly by proliferation of various open source libraries and frameworks, we are entering world of distributed development. The new coding life style needs slightly different designing approach. After reading "prologue", you'll find out that you need TheAPIBook if you want to code software for the 21st century.

Versioning

The preface also contains a fable about the perception of the world evolved from ancient Greek's over Newton, Einstein to today. The primary motivation to create such metaphor was to explain that one can even change rules over a time, but it is important to do that in a backward compatible way - e.g. in a way that nobody notices that the rules changed. Maybe the physics really changed between 17th and 19th century? Maybe the God was just trying to tease mankind?

Retrieved from "http://wiki.apidesign.org/wiki/Yet_Another_Design_Book%3F"
Personal tools
buy