Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site codas.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!akguc!codas!mikel
From: mikel@codas.UUCP (Mikel Manitius)
Newsgroups: net.unix-wizards
Subject: Re:  code quality
Message-ID: <312@codas.UUCP>
Date: Fri, 18-Oct-85 20:13:09 EDT
Article-I.D.: codas.312
Posted: Fri Oct 18 20:13:09 1985
Date-Received: Sun, 20-Oct-85 04:02:12 EDT
References: <2012@brl-tgr.ARPA> <8952@ritcv.UUCP>
Organization: AT&T Information Systems (SDSS) - Orlando
Lines: 18

I would like to point out one fact about software, companies contract
many consultants, who very often write C software, it has been my
experience in the past, where I have known several consultants
who claimed to be "proficient in C and Unix", who's C code was rediculously
clumsy, and contained indefinite logic problems, I have seen such software
released.

Before anyone starts flaming, I am not in any way blaming poor software
on consultants, or blaming consultants for poor software. I was once a
consultant myself. However, I would really like to see much tighter
quality control of personel before allowing them to do any work!
I would almost love to name some individuals who caused many problems
in the systems they worked on, perhaps others could avoid them.
Someone somewhere should think of setting up a "credit office" for
programer information, so that "trojan horse" programers would not
last very long.
-- 
	Mikel Manitius  - ...{ihnp4|akguc|attmail|indra!koura}!codas!mikel