Should you downvote an answer that "works" because it is not strictly "correct"? [duplicate]

Question

A question is raised and two answers are posted:

• The first is a solution that adheres to best practice and industry convention
• The second uses a kludge to get the right result

How should voters act in this situation? Am I encouraged to vote up an answer simply because it answers the question? Should I be down-voting an answer that strays from best practice?

For example, someone may ask how to pull out an attribute from a specific line of XML:

• Answer 1 would demonstrate use of XPath
• Answer 2 uses a regex to extract the attribute.

Answer 1

I would upvote Answer 1 and not upvote Answer 2. Correctness is about more than just accomplishing the end goal. In other words the ends do not justify the means.

A good answer needs to not only provide a solution but it needs to provide a solution in a manner that adheres to best practices.

I wouldn't downvote the second answer but I don't think it deserves an upvote along with the better answer simply because it works.

Answer 2

This is where the lack of granularity of up/down votes gets sticky. For me, you have three categories:

1. Answers which provide the right information - these get upvotes
2. Answers which provide incomplete information or a solution that works but isn't a particularly good idea - no vote of any kind, perhaps a comment explaining the shortcoming
3. Answers which don't answer the question, are factually wrong, or are simply so terrible as to make me sad - downvote

Of course, I doubt even half of the community treat it the same way, which is either a blessing or a curse, depending on who you ask.

Answer 3

No, you should edit it and make it correct and safe. Or failing that, identify the scenarios in which it will break badly, and point them out via comments... Then down-vote with self-righteous fury at the short-sighted programmers now-a-days.

Answer 4

In my opinion, bad advice is worse than no advice. The bad advice could be taken to heart by a novice who doesn't know any better.

But whether or not to downvote, to me, really depends on how much of a kludge the second answer is. If it is a particularly bad kludge, I would downvote it. If it seems to have received more upvotes than it deserves, I will downvote it. Otherwise I'd just leave it.

I would always leave a comment explaining why it is a bad idea (or upvote an existing comment which says why). I think a comment with 8 upvotes that says "wait a minute this is a bad idea" would deter users more than a negative vote total.

Answer 5

I think this is precisely how and why the SO voting system works. Some will look at that and upvote both, many will upvote the first and not vote on the second and a few may downvote the second as bad practice. Personally, I'm not inclined to downvote for something that works but is not best practice because there is a better way. But regardless, in the end I believe the votes work themselves out so that the answer with the best practice in it ends up at the top and the one that works but might not be advisable is second in line, above those that don't answer the question at all.

Answer 6

It could be that the asker cannot use XPath for some reason, then he is happy for a workaround. Even it is dirty (yeah, you are right, there are no clean workarounds).

Answer 7

I would say vote up the most correct answer (at the time of your voting). So in your example, I would vote up the XPath answer unless the questioner specifies that he doesn't have a real XML library and so couldn't use XPath.

Answer 8

I would downvote only if the kludge answer out-scores the best-practices answer. It's all about having the best answer float to the top. Then I would probably also leave a comment letting the answer know why.