Here's my approach: while I can, at times, provide the in-depth answer, I find the most satisfaction from identifying with the questioner and answering specifically to his/her level.
For example, in the midst of a "grep/not grep" debate, with code snippets and benchmarks coming fast and furious, the original poster may be entirely lost. I like to write a clear, patient description of the issue(s) describing the pros and cons of various techniques. If the supplicant is a beginner, (s)he will be more interested in an understanding of that cool array slice everyone keeps using -- rather than an esoteric debate over hashes vs. Schwartzian Transforms.
Explain an issue that you have recently learned, tailoring your post to guide readers along the same path you have taken. perlfunc:grep was one of mine. When I discovered grep, it was amazing how many "perfect" uses emerged. So, I tried to explain/use grep to solve problems. See grep! (My favorite <em>this</em> week, anyway...) and Re: diff of two hashes., for examples.
Look for a topic you can explain completely and clearly, even if it takes no code. RE: Random number (CGI Security)
Perl Monks is a great place to learn and share what you have learned, no matter what "level" you are.
Welcome, initiate marvell! Thanks for jumping on in.
Russ
Brainbench 'Most Valuable Professional' for Perl
In reply to Re: Wanting to help (answer to the asker's level)
by Russ
in thread Wanting to help
by marvell
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |