Personally, I consider all of those "false bugs" as gems. As I said in my OP, these are all indicators of where I can make my product more usable. Perhaps that unrelated link should not be placed quite so close to the submit button, for example. Of course, this is all theory on my part since I can't see what that tester compalined about. And, perhaps, we decide that the impact is low enough to warrant not fixing. But at least we know it's there - an informed risk vs an uninformed risk.

I agree - exposure should be part of risk calculation. But you only need to educate those who may become exposed. For example, the last time I was on a pig farm was ... lemme see... never! But the last time I was on a beach that was reachable by sharks was ... January, 2004. (I'm landlocked where I live, in the middle of the Canadian prairies, with many a farm within a small distance.) So learning about the risks from sharks is way more useful than learning about the risks of pigs. Exposure is critical, and is what Bruce ignores in your quote. There are probably also newsletters and newspapers and the like dedicated to farmers. There may even be government-funded booklets and the like which farmers would look at that the rest of us don't. So who is to say that there is more effort expended for one than the other? It's just that, to save money from being needlessly wasted, the effort is targetted to those who are at higher risk. Lots of people go to the oceans for vacation, so shark education is useful in the general public, but very few are exposed face-to-face with a pig. You, me, and Bruce wouldn't see the pig-risk documents. But those who need to are much more likely to have seen it.

In reply to OT: exposure vs risk (was Re^5: Dealing with the QA guy ... (no, really)) by Tanktalus
in thread Dealing with the QA guy ... (no, really) by Tanktalus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.