I sometimes get sideways with people during the design phase of a project.  I'm a big believer in rapid prototyping as partial design tool, but I often find that many people are of the "Waterfall" SW design philosophy, and can't adjust to the concept of writing some code, and then throwing it away once the refined design becomes more obvious. 

Of course, there is always the threat that sombody will fall in love with either the prototype or (worse) the prototyping environment and then proceed to misuse the prototyping tool, typically by pushing it beyond it's capabilities.  Living inside an IDE often feels like that.

--
Doug Roberts, RTI International
[EMAIL PROTECTED]
[EMAIL PROTECTED]
505-455-7333 - Office
505-670-8195 - Cell

On 9/11/06, Raymond Parks <[EMAIL PROTECTED]> wrote:
Douglas Roberts wrote:
> An equally reasonable alternative suggestion: write every app as an APL
> one-liner (no indentation nor whitespace needed).

   And it can be write-only (no reading and modifying).  Which, of
course, is why we keep trying things like WinFX - so that there's some
chance that you can pick up the code I generated two years ago and
change it.  I'm just a cynic, but sometimes I think we spend more time
and effort writing code to be reusable and modifiable than if we just
rewrote it every time we needed to change it.

--
Ray Parks                   [EMAIL PROTECTED]
IDART Project Lead          Voice:505-844-4024
IORTA Department            Mobile:505-238-9359
http://www.sandia.gov/scada Fax:505-844-9641
http://www.sandia.gov/idart Pager:800-690-5288


============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
lectures, archives, unsubscribe, maps at http://www.friam.org



============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
lectures, archives, unsubscribe, maps at http://www.friam.org

Reply via email to