Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!brl-adm!brl-smoke!smoke!rbj@icst-cmr
From: rbj@icst-cmr (Root Boy Jim)
Newsgroups: net.lang.c
Subject: Design Process
Message-ID: <908@brl-smoke.ARPA>
Date: Thu, 15-May-86 21:00:27 EDT
Article-I.D.: brl-smok.908
Posted: Thu May 15 21:00:27 1986
Date-Received: Sun, 25-May-86 11:44:32 EDT
Sender: news@brl-smoke.ARPA
Lines: 18


	> All too often, one sees programmers writing code before
	> a proper job of analysis and design has been done.  I
	> also believe that is partly because semi-running code
	> makes it appear as though progress has been made,
	> while a complete design doesn't convey the same impression.
	
	Sorry, Doug, I can't let that one go by.

Me neither. It has also been said that programs should be written twice:
once to find out what the specs are, then that program should be thrown
away and the job done right.

TPC seems to have followed that philosophy, as System V looks nothing
at all like UNIX :-)

	(Root Boy) Jim Cottrell		<rbj@cmr>
	"One man gathers what another man spills"