If on an electrical forum, someone advised OPs to test for mains connection by sticking their fingers in the socket; they'd rightly have their posts removed.

Bad programming advice and suggestions may not be life threatening; but they are a waste of a newbies time, potentially career threatening, and poisonous to Perl's reputation if followed.

The war against one Monk's perceived incompetence seemed childish when it amounted merely to downvotes and snide comments. Now we're moving solidly into cyberbullying and censorship.

There is nothing "perceived" about his incompetence; and no "war" from my perspective. It's not his name I consider, but his content. If he doles out bad advice on cgi or html, that's for others to consider; but when it's on a subject I know a little about and he obviously knows nothing, I take it as my responsibility to protect newbies from his blathering.

As for patience. I first started questioning his content in 2008; by 2010, I'd started politely asking him to "Show me the code" and expending considerable efforts demonstrating how out-of-date(about 30 years) his suggestions were; and some mild mocking to try and get the point across.

See here for more of the history.

I think moving to using consideration, only after 9 years of questioning, exhaustively demonstrating, gentle mocking, outright & forthright telling him to stop wasting other people's time with his terrible -- sometimes bordering on criminal -- "help", has demonstrated more than enough "monk-ly patience".


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
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". The enemy of (IT) success is complexity.
In the absence of evidence, opinion is indistinguishable from prejudice. Suck that fhit

In reply to Re: Patience is a Monk Virtue by BrowserUk
in thread Patience is a Monk Virtue by marinersk

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.