The problem is that I consider it unethical to teach something without knowing it well enough not to introduce well-known bugs. It's just bad for the community at
large to propogate bad memes under the banner of "helping", because it doesn't
help, it hurts.
It's the equivalent to spreading rumors that could harm someone else's reputation without first verifying them from an independent source, which I also consider to be unethical. Why do you think newspapers have such strict rules on "fact checking"?
-- Randal L. Schwartz, Perl hacker
: in response to
Update: I agree with merlyn in general, but I think a gentle suggestion that the author update the node with mention of the bugs and fixes would work just fine. Perhaps it would be even more helpful for a beginner to learn from someone else's common mistakes ? After all, this is a forum.
I would have no problem if the original node had been posted "in quotes", as in "I'm thinking of writing a tutorial, can someone review the following draft before I publish it...". But that wasn't done. It was posted as a done deal, and thus pushed my hotbutton.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||