You forgot two:

  1. TROLLING Finished polishing your last script? Have a little time to kill? Feeling ignored? Just hop over to PerlMonks and start a thread about ... oh about anything, really, it doesn't matter, but be sure to include a phrase that matches /not \s+ use \s+ CPAN .* module/xms. Poking a fire ant mound with a stick is about the closest equivalent to the mindless swarming and biting this will provoke.
  2. AD HOC BAYESIAN ADVICE FILTERING Say you value PerlMonks for its wisdom and advice, then you are left with a problem: What advice is good? How can you tell? This problem is a social network analog to that of email spam. Here is a heuristic on how to proceed:
    • Get a pad of paper and a pencil
    • Troll a thread as per the point above, but include an actual valid reason for not using CPAN. Two reasons that strangers are never able to gainsay without some claim to omniscience are, "My company won't allow it," and "I cannot have external dependencies". There are others.
    • Come back to the thread in about a day. Write down the user names of the responses and weight them as you will. Remember, the point is not to mark down people for advocating CPAN, but to mark down people for mindlessly advocating CPAN.
    • Keep this list of weighted user names next to your computer or taped to the laptop case. Refer to it when in doubt about the probable sagacity inherent in a future post.

    For the advanced learner, send a quick email to Paul Graham asking how he'd automate this. Then open a thread asking monks to help translate some lisp code to perl. Be sure to mention that the conversion can't use CPAN modules....

In reply to Re: Top 11 (GOOD) reasons not to use someone else's Modules by Anonymous Monk
in thread Top 11 (GOOD) reasons not to use someone else's Modules by miketosh

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.