in reply to To thank or not to thank?

User discretion is advised!

If it is just to say "Thank you", you add nothing of content to the thread and is indeed perhaps better done in a /msg. It is more personal and nicer.

A general comment such as "I used solution 'X' rather than 'Y' as it is more sexy" is best put as an update in the original node, but individual comments (which can include a "Thank you!") should be put in their own nodes.

YMMV

CountZero

"A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

Replies are listed 'Best First'.
Re^2: To thank or not to thank?
by blazar (Canon) on Jun 25, 2007 at 22:04 UTC
    If it is just to say "Thank you", you add nothing of content to the thread and is indeed perhaps better done in a /msg. It is more personal and nicer.

    Thank you for your contribution! (This is actually a meta-thanks!) In fact that's what I wrote in the root node too, and what I currently do. Yet, as I also underlined there, it may leave the respondent with Warnock... yes, I also wrote that it would leave people reading the thread with him as well - of course an update cures that. And of course each solution has its own advantages and its best area of application, as you clearly point out. Though there are overlappings. Thus I started this thread to see whether there was some sort of consensus both wrt the current status and if any good idea/brainstorming could get out for an additional "official" solution. Personally I think that simpler nodes with no vote button and limited text content, to be rendered as a footnote to some other node would be very nice to have. But that's just me, and a whole implementation away, of course!

      Thank you for your "Thank you"!

      In the Monastery we fortunately have the XP-system, which gives a rough indication how well the node was received by the other Monks and as such leaves us less "Warnocked" than on usenet.

      CountZero

      A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James