Good Technology
From APIDesign
(New page: 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...) |
|||
| Line 3: | Line 3: | ||
== [[Time To Market]] == | == [[Time To Market]] == | ||
| - | + | 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. | |
| + | |||
| + | 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!? | ||
== Total [[Cost of Ownership]] == | == Total [[Cost of Ownership]] == | ||
| Line 13: | Line 15: | ||
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. | 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. | ||
| - | On the other hand, if there is [[technology]] that is just cool, and it does not help at all with [[ | + | 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. |
Revision as of 17:25, 3 November 2008
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.
Time To Market
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.
Just download 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!?
Total Cost of Ownership
TBD
Coolness
It definitely helps if a technology can be seen as being 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.
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.
Follow
