Why do you cast downvotes on answers?

Question

This is a question which started off with a comment, then turned into an answer, and now it's a question in its own right (as suggested by Jeff). I'm not sure where it could go from here :)

It's obvious that different people cast downvotes for different reasons. (Upvotes are less controversial, generally.) Here are some possible reasons:

1. Answer is wrong
2. Answer is misleading (may be technically accurate, but will lead to readers making mistakes)
3. Answer doesn't match the question (e.g. a C# answer to a question about Java)
4. Answer doesn't really address the question, e.g. suggesting a completely different solution, even if the question specifies that there are good reasons why the current approach has to be followed
5. Answer is okay, but not as good as another one which currently has fewer votes
6. Answer appears to be plagiarised from existing answers.
7. Answer is by someone I don't like.
8. Answer is abusive (profanity, spam etc).
9. No reason, I just felt like it.
10. I'm a Happy Vertical People Transporter, and prefer down to up. Have you considered down?
11. Ideological grounds: answer suggests a technology I don't like, or expresses a negative opinion of a technology I do like

Personally I go with 1, 2 and 8 - although I'll add comments suggesting changes in various other situations.

Have I missed anything? What do you do, and why? What are the net benefits (to you, the world in general, and the answerer) from your approach?

Answer 1

If I see a bad answer at 0 votes, I generally leave a comment to give the poster a chance to correct or delete it (since the first downvote has been known to trigger a flood of pile-on downvotes). If I check back later and find that it is still wrong and not deleted, I will then downvote.

If a bad answer has already been voted up into, say, the top two or three answers, I will both comment and downvote. I don't want bad answers to be above good answers.

As for what I mean by a bad answer, I would say #1 and (on rare occasions) #6; however, in practice these kind of answers rarely stay around long enough for me to downvote (thus the 27 downvotes in my profile).

For #2, #3, #4, and #5, I'll simply leave a comment. For #8, I'll flag the answer; that already knocks the answer down a notch and potentially leads to -100 reputation for the answerer, so I see no need to penalize both the answer and myself by downvoting also.

Answer 2

I only downvote when the answer is technically wrong and sometimes when it's spam (most of the time I flag spam, rather than downvoting).

Specifically, I don't downvote misleading answers (those that recommend less than ideal solution) if they are technically correct. I handle that by upvoting or providing a better answer and mentioning that in a comment. I believe in any case, it's the responsibility of the reader to make sure the answer is suitable for his/her situation. So if an answer is correct but misleading, while not an ideal thing, it's still not worse than not answering at all. The poster had spent time to post a technically correct answer and shouldn't be punished for that.

I handle all other cases by a comment.

Answer 3

For me the main strength of Stack Overflow is the fact that correct answers "float" to the top. I only ever downvote if I think that the answer is impeding a correct answer floating above it.

FWIW, I never downvote any answer to a question that I have also answered; it seems wrong somehow, even though it's probably not...

Answer 4

I would like to add to the list:

   12. Is plain silly.

This is related to 3. and 4., but it is even worse.

For example, an answer has been upvoted to the top of the list because it is funny, but it does not address the question in any way.

Answer 5

I only downvote when:

• The answer is seriously wrong. This does not include minor syntax issues, typos and the like. The point of SO is to get you on the right path, not provide a comprehensive, fully-debugged program;
• The advice is seriously flawed. This doesn't include differences in opinion. I've gotten downvotes like "-1 just cos I hate VB.NET" and that irks me somewhat. I don't tend to recommend Python for much if anything but that doesn't mean I downvote people who do;
• The answer has nothing to do with the question like if someone asks about database table structure and someone replies how you should be using Ruby on Rails;

As for your abusive answer downvote, I don't downvote there. I just flag it. If it doesn't meet the standard for being flagged does it justify a downvote?

Answer 6

At different times, I've down-voted answers for any or all of #1, #2, #3, #5, and #9. I'll usually try to leave comments for the first three reasons, unless someone else already has; I'll rarely bother leaving comments for any of the other reasons.

I'll also down-vote a question if I think it's poorly asked, argumentative, asks for something dangerous, or is blatantly off-topic.

Answer 7

1. Seriously wrong answers

2. disrespectful answers, right or wrong

3. and always leave a comment explaining each downvote (question or answer)

<rant>I strongly suspect that the drive-by downvoters which are the source of most if not all irritating unwarranted uncommented downvotes will not have the courtesy to explain their actions here, since they don't bother to do it there either!</rant>

Answer 8

I try to vote according to the rule: helpful or unhelpful. In practice this probably corresponds to your 1, 2 & 8, though 2 is probably harder to judge than 1 & 8. Typically, I will only upvote the first and/or best correct answers -- they are not always the same. More complete answers are to be preferred over correct, but incomplete answers. For example, an answer that contains a link to some document that describes the correct answer probably won't get an upvote from me if there is an answer that both references the link and quotes from it. I wouldn't give a downvote to the linked answer because it's helpful but not as helpful as it could be.

As a general rule I try not to downvote unless I feel the answer is actively unhelpful.

I also tend to not downvote questions -- only answers. I prefer to flag or vote to close questions rather than downvote.

Answer 9

One reason for which I won't downvote is 6: "Answer appears to be plagiarised from existing answers."

This is:

• specifically encouraged in various forums (podcasts, blog entries)
• likely to result in an answer that is better than all the rest, since it can take the good and leave the bad.

In fact, I'll often upvote it.

Answer 10

I'll downvote for a misleading answer that I can't easily correct with a comment. I see no reason in pushing anything below -1. (There's also the issue that a sympathy upvote for a downvote will raise the answerer's reputation, which I'd rather not happen.) If there's a better answer, I'd rather upvote the better one. I won't downvote a good answer just because it isn't the best.

I also don't think it's cricket to downvote without a comment, except if the answer was obviously grossly bad.

So, put me down for 1 and 2, sometimes 3 and 4 and 8.

Answer 11

I just down-voted an answer for my very first time.

And the reason was: The "answer" was nothing more but a complaint, that the question of the OP was not yet answered. Additionally, the language he used was very colloquial in a manner that I feel very nerving. I think, this is a place where we can talk/write like adults. I don't mean perfect english (my English is learnt from school, I am German). But we don't need no

Somebody just fix this silly thing plz cuz i needa take my pics from the SanDisk Memory Card

here, I think.

Answer 12

I down vote readily, if warranted.

Basically, I look at the answer and decide if it's helpful, or not, and that will guide my votes.

So, I'll downvote if the answer is wrong (#1), misleading (#2) or shows signs that the answer author hasn't read the question fully/properly (#3, #4).

Abuse I'll flag - and most of the other reasons listed are more reason for me to UP-vote someone else instead.

Answer 13

I'll also downvote any answer to a blatant homework question, where the OP has shown zero effort towards actually doing the problem. Allowing these answers just further contributes to the OP's thought that "hey I'll just let the guys on Stack Overflow do this one for me".

Downvoting and explaining this (often to "young" answerers) often leads to self-deletion of the answer.

Examples:

• https://stackoverflow.com/questions/19468668/verify-a-number-is-odd-or-even/

Answer 14

13, sometimes I downvote 'clutter' - i.e. you sometimes have half a dozen one-line answers which are all saying the same thing but not adding anything to the discussion.

Answer 15

I've downvoted for a variation on 11. Some answers are basically a loaded opinion in favor or against a particular technology (e.g. snide remarks about Windows) and nothing more.

I'm pretty loose with my down voting. SO is supposed to be about quality answers. Low quality answers get downvoted.

Answer 16

I downvote for 1, 3 or 4. I'll downvote a misleading answer only if it's leading in an especially bad direction: towards obsolete technologies, for instance. I'll usually just comment things like leaving out "using" blocks in C#, unless I feel the poster should really have known better than to set such a bad example (you know who you are).

Anything else, and I'll either comment or just leave it alone.

Answer 17

A downvote reason missing from your list is "Though the answer was correct and accepted, the answerer said something negative in comments about a technology for which I am a rabid advocate". I ran into that one recently.

On the plus side, the guy did leave me a helpful comment explaining his downvote. Which is nice; I wouldn't have known to assign him zero credibility in all future matters, otherwise.

Answer 18

It's mentioned above but I prefer the bubbling up approach. Answers that are wrong are generally poorly written, or too short (my answers fit these), so I assume the average programmer (given that they are mostly well educated and have an IQ above 120) will ignore the poorly written answers, and only upvote the good ones.

I'll upvote people who have made the effort to do a well written response but haven't given the exact answer I'm after, or if I've learnt something from the answer.

I'm probably far too "green" and not ruthless enough in my approach.

Answer 19

Almost always (1). I could probably exhaust all my downvotes every day on answers that are simply and objectively wrong. If you don't believe me, try posting a simple question regarding C on SO - you will immediately get about four or five answers that show that the answerer has not a clue about C and are syntactically and semantically wrong.

I don't know if this is true of other languages, as the only ones I really follow are C++ (which seems somewhat less affected) and C. But the C bad answers are really bad.

Answer 20

I will downvote for:

1) mostly

2) sometimes, depends on how seriously misleading and whether it can be easily corrected

3) rarely, if it really looks like the information won't translate at all

7) for one very special person

8) for spam, see here for a succinct statement of my (highly offensive) opinion on profanity

However, one of the most important considerations as to whether I will downvote anything is whether my rep presently ends in 5, in which case I will likely only downvote things I feel extremely strongly about, or presently ends in 0, in which case I will probably not downvote anything at all.

I never claimed not to be crazy.

Answer 21

This is not an answer to the question, but it's definitely not a comment on the question itself:

I upvote downvoted answers when I feel that they've been wrongly downvoted. I do this especially when the downvote is clearly for reason #11.

I've done the same thing with downvoted questions, and on SO I find that there are many gems amongst the questions that are rated -1 and below.

At the same time, to answer the question: I downvote rarely, and I almost always downvote highly upvoted questions. I do this when the answer is terse, arrogant, and uninformative (though it may be technically correct). This is a subspecies of #5, I guess.

Answer 22

Here's another one for you, Jon: "Because my answer on the same question got downvoted". There's been a lot of that this morning on SO.

I would call it short-term vindictive downvoting, as opposed to your #7, which is long-term vindictive downvoting.

Answer 23

I downvote obvious wrong answers, especially for #3. However, I will be less likely to downvote if an answer's vote is too low, and I will more likely to downvote to make my reputation multiple of 5.

Answer 24

My reasons: 1, 4, 6, 8 and whenever someone tells that you should have looked up the answer on Google.

Wrong answers should be clearly marked as wrong. I will downvote the answer and explain why it's wrong. In these cases, I will also confirm or add the right answer!

Answers that don't address the question are just noise. They're distracting and can often make others think the Q has been answered already. Many people will still add answers if the number of answers is reasonably low but this noise just increases the number thus decreasing the chance that someone else will add the right answer...

Answers that are copies of other answers are also noise, although I can understand a duplicate answer if it's added almost immediately after the first one. (Within 5 to 10 minutes.) But if someone posts a duplicate long after someone else posted an answer, even if both answers are wrong, I will downvote them to mark them as noise.

Profanity has no place on these sites and will be downvoted even if the answer is correct. (And flagged for deletion.)

Finally, I get really pissed off when they just answer that you'd have to Google for the answer. If you still add the (correct) answer then that's okay but only sending someone to Google is not enough. These answers need to be downvoted into oblivion since these are bigger insults than all other reasons to get downvoted.

Answer 25

If the answer works, but there's better ways to do something, I might downvote.

For example, if someone was suggesting doing the following Ruby code

def my_function(input_array)
  result = []
  input_array.each do |element|
    result << element * 2
  end
end

without telling them about the map function, then the OP might think that that's the best available way to do things, when it isn't.

Answer 26

I usually downvote for 1 or 3. I may downvote for 4 or 8.

For 8 I may also flag. For 2, 4 and 5 I usually leave a comment.

I will downvote for 5 if the question asks about the best way to do something.

I don't think it's a good idea to downvote for 6. For the people reading an answer the important thing is whether it is good. Where the answer came from is secondary and I wouldn't penalize a good answer.

On SO I see quite a number of people who don't care about 3 and this really surprises me.

Answer 27

1. Answer is wrong

Yes.

Answer is misleading (may be technically accurate, but will lead to readers making mistakes)

Yes.

3.Answer doesn't match the question (e.g. a C# answer to a question about Java)

It's probably better to just leave this answer to rot on its own. Leaving a comment can be appropriate.

4.Answer doesn't really address the question, e.g. suggesting a completely different solution, even if the question specifies that there are good reasons why the current approach has to be followed

This is not so clear at all. Often enough OPs will claim something is a restriction only to deliberately steer answers to some pre-conceived idea. If the question truly gives believable and valid reasons something is not possible, then just let the answer rot as for #3. However, sometimes thinking outside the box is good, so this may even be a reason to upvote.

5.Answer is okay, but not as good as another one which currently has fewer votes

Then upvote the other, not downvote something that isn't wrong.

6.Answer appears to be plagiarised from existing answers.

That is hard to determine for sure unless it really is a copy and paste. Otherwise, you can just not upvote if you only think it might be a copy.

7.Answer is by someone I don't like.

Seriously?

8.Answer is abusive (profanity, spam etc).

This really should be flagged. Downvoting in the mean time doesn't hurt.

Sometimes I downvote these when they are at 0 only so that I can then vote to delete. You can only vote to delete answers that are negative.

9.No reason, I just felt like it.

Again, seriously?

10.I'm a Happy Vertical People Transporter, and prefer down to up. Have you considered down?

This is not how the site is supposed to work.

11.Ideological grounds: answer suggests a technology I don't like, or expresses a negative opinion of a technology I do like

Only if there is a reasonable argument that the technology in question is inappropriate for the question. If you simply don't like something without there being a good technical reason against it, then this is vandalism.

Basically answers should be downvoted when they are wrong, misleading, or so badly written they are undecipherable or annoying to read.

Answer 28

I could imagine a case where an answer could be downvoted in order to help the answerer to have an opportunity to get the Peer Pressure badge.

Note: I wouldn't do that.