Errata 9
From APIDesign
(→Page 154) |
(→Page 154) |
||
| Line 1: | Line 1: | ||
===== [[Errata 9|Page 154]] ===== | ===== [[Errata 9|Page 154]] ===== | ||
| - | [[Yoshiki]] wanted me to clarify meaning of ''that'', ''the'', ''this'' in the following paragraph. So here is the rephrased version: | + | [[Yoshiki]] wanted me to clarify meaning of ''that'', ''the'', ''this'' in the following paragraph. So here is the rephrased version (text is '''bold''' is changed compared to original used in [[TheAPIBook]]): |
Measuring the [[Cost of Ownership]] isn’t '''your''' primary focus when you want to find out why you don’t have as many developers using your library as you would like. It might be reasonable to analyze '''the cost of ownership''', if you used to have developers and are now losing them. However, if you’re just starting and you need to attract new ones, '''the cost of ownership''' is probably not the most important criterion to use. '''People may trust your library more''' if you have a good reputation with respect to [[BackwardCompatibility]] (which reduces the cost of ownership). However '''optimizing the [[Cost of Ownership]] may''' not '''your''' primary concern when you need to optimize for [[Time To Market]]. | Measuring the [[Cost of Ownership]] isn’t '''your''' primary focus when you want to find out why you don’t have as many developers using your library as you would like. It might be reasonable to analyze '''the cost of ownership''', if you used to have developers and are now losing them. However, if you’re just starting and you need to attract new ones, '''the cost of ownership''' is probably not the most important criterion to use. '''People may trust your library more''' if you have a good reputation with respect to [[BackwardCompatibility]] (which reduces the cost of ownership). However '''optimizing the [[Cost of Ownership]] may''' not '''your''' primary concern when you need to optimize for [[Time To Market]]. | ||
Revision as of 10:48, 11 February 2014
Page 154
Yoshiki wanted me to clarify meaning of that, the, this in the following paragraph. So here is the rephrased version (text is bold is changed compared to original used in TheAPIBook):
Measuring the Cost of Ownership isn’t your primary focus when you want to find out why you don’t have as many developers using your library as you would like. It might be reasonable to analyze the cost of ownership, if you used to have developers and are now losing them. However, if you’re just starting and you need to attract new ones, the cost of ownership is probably not the most important criterion to use. People may trust your library more if you have a good reputation with respect to BackwardCompatibility (which reduces the cost of ownership). However optimizing the Cost of Ownership may not your primary concern when you need to optimize for Time To Market.
Follow
