The Motivation to Create an API

From APIDesign

(Difference between revisions)
Jump to: navigation, search
(New page: More on topic than the previous chapter. Still quite a lot of preachy text without much in the way of specific information or advice. Could likely be trimmed down quite a bit. --~~~~)
Current revision (20:58, 13 August 2008) (edit) (undo)
(Have You Ever Wondered...?)
 
(3 intermediate revisions not shown.)
Line 1: Line 1:
-
More on topic than the previous chapter.
+
== Have You Ever Wondered...? ==
-
Still quite a lot of preachy text without much in the way of specific information or advice.
+
-
Could likely be trimmed down quite a bit.
+
-
--[[User:JesseGlick|JesseGlick]] 22:38, 26 March 2008 (UTC)
+
Maybe you are asking yourself: "Why should I slow myself down by creating an API? Is not that more work?". In the [[The Motivation to Create an API|second chapter]] of [[TheAPIBook]] I describe that overall, it is not more work. Moreover I also reveal that even if you try, you cannot live without APIs. APIs are everywhere, even in in-house systems. In the world of [[DistributedDevelopment]] they become inevitable.

Current revision

Have You Ever Wondered...?

Maybe you are asking yourself: "Why should I slow myself down by creating an API? Is not that more work?". In the second chapter of TheAPIBook I describe that overall, it is not more work. Moreover I also reveal that even if you try, you cannot live without APIs. APIs are everywhere, even in in-house systems. In the world of DistributedDevelopment they become inevitable.

Personal tools
buy