Thinking the accepted answer is the "right" answer is a common mistake made by people who aren't aware of how Stack Overflow works.
Accepting an answer is not meant to be a definitive and final statement indicating that the question has now been answered perfectly. It simply means that the author received an answer that worked for them personally.
Okay but is this a failure of the user or an unintuitive UX? We can't just expect to pass cognitive burden onto users in a million places. UI affordances and conventions exist for a reason.
I imagine that's what causes the confusion. The big green check is a Q&A site model ("this worked for me") but the site is intended as a documentation site ("this is how you do it"). It's a bit strange to have one question closed as a duplicate of another one that has an answer that only worked for the other question asker.
Comments
Thinking the accepted answer is the "right" answer is a common mistake made by people who aren't aware of how Stack Overflow works.
https://stackoverflow.com/help/accepted-answer
Okay but is this a failure of the user or an unintuitive UX? We can't just expect to pass cognitive burden onto users in a million places. UI affordances and conventions exist for a reason.
I imagine that's what causes the confusion. The big green check is a Q&A site model ("this worked for me") but the site is intended as a documentation site ("this is how you do it"). It's a bit strange to have one question closed as a duplicate of another one that has an answer that only worked for the other question asker.