Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site utah-gr.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!utah-cs!utah-gr!thomas
From: thomas@utah-gr.UUCP (Spencer W. Thomas)
Newsgroups: net.unix
Subject: Re: Unix and user friendy systems
Message-ID: <1463@utah-gr.UUCP>
Date: Tue, 28-May-85 00:48:15 EDT
Article-I.D.: utah-gr.1463
Posted: Tue May 28 00:48:15 1985
Date-Received: Thu, 30-May-85 20:05:17 EDT
References: <11048@brl-tgr.ARPA>
Reply-To: thomas@utah-gr.UUCP (Spencer W. Thomas)
Organization: Univ of Utah CS Dept
Lines: 16

In article <11048@brl-tgr.ARPA> munck@mitre-bedford.ARPA writes:
> ... Source
>code SHOULD BE written for human beings, who are its most frequent and
>expensive readers ...

As long as writing readable source code doesn't "prevent" you from ever
writing the documentation.  One of my friends, whenever he is asked how
something works, replies "Read the code!".  He rarely writes
documentation.  As a user of a piece of code, I would rather see
well-written *CORRECT* documentation and unreadable code than readable
code and NO documentation.
-- 
=Spencer   ({ihnp4,decvax}!utah-cs!thomas, thomas@utah-cs.ARPA)
	"There are only the pursued, the pursuing, the busy, and the tired."
	- F. Scott Fitzgerald