evolution by committee

Ed Nather nather at ut-sally.UUCP
Mon May 16 06:02:04 AEST 1988


In article <7890 at brl-smoke.ARPA>, gwyn at brl-smoke.ARPA (Doug Gwyn ) writes:
> In article <11593 at ut-sally.UUCP> nather at ut-sally.UUCP (Ed Nather) writes:
> >It makes me nervous to realize this evolutionary step was made by a
> >committee.
> 
> Whoopie do.  What are the alternatives?
> 	1) stagnation at a functionally inadequate level
> 	2) evolution by one individual's fiat (who?)
> 	3) evolution by cooperating individuals (e.g. committee)
> 	4) evolution by battling individuals
> Pick one.  I think I would be MORE nervous with the other alternatives.

If these are the only choices I'm offered, I guess
I would pick number 2 because I've seen it work sometimes, even though
failure is probably more likely.  C was designed by a single individual (dmr)
based on his knowledge of many other languages and ideas, on his own
experience as a programmer, and on his needs of the moment.  Is this the
ideal way to design anything?  No. Won't you end up with what HE wanted and
not what YOU want?  Sure.  But it will work if he knows what he is doing
and has a talent for design, and you may well find you can conform to his
way of doing things much easier than you can design your own.

I don't really know how much Dennis Ritchie has been involved with this
"evolutionary step" but a little boiled over into this newsgroup, so I
gather it's not zero.  So let me suggest another alternative:

5) evolution by the original designer, based on suggestions by cooperating
individuals (e.g. committee).

I've been on enough committees to recognize a serious problem: there are
too many interfaces between individuals and too little time for really
intensive iteration on problems and consequences.  A single individual
can iterate 10 times while taking a shower -- but not as a member of a
committee.  He must stop the loop after 1 cycle and check with the other
members.  With all due (and genuine) respect for the ANSI committee
members as individuals, I suggest the method itself is seriously limiting.

The ideal way to proceed, in my view, would be to come up with a proposed
standard, then give it to Dennis Ritchie and ask him to take out anything
he finds offensive, replace awkwardnesses with better solutions if he can 
find them, and take what he hands you back as the next "evolutionary step."
He may well not have the time nor inclination to do it, but I would ask.

-- 
Ed Nather
Astronomy Dept, U of Texas @ Austin
{allegra,ihnp4}!{noao,ut-sally}!utastro!nather
nather at astro.AS.UTEXAS.EDU



More information about the Comp.lang.c mailing list