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!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||