Hello fellow monks,

just curious... found Learning how to answer because I was asking myself something similar. Not because of XP, mind you, that's just fun and imho the best way to ensure feedback, but because of the quality of answers. Now, that node is some years old; time to raise the question again. Or has it been yet? afaik there was no poll about it...

Depending on how this proposal is voted, I'd compile a non-FAQ entry for the FAQ on how to answer (It's just wonderful to browse this site.) See shmem's scratchpad for a draft; obvious things? are there not so obvious?

Would you provide node links for good/bad examples? (but not mine, I know them :)

cheers,
--shmem

update: removed objectionable cruft about XP

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

Replies are listed 'Best First'.
Re: On How To Answer
by jpeg (Chaplain) on Jun 24, 2006 at 03:29 UTC
    There are nearly as many approaches to composing a reply as there are perlmonks. timtowtdi, etc.

    This is a community and I think it's most useful in seeing the diversity of your fellow monks' approaches to answering SoPW questions or contributing code they may think is useful. I really think the most rewarding approach is to use the site, really use it: dig through the snippets, tutorials, cufp, and code sections. Upvote what you find useful, if rating means something to you. Read through the SoPW sections. Try to answer some; if someone actually teaches the seeker (or the seeker actually learns something) - it's worthy of an upvote IMO.

    I keep a list nodes I find valuable, but I doubt they'd have much significance to you. We're all at different points in our journeys with perl and programming.

    --
    jpg
      jpeg++, I second all you say. But you get this by experience.

      Being an experienced monk you don't need the FAQ any more, except for What shortcuts can I use for linking to other information? and such.

      And you will need an how to answer as little as How do I post a question effectively?. This one is meant for beginners. Not having it is like saying "post along. We will not tell you if we will blame you for it for obvious reasons", which is arguably a good approach. Or not.

      cheers,
      --shmem

      _($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                                    /\_¯/(q    /
      ----------------------------  \__(m.====·.(_("always off the crowd"))."·
      ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}
Re: On How To Answer
by McDarren (Abbot) on Jun 24, 2006 at 01:21 UTC
    I believe that Erudil has already covered this topic quite adequately :)

    Update: - okay, perhaps that was a bit dismissive of me - my apologies. Yes, I think a FAQ on answering questions is perhaps a good idea :)

    However, saying "I didn't do this for XP" sort of turns me off a bit. Saying it three times turns me off even more. It reminds me too much of a politician - "I'm not cutting taxes because there is an election coming up - I'm doing it because it's the right thing to do" ...yeah, right.

    Anyway, looking at your what you have so far on your pad - I'd say it's a good start. There is just one point I would take issue with:

    "Don't say module Foo::Bar does the trick"

    Why not?
    In many cases, that's all that is required. Quite often, the OP doesn't need to be spoonfed an answer - they just need be pointed in the right direction. I think the main point is that a good answer is one that is tailored as best as possible to the level that the OP is at. Of course that's not always easy to judge, so a bit of guesswork is usually involved.

    I think the best guideline one could adopt for answering questions here in the Monastery, is to attempt at all times to remain humble. I say this because I know it's something I have to constantly remind myself of.

    Cheers,
    Darren :)

      All that's behind the bullet was meant to be one point. It read:

      • Don't give non-solvers.
        If the OPs question is fuzzy or their code bad, point it out.
        Don't say module Foo::Bar does the trick

      Now it reads:

      • Don't give non-solvers: if the OPs question is fuzzy or their code bad, point it out, instead of saying module Foo::Bar does the trick and done.

      The thread Deleting by Age! is a good example. The OP didn't need a module but be pointed back at their code, and told to formulate their needs in a coherent way - and then eventually be advidsed to use a Module.

      I think the best guideline one could adopt for answering questions here in the Monastery, is to attempt at all times to remain humble.
      Very true. And an obvious point that must be pointed out, for anybody to whom it isn't obvious...

      Erm... and on the politician stuff. I had the idea to declare this node a poll, which ain't. It doesn't work. Its a node. That's why I had said not for XP.

      To ask for feedback is ok, but if I think there should be a FAQ entry covering how to answer, then I'll just do it. Then there's a node, which eventually will be linked into the FAQ. That's the right way.

      Thanks for the link and your comment, McDarren. Hmm. Why isn't 1st Monasterians up front?
      --shmem

      _($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                                    /\_¯/(q    /
      ----------------------------  \__(m.====·.(_("always off the crowd"))."·
      ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}