Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!accuvax.nwu.edu!delta.eecs.nwu.edu!travis
From: travis@delta.eecs.nwu.edu (Travis Marlatte)
Newsgroups: comp.software-eng
Subject: Re: Code Inspections
Summary: Good success using inspections
Message-ID: <16581@accuvax.nwu.edu>
Date: 1 Feb 91 01:19:53 GMT
Sender: news@accuvax.nwu.edu
Reply-To: travis@delta.eecs.nwu.edu (Travis Marlatte)
Organization: Northwestern U, Evanston IL, USA
Lines: 26
References:

I have worked at several places that used code inspections. At each place,
there were some that had a hard time dealing with inspections from an
emotional perspective. However, the inspections were done well and 
these same people eventually became major contributors to the inspections
and to the team environment in general.

Does this say that introverted programmers have no place in a development
team? And, that open, sharing programmers are the only ones that are
generally usable? No, I don't think so. However, if it is a team, then
all players must participate at some level.

I am of the opinion that all people can achieve an attitude of open
participation in programming teams and inspections. One colleague who
was scared to death to go into her first inspection decided that she would
rather open her code to local critism than to have the customer find the
faults. She went on to become a project manager and now operates as an
independent consultant.

You too can achieve popularity. Your friends won't recognize you. You'll
be the life of the party. Just send for our free booklet, "I once was
an inspection dropout." Please include $25.00 for postage and handling.

I don't buy the observation that some programmers where born "this" way and
so they have to stay "this" way.

Travis Marlatte