I think the reason the OP's comments got me riled up is that it's the 'what does it matter when it saves time and money' kind of attitude1 that can make working in these 2% situations very difficult. I think what I really wanted to communicate is that you can not always assume 'it works' is good enough. If your working environment has standards set higher than that, you're quite likely to be contracted to work to them, not under them, and you are obliged to do so.

I suspect it's residual bitterness from having to spend late nights at work double-checking data sheets against data inputs (that have already been checked twice yet still have 5% error rates). Eventually I did most of the key-punch work myself because I had the fastest data entry speed with the lowest error rate. People look at you like you're doing voodoo when you can do data entry on the keypad without using the mouse to navigate cells or look at the screen.

1 I'm not belittling his opinion. In situations where you've got to ship the product on a deadline, you've got to do what you've got to do and it is the right way to be thinking. I'm just putting up the counter PoV.

In reply to Re^3: The dangers of perfection, and why you should stick with good enough by Bloodrage
in thread The dangers of perfection, and why you should stick with good enough by redhotpenguin

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.