>But am I doing them a disservice?
>If they blindly use my code snippets
>without understanding, this is a bad thing.
Isn't that what's referred to as cargo cult programming?

My take is to do pointers(à la metadoktor, I include nodes here), and if the problem has been sufficiently explored or is interesting provide some code. This is what I like for people to do with me, and what I sought when I began. I am often slightly dismayed when I come to a node that asks a question relating to the fundamentals. The inquisitor has a chance to truly learn and a monk has succumbed to the temptation to post code, to solve the problem for them. Part of the reason it is good to refer people to documentation is that something other than what they are looking for may get lodged in their casava that they can fetch or have an inkling of use for later. This is why I read through the Camel etc. occasionally. It's also why I read the CPAN uploads for Modules that you want to know but haven't used yet. Then again, I also read the encyclopedia for my own amusement and edification.

--
perl -pe "s/\b;([mnst])/'\1/mg"


In reply to Re: Pedagogy: pointers or plaintext posts by belg4mit
in thread Pedagogy: pointers or plaintext posts by Ovid

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.