Path: utzoo!mnetor!uunet!mcvax!ukc!stl!stc!datlog!dlhpedg!cl
From: cl@datlog.co.uk (Charles Lambert)
Newsgroups: comp.software-eng
Subject: Boswell and the Project Chronicles
Message-ID: <758@dlhpedg.co.uk>
Date: 28 Apr 88 12:12:52 GMT
References: <321@uwslh.UUCP> <40335UH2@PSUVM>
Sender: news@dlhpedg.co.uk
Reply-To: cl@datlog.co.uk (Charles Lambert)
Organization: FSD@Data Logic Ltd, Queens House, Greenhill Way, Harrow, London.
Lines: 32

In article <40335UH2@PSUVM> UH2@PSUVM.BITNET (Lee Sailer) writes on the
subject "Who builds tools?":
>Put in a broader perspective, maybe every project ought to have someone
>who, while not being good at the techniques the final code will contain,
>IS good with tools and tool building.

In a similar vein,  I believe that every project should have a "Boswell"
(cf. Dr Johnson) whose job is to look over the team's collective shoulder
and write down all those nuggets of expertise,  revelation and folklore
that eventually (in our imperfect profession) make the original team
indispensable.  Boswell's brief would be either

i.	to write the project documentation, or
ii.	to note everything that needs to go into the project documentation
	so that the team leader can chase the responsible parties.

That documentation would include clear instructions for the use of the
Toolsmith's creations AND an explanation of the underlying procedure, so
that new recruits will not be crippled when the special tools fail.

The measure of his or her success would be the ease with which new members
could be brought up to speed and the lack of involvement by the development
team after handing over to maintenance.

Boswell's effort would have a profound effect on the integrity of the code,
the consistency of the design and,  hence,  the cost of maintenance because
the philosophy and foibles of the implementation - things which are usually
either opaque or invisible to late recruits and maintainers - would be
recorded.

--------------
Charles Lambert