While I don't think doing a search should be required before every SoPW post, it might be a good idea to require reading of certian nodes, such as how not to ask questions, before one's first SoPW. In any case, I think the best system to get good questions out of people is a combination of the two existing ones. First, downvote bad questions, and upvote good ones. Second, when somebody posts a "code this for me" node, tell them what they've done wrong, in a helpful and non-abusive way. "You might want to look at Some::Module; if you show us some code we'll give you specifc help". If there's some search they should have done that's fairly obvious, link to the search, and not to the results, or at least explain how you got the results.

"I searched on search.cpan.org for 'ping', and found Net::Ping" is much better then "look at Net::Ping.

Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).

In reply to Re: Loads of Nodes by theorbtwo
in thread Loads of Nodes by AcidHawk

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.