From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: *
X-Spam-Status: No, score=1.1 required=5.0 tests=BAYES_40,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Xref: utzoo comp.lang.ada:5775 comp.lang.c++:14297
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!mips!apple!well!nagle
From: nagle@well.sf.ca.us (John Nagle)
Newsgroups: comp.lang.ada,comp.lang.c++
Subject: Re: chief programmer team organizations was (c++ vs ada results)
Message-ID: <25587@well.sf.ca.us>
Date: 22 Jun 91 02:14:23 GMT
References: <1991Jun18.122812.18190@eua.ericsson.se> <1991Jun18.220609.19103@netcom.COM> <1991Jun19.170047.25064@software.org> <1991Jun20.143535.27176@software.org>
List-Id: <comp.lang.ada>


     Real chief programmer teams are very rare.  I've never heard of one
other than in Brooks' book.  It's very different than having a lead programmer
or a system architect.  It's organized like a surgical team.  The chief
programmer personally writes most of the delivered code, and everything else
is set up to facilitate this.  There is an administrator, who reports to the
chief programmer, to take care of mundane problems.  A toolsmith creates
tools not part of the deliverable code.  A language lawyer deals with
compiler and library issues.  A tester tests everything.  A librarian 
keeps track of everything.  All these people are subordinate to the chief
programmer.

    It's too much of a culture shock for most organization.

					John Nagle