I used to be the kind who would disagree vociferously, but I've evolved since then.
The sense in which program development is similar to evolution is somewhere between the level of detail you describe here and the very general "things change". The driving imperative in evolution is "adapt or perish". Of course, that's true of anything geared to a marketplace, and evolutionary design might just as well be termed "market-driven design".
According to this article on the topic, "evolutionary design" is meaningful as a contrast to "planned design". In the latter, you design, then you code to spec. In the former, both are ongoing processes. If you object to the use of "evolutionary", you might prefer Just-In-Time programming for a similar concept: programs are written and changed in response to demand, rather than in far-sighted anticipation of it.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
