3 ms·
Highly upvoted answers are usually converted into "wiki entries", so that they can evolve, extend and restructure with time. It somehow alleviates the problem,
by nine_k 10y ago
Highly upvoted answers are usually converted into "wiki entries", so that they can evolve, extend and restructure with time. It somehow alleviates the problem, as long as the both sides (asking and answering) care to actually update it.
- jlarocco 10y agoI'm skeptical that happens very often. The only wiki answers I've seen have been hugely popular with dozens of answers and hundreds of votes. Maybe it happens outside of that, but it's definitely not how it "usually" works, IME. Most of the questions I see on SO have maybe 0-5 answers, and the average number of votes is something like 2. If you're lucky there's an accepted answer and/or an answer with a clear majority of votes. I've even seen cases where the accepted answer is wrong, while a more upvoted answer is correct.
- flashman 10y agoSO could be the internet's technical manual if good answers were properly organised and maintained - if the point of providing answers was to document 'how to do programming' and you could only close a duplicate by explaining how to documented answer applies. But the incentive is get in fast, answer and move on to the next question.
- shagie 10y agoThat was the idea behind tag-wikis at one point ( see http://stackoverflow.com/tags/scala/info http://stackoverflow.com/tags/scala/info ) and was the utopian ideal of what Documentation would become. Organizational and writing skill don't necessarily correlate well to programming skill. And when one adds gamification to that allowing for material curated by the masses without the corresponding community investment by those who _do_ have that skill set... well.