Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!titan!preston
From: preston@titan.rice.edu (Preston Briggs)
Newsgroups: comp.lang.misc
Subject: Re: Languages & cultures
Message-ID: <5995@brazos.Rice.edu>
Date: 22 Mar 90 20:22:34 GMT
References: <2605a117.396e@polyslo.CalPoly.EDU> <8440@hubcap.clemson.edu> <5948@brazos.Rice.edu> <5631@odin.corp.sgi.com>
Sender: root@rice.edu
Organization: Rice University, Houston
Lines: 29

In article <5631@odin.corp.sgi.com> archer@elysium.sgi.com (Archer Sully) writes:
>In article <5948@brazos.Rice.edu> preston@titan.rice.edu (Preston Briggs) writes:

>>Hmmmmm.  I believe I'm more efficient (bang for the buck) than any large
>>group of programmers.  I also believe I can write cleaner, better organized,
>>better documented programs than a large group of people.  

>Are you making a connection between your ability to write good code
>and grad school?

No.  I meant something closer to "one person can do a better job than
many people."  A group have people will have communication and management
problems to deal with.  An individual should be able to avoid these!

Arguments for programming teams might run along the lines of:
	Finishing the product in time for it to be economically interesting.
	Distribution of overhead (building, computers, insurance, ...)

(On the other hand, considering grad student pay, the "bang for the buck"
 argument may still hold. :-)  Remember also that grad students are supposed
 to be working on their thesis.  Any code produced is usually a by-product,
 perhaps even toxic waste.  You get what you pay for.)

My earlier comments about grad school were intended to imply that I feel
like I've learned a lot.  It's been worth my while.

--
Preston Briggs				looking for the great leap forward
preston@titan.rice.edu