I appreciate a thank-you, particularly if it gives a little explanation of how the final solution turned out. I'm here to learn through contributing, if that makes sense. When I see an interesting question I do a little research, and provide an answer. Some answers are more helpful than others, but either way I learn something along the way too. If I later hear how a question was resolved, I gain a little more insight. A thank-you thrown in there is always welcome.

That being said, those times where I've been on the giving end of a thank you, I haven't seen much voting activity on such nodes. Not that I'm looking for people gushing all over a thank you with upvotes, but I sometimes am left wondering if the person I'm responding to noticed. I'm in the habit of upvoting any thank you directed at me because, in the back of my mind, it almost feels like a nod or acknowledgment in response to the appreciative node.

There are those who feel that thank yous damage the signal to noise ratio around here. There is something to be said for that. I find it annoying when I'm reading a thread and the OP has issued a thank you after each and every reply he gets. That tells me nothing. I don't learn which response helped him to solve his problem. All it does is add chafe to the thread. So this goes back to my original statement, "particularly if it gives a little explanation of how the final solution turned out." Let the OP wait and reserve the thank yous for once the thread has had a little time to mature. And at that time, one at the end is plenty.

If a person feels inclined to give an immediate token of appreciation, especially several times in the progress of a thread, use votes and the /msg box to thank people. At the end, summarize how things turned out.

Opinions expressed in this post are those of ...me... ;)


Dave

In reply to Re: Are short "thank you" posts within discussions welcome at Perl Monks? by davido
in thread Are short "thank you" posts within discussions welcome at Perl Monks? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.