Re: Paying developers to get features faster

From: Barry Margolin (barmar_at_alum.mit.edu)
Date: 01/22/04 

Date: Thu, 22 Jan 2004 06:35:08 GMT

In article <hqnu00d3tutt87k080f5cepfc85kopl9ii@4ax.com>,
 Steve Holdoway <steve@itemfront.ltd.uk> wrote:

> Just because somebody requires it, doesn't make it worthwhile!

Nor does it automatically make it worthless, either. Some programming
standards have a reasonable basis.

Warnings usually indicate that there's something wrong, or at least
suspicious. Even if you're sure they're benign, consider the plight of
the next developer to work on the code -- he'll have to go through all
the warnings, trying to figure out which can be ignored and which must
be resolved. The alternative is to blindly ignore all the warnings, in
which case you have a "boy who cried 'wolf'" situation -- inevitably a
warning that should be heeded will come out, and it will be ignored. 

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
Quantcast