How to Check the Quality of an API
From APIDesign
(Difference between revisions)
AdamDingle (Talk | contribs)
(New page: * p 35: The paragraph beginning "The definition and measurement of beauty" wanders off into philosophy a bit. I'd shorten this paragraph, perhaps keeping only the last two sentences. * p ...)
Next diff →
Revision as of 01:20, 28 March 2008
- p 35: The paragraph beginning "The definition and measurement of beauty" wanders off into philosophy a bit. I'd shorten this paragraph, perhaps keeping only the last two sentences.
- p 35, para -2: "defined by the horizon" => "defined by their horizon"?
- p 36, para 2: "steeply increased" => "greatly increased"
- p 36, para -2: "This is problematic" => "This was problematic"
- p 36, para -2: "most applications are fine" => "most applications were fine"
- p 36, para -2: "certain pieces is gone" => "certain pieces were gone"
- p 36, para -2: "developers are informed" => "developers were informed"
- p 36, para -2: "they can no longer compile" => "they could no longer compile"
- p 37, para 1: "on screen" => "on-screen"
- p 37, para 2: "the API usage" => "the API's usage"
- p 37, para 2: "the ultimate open source project" => "the ultimate open-source project"
- p 38, para 2: "negatively effect" => "negatively affect"
- p 39, para 2: "well intended" => "well-intended"
--AdamDingle 01:20, 28 March 2008 (UTC)
Follow
