Use some of the excess to downvote bad nodes; i.e., the "gimme, cuz I faked my knowledge of perl to get my job';" the homework nodes; the self-contradictory nodes (for exceptionally bad cases); and the nodes with content that boils down to a spec (possibly deficient) and a statement to the general effect that "my code doesn't work." Then spend some time clearly explaining why the node falls short of the standards suggested in the various FAQs.
Some consider this bad advice because downvoting bad nodes "might hurt the little darling's sense of self-worth" or might discourage a noobie, among others.
The noonbie argument may have some value, so instead of downvoting the first-timer who appears to HAVE MADE AN EFFORT TO FOLLOW OUR GUIDELINES, explain, clearly and gently, how to improve the node so that it does satisfy our guidelines --- does provide the code, data and spec that we need to actually be helpful.
If you didn't program your executable by toggling in binary, it wasn't really programming!
-
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.
|
