Indeed. As nobull is often quoted over on c.l.p.misc:
Get real! This is a discussion group, not a helpdesk. You post something -- we discuss its implications. If the discussion happens to answer a question you've asked, that's incidental. If you post a question that implies that you've got a problem finding answers to trivial questions in the manual, then it is perfectly reasonable for us to discuss how to do that.
It's quite clear in my mind that much of the value in a site like Perlmonks isn't in getting an answer
. It's in getting people thinking about how
to solve the problem. At first glance, those might look like the same thing, but they really differ quite a bit. It's nice that the person asking gets help, but it'd be selfish to count on such a large resource to give up at one answer. The very broad array of ways in which programmers can solve problems lends naturally to discussion, and that's where deeper learning happens.
We should especially be accustomed to TMTOWTDI in the Perl community, and discussion of options rather than a simple answer or a guided thought exercise seems the natural route to me.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||