Please substantiate the two unsupported assertions you make in...
"but most people posting here are intermediate-level Perl programmers and will learn more and faster by reading through a finished solution than by being told to go look at x, y, z modules
and, please provide objective support for the value judgment you offer in...
"it just seems lazy for people who know the answer to reply with module links rather than taking the time to code a short solution...."

I can't provide any data to support my view, either, but the notion that most of the SOPW are posted by "intermediate-level Perl programmers" seems, at best, questionable. How many intermediate programmers have to post SOPW like "how do I remove a leading space" or ones that are rooted in vast ignorance of the differences among OSen? We certainly see a lot of those.

Likewise, I lack evidence for my disbelief of your "learn more and faster" proposition, but my own view (based, obviously on far-less-than-rigorous analysis) is that too many times a complete code solution is greeted with a follow-on to the general effect of "please explain how that works" or -- worse -- "wow, thanks; that works perfectly." without any hint that OP has done anything beyond simply adopting the solution provided. For more on this, please see the discussion (the discussion, not the trolls) re BrowserUk's excellent point.

As to your value judgement ("lazy"), it's my view that providing a reply with good teaching value (ie, with acknowledgement, for example, that a particular solution may be useless in circumstances upon which the OP is ambiguous) is often (usually?) more work than simply providing code.

In reply to Re^3: Put some of the posting guidelines directly above the posting form: by ww
in thread Put some of the posting guidelines directly above the posting form: by TJPride

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.