Lists Home |
Date Index |
Bullard, Claude L (Len) wrote:
>> Ideally, in a software project, one cycles through as many
>>phases of complexifiction->simplification as possible during the
>>"design" phase. It is really unfortunate, although often unavoidable,
>>when these phases involve released code...
>No that is ideal. The customer is an observer and has access to the
>feedback ports. The real trick is to create an economic model that
>recognizes this without breaking the firm fixed price for the initial
>acquisition. It's called maintenance. The smart contract builds this
>in as services. It is this evolution toward a services economy that
>Gertsner recognized and which has made IBM a major player while Sun
>has languished and Microsoft has worked mightily to maintain dominance
>over the core technologies. The Microsoft hegemony will crack and
>IBM will prosper. Sun will wise up.
>But back to frequency and occurrence? What will the effect of
>open blogging be on Sun and Microsoft? Is the size of the
>company an issue?
while we're talking entropy, don't forget the most important aspect of
it. in a closed system it increases over time. i think this is
overlooked too much. (the reason time is an arrow, not a bidrectional line).
this, put simply, means that all our designs will start to break down
over time unless we have a maintenance cycle. and in our maturing
industry, as you have observed re ibm, the companies that get this right
will be the winners. the technologies that get this right will be the
so as the entropy of xml increases where is the energy coming from to
maintain order in the process, or is it as some suspect, out of control?
will xml survive the fragmentation forces?
tel;cell:+61 411 287 530