Similarly, the "senior monks" (to borrow your phrase) need to make sure they're not trying to use PSI::ESP; until such time the module's actually released.
By which, I mean:
One student's "homework" might be a transitioning programmer's first project.
Not everyone has time to review 100,000 posts in a community before trying to find an answer to a question.
FAQ's are fine, but only if you know they're there. Perhaps there's a reason people are asking those questions frequently?
Everyone's a newbie at some time or other.
Topicality can be context sensitive. For example, permissions are not a Perl problem, but if you're writing your first CGI program in Perl, "How do I use chmod?" may be an relevant question to ask.
Some people really aren't aware that good software can be licensed and used for free.
We call them "research skills" for a reason; they have to be learned.
Put a slightly different way, it's going to be easier for us to get people to believe that we are an open, accepting community if we treat them nicely while they're learning how the community works.
After all, we're the ones that (presumeably) know what we're doing.
--f
In reply to Re: What makes a bad question?
by footpad
in thread What makes a bad question?
by demerphq
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |