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.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1108a1,59ec73856b699922
X-Google-Attributes: gid1108a1,public
X-Google-Thread: fdb77,5f529c91be2ac930
X-Google-Attributes: gidfdb77,public
X-Google-Thread: 103376,583275b6950bf4e6
X-Google-Attributes: gid103376,public
X-Google-Thread: f43e6,899fc98b2883af4a
X-Google-Attributes: gidf43e6,public
X-Google-ArrivalTime: 2003-05-17 10:28:13 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!arclight.uoregon.edu!wn13feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!rwcrnsc53.POSTED!not-for-mail
Message-ID: <3EC67113.70600@attbi.com>
From: "Robert I. Eachus" <rieachus@attbi.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: 
 comp.lang.java.advocacy,comp.object,comp.lang.ada,comp.software-eng
Subject: Re: Quality systems (Was: Using Ada for device drivers? (Was: the
 Ada  mandate, and why it collapsed and died))
References: <9fa75d42.0304230424.10612b1a@posting.google.com>
 <9fa75d42.0305090612.261d5a5c@posting.google.com>
 <b9gko2$pub@library1.airnews.net>
 <9fa75d42.0305091549.48b9c5d9@posting.google.com>
 <dstanbro-DDA263.20492210052003@mec2.bigpond.net.au>
 <ZpGva.13$1Q1.6@read3.inet.fi>
 <7507f79d.0305121629.5b8b7369@posting.google.com>
 <ln0wa.54$a03.44@read3.inet.fi>
 <9fa75d42.0305130543.60381450@posting.google.com>
 <254c16a.0305140549.3a87281b@posting.google.com>
 <9fa75d42.0305141747.5680c577@posting.google.com>
 <slrnbc6ivm.i3.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <3EC3D737.6020509@attbi.com> <fZQwa.855043$F1.107665@sccrnsc04>
 <3EC65525.186A7BB7@mail1.stofanet.dk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 24.62.164.137
X-Complaints-To: abuse@attbi.com
X-Trace: rwcrnsc53 1053192492 24.62.164.137 (Sat, 17 May 2003 17:28:12 GMT)
NNTP-Posting-Date: Sat, 17 May 2003 17:28:12 GMT
Organization: AT&T Broadband
Date: Sat, 17 May 2003 17:28:12 GMT
Xref: archiver1.google.com comp.lang.java.advocacy:64029 comp.object:63619
 comp.lang.ada:37453 comp.software-eng:19262
Date: 2003-05-17T17:28:12+00:00
List-Id: <comp.lang.ada>

Bjorn Reese wrote:

> The major factor, in my experience, to cascading defects is increasing
> cognitive complexity of the system, usually combined with insufficient
> staffing. The problem is that no matter how clever your staff is, they
> will eventually reach a break-even point where the cognitive complexity
> of the system exceeds their mental capabilies. Blaming or replacing the
> staff will not decrease cognitive complexity.

Right, once the code gets too complex, all you can do is either freeze 
it totally, if that is acceptable, or start with a fresh sheet of paper.

If the system as a whole has low coupling, it is often possible to use 
that fresh sheet of paper to rewrite a small part of the system where 
the bugs and complexity are concentrated.  However, often the "bad" 
modules do have high coupling, and the only choice is to can the whole 
system.

By the way, if you find that one of your programmers is creating an 
undue share of follow-on bugs, get that guy's hands off the code 
immediately.  If you can put the hot-shot in charge of some stand alone 
utilities great, otherwise you may have to fire him or her.  (Although 
hot-shot programmers are almost alway male.)  I have never had to fire 
anyone in this situation.  Assign them to documenting what their 
existing code, or to write test scripts, and they are gone so fast that 
your head will spin.