[sf-perl] Getting Help (was Re: Debugging a CGI script - how)

[David Alban]

there's overlap here with what joe wrote below, but also consider...

  * demonstrate a serious effort on your part before posting your
questions (see 'rtfm'); at the very least, have done a web search and
have consulted the available documentation (see 'perldoc', 'man', and
friends)

  * specific questions will get much better results than extremely
high level / vague / general questions or questions without detail

  * don't post anything that even appears that you want someone else
to do your work for free; note the use of the word "appears"; you may
not intend it, but if it appears that you do you will probably not get
the information you need

  * try and come up with the smallest and simplest code that
demonstrates your problem (if applicable), you'll get fewer responses
if folks have to spend more then five or ten minutes grokking your
problem.

  * if someone cranky flames you, don't respond to the flamey bits.  just don't.

On Sat, Mar 8, 2008 at 1:44 PM, Quinn Weaver <quinn at fairpath.com> wrote:
>  If you have some problem code and want to ask a question about it, please:
>
>  - First try a quick web search (Google or PerlMonks), and consult
>   the standard docs bundled with Perl.  It's amazing how many questions
>   are resolved this way.
>
>  If you do post, please:
>
>  - Be polite.
>
>  - Include relevant code snippets, input data, output, and configuration files.
>   Send the smallest bit that you think is relevant, not the whole thing.
>
>  - Describe the circumstances in which the problem appears, what you've
>   already done to try to diagnose and fix it, and why you're stuck.
>
>  - Be patient with the speed at which people respond.  After all, these are
>   experts who are giving you a free service!
>
>  Thanks,
>  The San Francisco Perl Mongers staff

-- 
Live in a world of your own, but always welcome visitors.