I agree with both sides of this argument. If all you have to say is "use Grommit::Wallace", then perhaps it'd be nice if you gave someone else a chance to answer.
On the other hand, I don't want to start seeing the POD for CGI pasted into a node every time someone asks a CGI question. And I don't see much point in trying to write a mini CGI tutorial in response to every CGI question.
So what do I want? Well, if you point me to a FAQ or a module (please include a link), I would really like it if you actually tried to find an answer to my question by looking at what you pointed me at. 80% of the time that I'm tempted to post a link, I find that the answer isn't easy to find at that link, or that the answer at that link isn't really a very good one, or that the specific question isn't really answered there even though I had thought that it was. So post a link to the FAQ and a bit of description about how to find the part of the FAQ that pertains to the question and perhaps why you think it is relavent.
It is also often nice to post just excerpts of the documentation that you have given a link to. This is particularly helpful to the people just reading the discussion. I'm rarely so interested in someone else's question that I go read a whole section of documentation. But I very often find it informative to have the answer summarized right there in the node.
- tye (but my friends call me "Tye")In reply to (tye)Re: Don't just provide a module name
by tye
in thread Don't just provide a module name
by gryphon
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |