In the general case, it is foolish to assume that bosses are morons and underlings have the correct answers.

First, there is no implicit or implied assumption that all bosses are morons. Having been the boss for a good part of my career, that would indeed be foolish. I've also been lucky enough to work for many, very excelllent bosses over the years.

However, I've also been unlucky enough to work for some, who whilst often very competent people and resource managers, decisions makers etc., that were completely out of their element when it came to the technical issues of the departments they ran. These are far more common than one would like, and it's not always a bad thing. The problems arise when they start to make technical descisions in ass-covering mode; or on the strength of the school/college/regimental logo on the tie of the last salesman they spoke to; or the quality of the meal he brought them; or simply because his sales pitch had convinced them that XYZ would save their project.

A consortium of underlings may conspire and through insubordination save a project from a mandate of some stupid practice, but that just helps to prove the mandate worthwhile.

No matter how I read that I would paraphrase it as:

A mandate of a stupid practice is worthwhile, if it causes the underlings subjected to it, to pull together to save the project. Even if that means they must resort to insubordination to do so.

Hmm. If a bad commander's policy of 'shoot to kill' eventually causes his troops to rebel and initiate a coup against him, his brutality was justified?

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^10: Module Announcement: Perl-Critic-1.01 (scalar) by BrowserUk
in thread Module Announcement: Perl-Critic-1.01 by jthalhammer

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.