3 ms·
Yes, the stackexchange (implicit) model contributes to this. It assumes once a Q has been asked and answered, the issue is resolved. Due to the non-duplicates p
by _Gyan_ 6y ago
Yes, the stackexchange (implicit) model contributes to this. It assumes once a Q has been asked and answered, the issue is resolved. Due to the non-duplicates policy, any corrections or updates are supposed to be added to the same thread. But the original accepted answer will have a tick mark next to it and likely a high score. So naive users don't read further and the obsolete answers remain heeded.
Some sort of deprecation or salience decay needs to be added.
- madeofpalk 6y agoYou can edit the accepted answer!
- _Gyan_ 6y agoI don't like to mix voices - that's inorganic when the changes are more than minor and can lead to parts of the 'answer' being at odds with itself. Except for typos, syntax..etc, I don't edit someone else's answer; I leave a comment and let the original respondent edit.