Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!ll-xn!mit-eddie!bloom-beacon!think!fad
From: fad@think.COM (franklin a davis)
Newsgroups: comp.software-eng
Subject: Re: Boswell and the Project Chronicles
Message-ID: <20437@think.UUCP>
Date: 3 May 88 14:18:05 GMT
References: <321@uwslh.UUCP> <40335UH2@PSUVM> <758@dlhpedg.co.uk> <41127UH2@PSUVM>
Sender: usenet@think.UUCP
Reply-To: fad@balder.think.com.UUCP (franklin a davis)
Organization: Thinking Machines Corporation
Lines: 20

In article <41127UH2@PSUVM> UH2@PSUVM.BITNET (Lee Sailer) writes:
>
>Brooks's "surgical team" approach provides for this, but not in the pattern
>you suggest.  It is the Chief Programmer's job to oversee the documentation.
>A librarian/secretary/editor is on the team to relieve the workload.
>
>The "Boswell"  (nice term) is the assstant to the Chief Programmer, and
>very few official duties, except to hang around the Chief Programmer,
>look over his or her shoulder, know everything the chief programmer knows,
>and be ready to step in at a moments notice if the CP gets hit by a truck.
>

There have been several recent references to Brooks' CP model.  The
main problem I see with it is that, realistically, few projects are
lucky enough to find a "super-programmer" with the skills and talent
to fill the role.  

--Franklin

  franklin a davis  Thinking Machines Corp. Cambridge, MA 02142   617-876-1111
  <fad@think.com>   {ihnp4, harvard, seismo}!think!fad  "Roll away...the dew!"