Updating and Linking Old Nodes

Often when searching pm for a solution I'll discover old nodes with old solutions (as well as new relevant nodes).

For example, searching for SoundEx I found a thread from 1999 (Approximate or Phonetic String-Matching) which didn't mention Text::Metaphone. I'd only discovered T::M from the same search at Re: comparing strings - better than soundex.

Should a good monk help his fellows by responding to the old discussion with updated information or a link to the newer discussion?
Or would it just be clutter, given they'll find it themselves?

A similar predicament occurs when I post a question on pm then some time later find code or read a mailing list discussion which addresses the same question.
Should a monk add links for others?

Brad

Comment on Updating and Linking Old Nodes

Replies are listed 'Best First'.
Re: Updating and Linking Old Nodes by CukiMnstr (Deacon) on Jun 11, 2003 at 08:07 UTC
I wouldn't see it as clutter... When you are serching for something, the precise terms you use for a search maybe won't give you back every thread on that topic. I wouldn't take for granted that they'll find it themselves ;) Also, someone checking out Newest Nodes can see your reply and get to an interesting node that otherwise would go unnoticed. (a few days ago I found an interesting thread this way) hope this helps,	[reply]
Re: Updating and Linking Old Nodes by tjh (Curate) on Jun 11, 2003 at 12:22 UTC
Often when searching pm for a solution I'll discover old nodes with old solutions Often, I enjoy finding old threads about current problems. I've had the experience of the old thread shedding light on why something or some solution evolved the way it did. Also, older data has provided workarounds for 'modern' and broken modules or applications. Should a good monk help his fellows by responding to the old discussion with updated information or a link to the newer discussion? Generally I think "Yes" is the right answer here. Occasionally you'll see that happen Q&A or other areas. In practice it'll never happen methodically, since it's not somehow encouraged by discussion board designs (Everything included.) It's a "here and now" moving window of Today's Questions mostly. It would be wonderful to find a workable paradigm for open source version control on "Know How". Updating 'old' threads might be a stab at that, including change, date and author history.	[reply]
Re^2: Updating and Linking Old Nodes by Aristotle (Chancellor) on Jun 16, 2003 at 13:59 UTC
Such a continuously updated knowledge base is basically what a wiki offers. Makeshifts last the longest.	[reply]
Re: Updating and Linking Old Nodes by coolmichael (Deacon) on Jun 11, 2003 at 20:40 UTC
Speaking for myself, there have been a number of times when I was searching for something, only to discover an old discussion (think two or three years.) Having an updated post in the thread saying, "This has been discussed more recently here" with a link to the new thread would be most helpful, especially to newbies. Just my two cents. -- negativespace.net - all things inbetween.	[reply]
Re: Updating and Linking Old Nodes by artist (Parson) on Jun 11, 2003 at 17:34 UTC
It's 'generally' believed that the newer discussion on similar topics would have better material in the light of older discussion(s). Which may not be the truth all time, but that is what mostly practiced and perceived. Update by author would be certainly better as it will throw the latest information what author believes in the light of his/her new knowledge. It will help wherever people are looking for information. An alternative way is for the seeker to ask/msg the author about more information that he/she has gained till date and provide other insights in the problem as well. It would be interesting that seeker/author updates the knowledge in node in question or/and add in some other form such as QA. Thus know-how here would help to solve the problem rather than just being a piece of knowledge and monastery would be enriched. I certainly like the idea of open-source know-how, mentioned by tjh. artist	[reply]


Do you know where your variables are?
	PerlMonks