-3
\$\begingroup\$

This question already has an answer here:

When should a answer be "accepted" since in Code Review it is a opinion review, and not a fact-based answer that points to a problem in a code (or something like that), and any opinion can be good enough?

For example, user A says a opinion and user B says another in their reviews. But which one must be chosen The One? After all, opinions are indifferent to each other when rated by someone neutral to them.

\$\endgroup\$

marked as duplicate by Mast, nhgrif, Vogel612, Quill, Phrancis Jan 8 '16 at 0:01

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

11
\$\begingroup\$

The asker should mark as accepted the answer which they found most constructive.

It's not an objective thing (on any of the Stack Exchange sites even). It is entirely the opinion of the asker. It's a super upvote, if you will.

\$\endgroup\$
5
\$\begingroup\$

While Code Review answers can deal with opinions, they often deal with accepted best practices, bug fixes, and other non-opinionated improvements. As @nhgrif says, accept the one that helped you the most. Sometimes, this is the answer that covers the most, sometimes it is the one that points out an obscure bug. It really depends on the circumstances.

\$\endgroup\$
  • \$\begingroup\$ I'd say that in many cases, it really is about opinions. I have written comments many times of the form "I like your answer, but do not agree with X because I think Y" \$\endgroup\$ – Simon Forsberg Jan 8 '16 at 7:44
  • \$\begingroup\$ @SimonForsbergMcFeely This better? \$\endgroup\$ – Hosch250 Jan 8 '16 at 10:48

Not the answer you're looking for? Browse other questions tagged .