Well, showing efficient code is not necessarily a bad thing. I think the problem is when the newbie's question gets twisted into a golf challenge! If someone's new to the language, I think it's better to provide them with something that may use up a few more symbols, but is easier to understand.
The recent thread on Removing Duplicates in an array is a great example. The first answer is an RTFM , followed by two rounds of golf. I'm not pointing fingers at the people who posted; I've done all of these myself. (I think RTFM answers are appropriate sometimes, but indicate where in the FM to R! If a clear and detailed writeup is available, provide a link to the node or external page.)
I don't think a separate node type or area for "newbie questions" is really necessary. We just need to indicate somehow that the emphasis in SOPW answers should be on clarity and simplicity of the code. Efficiency always counts, but don't sacrifice legibility and ease of understanding for a few cycles.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||