Seems to me that there is a big difference between statutory requirement where risk to life and limb is involved, and a set of coding standards (preferences). Non-compliance with a statutory requirement could never be deemed "good enough".

I mean, is 'it works' good enough for ...

...a list of mission critical software that represents maybe 2% of the software written. Even then, if your definition of "it works" is: meets all the projects requirements, which by definition includes any statutory requirements applicable, then yes. It works is good enough.

A piece of (say) game software is unlikely to result in death or injury, if it occasionally accumulates enough floating point errors to cause a game piece spacecraft to attempt a high speed rendezvous with the moon. Space flight control software could. Failure to destinguish between the quality requirements of the two could be disasterous for the company developing the software either way.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^2: The dangers of perfection, and why you should stick with good enough by BrowserUk
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.