I thought I might be misreading it which is why I said, "Maybe it's me", but it did seem to have a curt tone. More than a couple posts of merlyn's have struck that chord with me. Don't get me wrong. I probably use one of his books or articles every single day. Even if he was unbelievable belligerent (He's not), I'd still listen to him because he knows a hell of alot more than I and I've learned a hell of a lot too.
Like I said, this thread is not a particulary worthy example, but what I was more addressing is an attitude I've perceived at the Monastery.I really think there is a lot to be learned by doing things the hard way
sometimes. I use modules all the time, but when I started, I didn't have the luxury. Hell, I didn't have docs for most stuff. Just wading through ASM,C and x86 docs from the library. Trial and Error is a tough way to learn but I think you learn a lot more from solving a problem than reading it's answer.
I'm not suggesting rebuilding the wheel over and over, If someone asks a question and there is a good module, that's the first place I'll point them, but I've noticed that if someone doesn't want to use CGI.pm for instance, a lot of monks just start scolding.
Now, if someone doesn't want to take their time solving a problem that has already been solved, I can totally respect that, but I don't think there is a need to harp on the person asking. Most people will just give up anyways and come around to the CGI.pm way. And the ones who stick it out? Maybe they'll come up with something even better. (As an aside, I almost always use CGI.pm or subclass it to meet my CGI needs)
Just my 2 cents.
-Lee
"To be civilized is to deny one's nature."
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.