Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!pwa-b!mmintl!franka
From: franka@mmintl.UUCP (Frank Adams)
Newsgroups: net.lang.c
Subject: Re:  questions from using lint
Message-ID: <1504@mmintl.UUCP>
Date: Sun, 25-May-86 22:19:02 EDT
Article-I.D.: mmintl.1504
Posted: Sun May 25 22:19:02 1986
Date-Received: Wed, 28-May-86 05:59:47 EDT
References: <531@bu-cs.UUCP> <531@brl-smoke.ARPA> <6667@utzoo.UUCP> <1464@mmintl.UUCP> <6726@utzoo.UUCP>
Reply-To: franka@mmintl.UUCP (Frank Adams)
Organization: Multimate International, E. Hartford, CT
Lines: 22

In article <6726@utzoo.UUCP> henry@utzoo.UUCP writes:
>> ... Beyond a certain minimum size, design/code/debug is faster than
>> code/debug.
>
>Ah, but is design/code/debug/release/withdraw/revise/really-release faster
>than code/debug/try/code/debug/release? :-)

But now you're arguing about a different part of the process.  What I want
is design/code/debug/try/[re-design]/code/debug/release.  This often is
faster than leaving out the design phase.

>More seriously, I do acknowledge
>the need to have some idea of where you're going before you set out to
>get there.  And the degree of advance planning needed is indeed a function
>of project size.  But getting where you're going and then discovering that
>you really want to be somewhere else should be treated as a predictable
>part of the development process, not as a rare and surprising exception.

Agreed.

Frank Adams                           ihnp4!philabs!pwa-b!mmintl!franka
Multimate International    52 Oakland Ave North    E. Hartford, CT 06108