Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!gatech!hao!husc6!bloom-beacon!oberon!castor.usc.edu!blarson From: blarson@castor.usc.edu (Bob Larson) Newsgroups: comp.lang.c Subject: Re: Writing readable code Message-ID: <3298@oberon.USC.EDU> Date: Fri, 10-Jul-87 15:21:09 EDT Article-I.D.: oberon.3298 Posted: Fri Jul 10 15:21:09 1987 Date-Received: Sun, 12-Jul-87 13:24:02 EDT References: <598@nonvon.UUCP> <2365@bunker.UUCP> Sender: nobody@oberon.USC.EDU Reply-To: blarson@castor.usc.edu (Bob Larson) Organization: USC AIS, Los Angeles Lines: 19 In article <2365@bunker.UUCP> garys@bunker.UUCP (Gary M. Samuelson) writes: Paraphase: Managers frequently don't see time spend writing documentation as progress to the goal of a completed project. True. This also applies to reading documentation, only you don't have any physical work to point to after you are done. The people who can't see spending the time reading new manuals as they become available tend to be the same ones that treat you as a guru when you use the knolage gained. Even harder to directly prove is the benifits of reading newsgroups such as comp.lang.c. (With manuals, you can occasionally point out things like "the answer is in the chapter on wildcards in the primos reference manual".) [Fortuanatly, I have an manager who knows the benifits of writing readable code and doesn't breath over my shoulder all the time.] -- Bob Larson Arpa: Blarson@Ecla.Usc.Edu Uucp: {sdcrdcf,seismo!cit-vax}!oberon!castor!blarson "How well do we use our freedom to choose the illusions we create?" -- Timbuk3