From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Bug zapper? :)
Date: Tue, 10 Aug 2004 22:13:56 +0100 [thread overview]
Message-ID: <200408102213.56383.nick@linicks.net> (raw)
"I'm suggesting things to make code auditing simpler, more accurate, more
precise. "Quality-Assurance audited code still contains on average 5
bugs per kloc" is a really nasty thought."
I really disagree with stuff like this.
OK, I am not a contributer to kernel code - far from it - nor really any sort
of coder at all except I can read it all and try to understand.
But why does 'quality assurance' == less bugs (or whatever you try it on - and
take we know who for an e.g.)?
It doesn't. All it does is give a 'false' assurance to something that when
tested and looked at didn't find what it was searching for to look at and
find - and of course, who/whatever does the assessment needs to be 'QA'ed'
first to make sure that is correct - so what/who does that?
If the code is 'Assured clean' then should everybody accept it and carry on to
the next bit?
Quality assurance may work in the manufacturing industry (sort of), but in
abstract fluent work...
Many eyes is the only way, reading and re-reading.
Nick
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
next reply other threads:[~2004-08-10 21:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 21:13 Nick Warne [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-09 20:07 [RFC] Bug zapper? :) John Richard Moser
[not found] ` <200408100042.37159.vda@port.imtp.ilyichevsk.odessa.ua>
2004-08-09 23:09 ` John Richard Moser
2004-08-10 0:58 ` Bernd Eckenfels
2004-08-10 1:55 ` Tommy Reynolds
2004-08-10 2:47 ` Rik van Riel
2004-08-10 3:13 ` John Richard Moser
2004-08-10 8:35 ` Jakob Oestergaard
2004-08-10 15:19 ` John Richard Moser
2004-08-10 21:43 ` Bernd Eckenfels
2004-08-10 21:30 ` V13
2004-08-10 23:35 ` John Richard Moser
2004-08-11 4:50 ` Bernd Eckenfels
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200408102213.56383.nick@linicks.net \
--to=nick@linicks.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox