Good Technology - Revision history

http://wiki.apidesign.org/index.php?action=history&feed=atom&title=Good_Technology Good Technology - Revision history 2026-05-01T13:39:30Z Revision history for this page on the wiki MediaWiki 1.12.0rc1 http://wiki.apidesign.org/index.php?title=Good_Technology&diff=9878&oldid=prev JaroslavTulach: /* Time to Market */ 2018-10-20T06:17:32Z

<p><span class="autocomment">Time to Market</span></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 06:17, 20 October 2018</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 7:</td> <td colspan="2" class="diff-lineno">Line 7:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>Just download [[wikipedia::Ruby on Rails|Ruby on Rails]] and create your website. The only thing that you need to do is to execute a command in a shell and you have a running application. The application does not do much, but it took just seconds to create it. How can such technology be bad!?</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>Just download [[wikipedia::Ruby on Rails|Ruby on Rails]] and create your website. The only thing that you need to do is to execute a command in a shell and you have a running application. The application does not do much, but it took just seconds to create it. How can such technology be bad!?</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>An important aspect that helps the [[Time To Market]] perception is [[Cluelessness]]. If the library or framework can be used immediately, without reading bunch of materials. If one can write code without studying the whole API. If the code can execute and do something meaningful, as soon as it is compiled, then the entry barrier is lowered, and the [[Time To Market]] made smaller.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>An important aspect that helps the [[Time To Market]] perception is [[Cluelessness]]. If the library or framework can be used immediately, without reading bunch of materials. If one can write code without studying the whole <ins style="color: red; font-weight: bold; text-decoration: none;">[[</ins>API<ins style="color: red; font-weight: bold; text-decoration: none;">]]</ins>. If the code can execute and do something meaningful, as soon as it is compiled, then the entry barrier is lowered, and the [[Time To Market]] made smaller.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>What implication does this have with respect to [[API]]s of our libraries? They need to be easy to use, navigate, they need to be self documenting. On the other hand, one can substitute much of this functionality with the [[wikipedia::Ruby on Rails|Ruby on Rails]] trick: having templates, tutorials, premade samples, that can just be taken and used instantly serves this purpose well too. Good tools can make every [[API]] simple to start with...</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>What implication does this have with respect to [[API]]s of our libraries? They need to be easy to use, navigate, they need to be self documenting. On the other hand, one can substitute much of this functionality with the [[wikipedia::Ruby on Rails|Ruby on Rails]] trick: having templates, tutorials, premade samples, that can just be taken and used instantly serves this purpose well too. Good tools can make every [[API]] simple to start with...</div></td></tr> </table>

JaroslavTulach http://wiki.apidesign.org/index.php?title=Good_Technology&diff=9877&oldid=prev JaroslavTulach at 06:15, 20 October 2018 2018-10-20T06:15:56Z

<p></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 06:15, 20 October 2018</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 24:</td> <td colspan="2" class="diff-lineno">Line 24:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>On the other hand, if there is [[technology]] that is just cool, and it does not help at all with [[Time To Market]] or its [[Cost of Ownership]] is known to be too high, then no amount of coolness can compensate that and in long term the [[technology]] is destined to be seen as poor, and not as good.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>On the other hand, if there is [[technology]] that is just cool, and it does not help at all with [[Time To Market]] or its [[Cost of Ownership]] is known to be too high, then no amount of coolness can compensate that and in long term the [[technology]] is destined to be seen as poor, and not as good.</div></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div><del style="color: red; font-weight: bold; text-decoration: none;"></del></div></td><td colspan="2"> </td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div><del style="color: red; font-weight: bold; text-decoration: none;"></del></div></td><td colspan="2"> </td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div><del style="color: red; font-weight: bold; text-decoration: none;"><comments/></del></div></td><td colspan="2"> </td></tr> </table>

JaroslavTulach http://wiki.apidesign.org/index.php?title=Good_Technology&diff=9865&oldid=prev JaroslavTulach at 05:52, 20 October 2018 2018-10-20T05:52:04Z

<p></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 05:52, 20 October 2018</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>What makes a [[Technology]] ''good''? What made some people to select one [[technology]] over another? What a designer needs to concentrated on when creating a library or framework to make it ''good'', successful, widely accepted? This page highlights the common principles that make things ''work''.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>What makes a [[Technology]] ''good''? What made some people to select one [[technology]] over another? What a designer needs to concentrated on when creating a library or framework to make it ''good'', successful, widely accepted? This page highlights the common principles that make things ''work''.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>== [[Time <del style="color: red; font-weight: bold; text-decoration: none;">To </del>Market]] ==</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>== [[<ins style="color: red; font-weight: bold; text-decoration: none;">wikipedia::Time_to_market|</ins>Time <ins style="color: red; font-weight: bold; text-decoration: none;">to </ins>Market]] ==</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>Evaluation of any software technology starts with downloading, installing and trying to create simple hello world application. The faster one can do this, the less obstacles are found in a way, the better perception such [[technology]] gets. Of course, there is a long way from a ''hello world'' demo, to the final release, yet the first perception counts. </div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>Evaluation of any software technology starts with downloading, installing and trying to create simple hello world application. The faster one can do this, the less obstacles are found in a way, the better perception such [[technology]] gets. Of course, there is a long way from a ''hello world'' demo, to the final release, yet the first perception counts. </div></td></tr> </table>

JaroslavTulach http://wiki.apidesign.org/index.php?title=Good_Technology&diff=9744&oldid=prev JaroslavTulach at 12:29, 24 September 2018 2018-09-24T12:29:46Z

<p></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 12:29, 24 September 2018</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 17:</td> <td colspan="2" class="diff-lineno">Line 17:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>The implications of this [[life cycle]] phase on the shape of [[API]]s of our libraries is quite different to the initial ''to market'' phase. The code created using such [[API]] needs to be readable, preferably by other person than just the author of the code. And especially, [[API]]s for a [[Good Technology]] shall not stimulate [[Fear of Upgrades]] syndrome. </div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>The implications of this [[life cycle]] phase on the shape of [[API]]s of our libraries is quite different to the initial ''to market'' phase. The code created using such [[API]] needs to be readable, preferably by other person than just the author of the code. And especially, [[API]]s for a [[Good Technology]] shall not stimulate [[Fear of Upgrades]] syndrome. </div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>== Coolness ==</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>== <ins style="color: red; font-weight: bold; text-decoration: none;">[[</ins>Coolness<ins style="color: red; font-weight: bold; text-decoration: none;">]] </ins>==</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>It definitely helps if a technology can be seen as being [[wikipedia::coolness|cool]]. People like to talk about cool things, like to show to others that they follow the trends and as such [[technology]] that is cool, is easier to market and to spread. </div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>It definitely helps if a technology can be seen as being [[wikipedia::coolness|cool]]. People like to talk about cool things, like to show to others that they follow the trends and as such [[technology]] that is cool, is easier to market and to spread. </div></td></tr> </table>

JaroslavTulach http://wiki.apidesign.org/index.php?title=Good_Technology&diff=1959&oldid=prev JaroslavTulach: /* Coolness */ 2009-01-25T14:35:10Z

<p><span class="autocomment">Coolness</span></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 14:35, 25 January 2009</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 19:</td> <td colspan="2" class="diff-lineno">Line 19:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Coolness ==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Coolness ==</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>It definitely helps if a technology can be seen as being [[wikipedia::coolness|cool]]. People like to talk about cool things, like to show to others that they follow the trends and as such [[technology]] that is cool, is easier to market and spread. </div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>It definitely helps if a technology can be seen as being [[wikipedia::coolness|cool]]. People like to talk about cool things, like to show to others that they follow the trends and as such [[technology]] that is cool, is easier to market and <ins style="color: red; font-weight: bold; text-decoration: none;">to </ins>spread. </div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>On the other hand, if there is [[technology]] that is just cool, and it does not help at all with [[Time To Market]] or its [[Cost of Ownership]] is known to be too high, then no amount of coolness can compensate that and in long term the [[technology]] is destined to be seen as poor, not good.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">''Being cool'' can be achieved in many forms. One can follow the [[wikipedia::coolness|cool]] trends, talk about such technology using [[wikipedia::buzzword|buzzword]]s or even give the technology [[Good Name]].</ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div> </div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>On the other hand, if there is [[technology]] that is just cool, and it does not help at all with [[Time To Market]] or its [[Cost of Ownership]] is known to be too high, then no amount of coolness can compensate that and in long term the [[technology]] is destined to be seen as poor, <ins style="color: red; font-weight: bold; text-decoration: none;">and </ins>not <ins style="color: red; font-weight: bold; text-decoration: none;">as </ins>good.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><comments/></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><comments/></div></td></tr> </table>

JaroslavTulach http://wiki.apidesign.org/index.php?title=Good_Technology&diff=1619&oldid=prev JaroslavTulach: /* Time To Market */ 2008-11-03T18:28:22Z

<p><span class="autocomment">Time To Market</span></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 18:28, 3 November 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 5:</td> <td colspan="2" class="diff-lineno">Line 5:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>Evaluation of any software technology starts with downloading, installing and trying to create simple hello world application. The faster one can do this, the less obstacles are found in a way, the better perception such [[technology]] gets. Of course, there is a long way from a ''hello world'' demo, to the final release, yet the first perception counts. </div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>Evaluation of any software technology starts with downloading, installing and trying to create simple hello world application. The faster one can do this, the less obstacles are found in a way, the better perception such [[technology]] gets. Of course, there is a long way from a ''hello world'' demo, to the final release, yet the first perception counts. </div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>Just download [[wikipedia::Ruby on Rails|Ruby on Rails]] and create your website. The only thing that you need to do is to execute a command in a shell and you have a running application. The application does not do much, but it <del style="color: red; font-weight: bold; text-decoration: none;">too </del>just seconds to create it. How can such technology be bad!?</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>Just download [[wikipedia::Ruby on Rails|Ruby on Rails]] and create your website. The only thing that you need to do is to execute a command in a shell and you have a running application. The application does not do much, but it <ins style="color: red; font-weight: bold; text-decoration: none;">took </ins>just seconds to create it. How can such technology be bad!?</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>An important aspect that helps the [[Time To Market]] perception is [[Cluelessness]]. If the library or framework can be used immediately, without reading bunch of materials. If one can write code without studying the whole API. If the code can execute and do something meaningful, as soon as it is compiled, then the entry barrier is lowered, and the [[Time To Market]] made smaller.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>An important aspect that helps the [[Time To Market]] perception is [[Cluelessness]]. If the library or framework can be used immediately, without reading bunch of materials. If one can write code without studying the whole API. If the code can execute and do something meaningful, as soon as it is compiled, then the entry barrier is lowered, and the [[Time To Market]] made smaller.</div></td></tr> </table>

JaroslavTulach http://wiki.apidesign.org/index.php?title=Good_Technology&diff=1615&oldid=prev JaroslavTulach: /* Coolness */ 2008-11-03T18:20:46Z

<p><span class="autocomment">Coolness</span></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 18:20, 3 November 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 24:</td> <td colspan="2" class="diff-lineno">Line 24:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div><<del style="color: red; font-weight: bold; text-decoration: none;">comment</del>/></div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><<ins style="color: red; font-weight: bold; text-decoration: none;">comments</ins>/></div></td></tr> </table>

JaroslavTulach http://wiki.apidesign.org/index.php?title=Good_Technology&diff=1614&oldid=prev JaroslavTulach at 18:20, 3 November 2008 2008-11-03T18:20:37Z

<p></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 18:20, 3 November 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 22:</td> <td colspan="2" class="diff-lineno">Line 22:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>On the other hand, if there is [[technology]] that is just cool, and it does not help at all with [[Time To Market]] or its [[Cost of Ownership]] is known to be too high, then no amount of coolness can compensate that and in long term the [[technology]] is destined to be seen as poor, not good.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>On the other hand, if there is [[technology]] that is just cool, and it does not help at all with [[Time To Market]] or its [[Cost of Ownership]] is known to be too high, then no amount of coolness can compensate that and in long term the [[technology]] is destined to be seen as poor, not good.</div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;"></ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;"></ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;"><comment/></ins></div></td></tr> </table>

JaroslavTulach http://wiki.apidesign.org/index.php?title=Good_Technology&diff=1610&oldid=prev JaroslavTulach at 18:08, 3 November 2008 2008-11-03T18:08:35Z

<p></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 18:08, 3 November 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 6:</td> <td colspan="2" class="diff-lineno">Line 6:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>Just download [[wikipedia::Ruby on Rails|Ruby on Rails]] and create your website. The only thing that you need to do is to execute a command in a shell and you have a running application. The application does not do much, but it too just seconds to create it. How can such technology be bad!?</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>Just download [[wikipedia::Ruby on Rails|Ruby on Rails]] and create your website. The only thing that you need to do is to execute a command in a shell and you have a running application. The application does not do much, but it too just seconds to create it. How can such technology be bad!?</div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;"></ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">An important aspect that helps the [[Time To Market]] perception is [[Cluelessness]]. If the library or framework can be used immediately, without reading bunch of materials. If one can write code without studying the whole API. If the code can execute and do something meaningful, as soon as it is compiled, then the entry barrier is lowered, and the [[Time To Market]] made smaller.</ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;"></ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">What implication does this have with respect to [[API]]s of our libraries? They need to be easy to use, navigate, they need to be self documenting. On the other hand, one can substitute much of this functionality with the [[wikipedia::Ruby on Rails|Ruby on Rails]] trick: having templates, tutorials, premade samples, that can just be taken and used instantly serves this purpose well too. Good tools can make every [[API]] simple to start with...</ins></div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Total [[Cost of Ownership]] ==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Total [[Cost of Ownership]] ==</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div><del style="color: red; font-weight: bold; text-decoration: none;">TBD</del></div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">However [[life cycle]] of a software product is not over after releasing first version. Especially in case of successful products, there will be many subsequent revisions. Creation of these new versions puts fundamentally different requirements on the underlying [[technology]] - it is no longer important how fast it is to write new code. It is more important whether the existing code can be read, debugged and modified without introducing major regressions. It is important whether one can safely upgrade to newer version of underlying framework or [[technology]] without being afraid of [[BackwardCompatibility]] problems.</ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div> </div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">The implications of this [[life cycle]] phase on the shape of [[API]]s of our libraries is quite different to the initial ''to market'' phase. The code created using such [[API]] needs to be readable, preferably by other person than just the author of the code. And especially, [[API]]s for a [[Good Technology]] shall not stimulate [[Fear of Upgrades]] syndrome. </ins></div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Coolness ==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Coolness ==</div></td></tr> </table>

JaroslavTulach http://wiki.apidesign.org/index.php?title=Good_Technology&diff=1608&oldid=prev JaroslavTulach at 17:25, 3 November 2008 2008-11-03T17:25:20Z

<p></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 17:25, 3 November 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 3:</td> <td colspan="2" class="diff-lineno">Line 3:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== [[Time To Market]] ==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== [[Time To Market]] ==</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div><del style="color: red; font-weight: bold; text-decoration: none;">TBD</del></div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">Evaluation of any software technology starts with downloading, installing and trying to create simple hello world application. The faster one can do this, the less obstacles are found in a way, the better perception such [[technology]] gets. Of course, there is a long way from a ''hello world'' demo, to the final release, yet the first perception counts. </ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div> </div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">Just download [[wikipedia::Ruby on Rails|Ruby on Rails]] and create your website. The only thing that you need to do is to execute a command in a shell and you have a running application. The application does not do much, but it too just seconds to create it. How can such technology be bad!?</ins></div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Total [[Cost of Ownership]] ==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Total [[Cost of Ownership]] ==</div></td></tr> <tr><td colspan="2" class="diff-lineno">Line 13:</td> <td colspan="2" class="diff-lineno">Line 15:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>It definitely helps if a technology can be seen as being [[wikipedia::coolness|cool]]. People like to talk about cool things, like to show to others that they follow the trends and as such [[technology]] that is cool, is easier to market and spread. </div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>It definitely helps if a technology can be seen as being [[wikipedia::coolness|cool]]. People like to talk about cool things, like to show to others that they follow the trends and as such [[technology]] that is cool, is easier to market and spread. </div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>On the other hand, if there is [[technology]] that is just cool, and it does not help at all with [[<del style="color: red; font-weight: bold; text-decoration: none;">time to market</del>]] or its [[<del style="color: red; font-weight: bold; text-decoration: none;">cost </del>of <del style="color: red; font-weight: bold; text-decoration: none;">ownership</del>]] is known to be too high, then no amount of coolness can compensate that and in long term the [[technology]] is destined to be seen as poor, not good.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>On the other hand, if there is [[technology]] that is just cool, and it does not help at all with [[<ins style="color: red; font-weight: bold; text-decoration: none;">Time To Market</ins>]] or its [[<ins style="color: red; font-weight: bold; text-decoration: none;">Cost </ins>of <ins style="color: red; font-weight: bold; text-decoration: none;">Ownership</ins>]] is known to be too high, then no amount of coolness can compensate that and in long term the [[technology]] is destined to be seen as poor, not good.</div></td></tr> </table>

JaroslavTulach