As a decent chappy, I want to help. However, it would
that every time I get to question, it's been answered,
often multiple times.I don't want to answer the same question again, just for
the XP, it seems pointless. Is there an easy way that "unanswered" questions, in any
section of the site can be easily identified?
--
Brother Marvell
Re: Wanting to help
by BigJoe (Curate) on Dec 01, 2000 at 18:24 UTC
|
Something else you can do is: Even though others have answered it, verify their work. So that the user asking for help is getting help and not a headache. I am also a big fan of "Another Way". If you see a question you could answer differently help out your fellow monks and post it.
--BigJoe
Learn patience, you must. Young PerlMonk, craves Not these things. Use the source Luke. | [reply] |
Re: Wanting to help (answer to the asker's level)
by Russ (Deacon) on Dec 01, 2000 at 22:25 UTC
|
Excellent comments throughout this thread!
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 | [reply] |
Re: Wanting to help
by swiftone (Curate) on Dec 01, 2000 at 21:04 UTC
|
It is indeed hard to get to a question first. Often you will answer to find that you've been beaten out by an identical answer (or three!)
One way I got early XP was to be verbose and thorough. Rather than fixing the bad reference usage in a post, explain the concept behind references and helpful uses. Rewrite sections of code. Run Search and Super Search and put up links to previous nodes that addressed the issue.
Another good place for new users to grab XP is from vague questions. If you can weasel out what the user means, you can often be first to answer.
In many ways, new users do the most work, while higher level monks can just sit on their laurels and answer the easy stuff.
This post, for example, isn't addressing your question of identifying unanswered nodes. :) Normally I just want Newest Nodes and refresh every minute or so. When a new node appears, there's usually a 30 second window in which to answer :)
I believe someone has a Newest Nodes client, check ZZamboni's or Shendal's home nodes for info. | [reply] |
Re: Wanting to help
by chromatic (Archbishop) on Dec 01, 2000 at 21:19 UTC
|
I had the idea recently that higher level monks could mark a post 'not needing an expert'. It would be voluntary, but having a marker on a post would indicate that it's not a question that will send one of us to the Perl source code for a definitive answer.
Less experienced monks would get a chance to give an answer.
I think a great portion of the knowledge I've accumulated over the past year has come from answering questions. Why deny others the same chance? Especially since I've answered questions with "You can do that with grep, but use a hash instead" more often than I'd like. :) | [reply] |
|
One thing I learned while doing Martial Arts was that you
learn as much by teaching as you do by being taught. That
lesson applies to Perl and much more.
You also learn to be clearer to a wider audience.
| [reply] |
Re (tilly) 1: Wanting to help
by tilly (Archbishop) on Dec 02, 2000 at 12:07 UTC
|
I try to limit myself to answers that I don't think that
anyone else here would come up with. I admit to not always
succeeding in that, but I have been pleasantly surprised at
how often I can do that. Even if a question has been
answered, there may be a way to bring up something important
that the existing answers don't.
I think it is good if higher level monks try to do that.
As chromatic says, why deprive others of the valuable
learning experience of trying to answer people's questions? | [reply] |
Re: Wanting to help
by kilinrax (Deacon) on Dec 01, 2000 at 18:10 UTC
|
| [reply] |
|
However, there answer status is not marked. I guess I'll just
have to keep a close eye on it.
--
Brother Marvell
| [reply] |
(Blue) Re: Wanting to help
by Blue (Hermit) on Dec 01, 2000 at 21:32 UTC
|
I understand where you're coming from. PM is blessed by the presence of several active Perl gurus. Curse their bones. {grin} Often I will go to answer a question, and be intimidated by the quality and depth of answers before me.
I suggest just plunging into answering. Newest Nodes is a good place to start if you park your browser here, otherwise it's hard to find a node with no answers. Look for a node where you have something to add - even though others have answered, you have have either an alternative viewpoint, a bit more depth, or a clearer example. Don't worry about 'first post', like at some other online community that shall remain nameless, just add where you can. That's all any of us can do.
=Blue
...you might be eaten by a grue... | [reply] |
|
|