Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
How about this, then? Why not add page to your site that explains cargo-cult memes, a correct solution, and why it's correct. As you encounter people who are either victims of bad memes ("This doesn't work, why?"), or people propogating bad memes ("Your problem is this, here's how to fix it."), you can add these to your web page, with well-worded explanations that explain why the meme is bad, what the risks are, and the correct way to do it, and *why*. And perhaps, if you know the original source of the meme, a little history ("The original module required this work around, later version do not, this is not longer required, and in fact, exposes this vulnerability").

Then, instead of whacking them between the eyes, and leaving many of them stunned, senseless, confused, and annoyed, you can link to your page, and specific article, and re-educate them (and perhaps gain XP, instead of losing it...)

The reality is this: Just because you say it loudly, or repeat it 4 times, doesn't necessarily mean it's right. If I don't know who merlyn is, you're just another user. And I'm not about to go to research on each and every person who gives me an answer to determine if suddenly they're someone who's opinion I should respect. Lots of people know who you are, but a lot more don't.

I imagine that the time you would spend writing each rant would be far less than inserting a link to a page that could be re-used each time. Heck, you might could even get your own section in FAQ, or something.


e-mail jcwren

In reply to (jcwren) RE: On identifying cargo cult items... by jcwren
in thread Regarding style by footpad

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.