Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 153 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Possible Duplicates:
The bike shed problem and SO
Why do non-programming questions get many responses?
Why is “subjective” the top upvoted tag for questions?

If someone provides a detailed and deeply insightful technical answer to a tough question he/she may get rewarded with 5 or 10 up votes. But if someone answers a question like, "Which is better, C# or Java" they will hit the daily limit. Is there anything we can do to fix this?

share|improve this question

marked as duplicate by Robert Cartaino, Ether, fretje, juanformoso, random Mar 8 '10 at 0:42

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.

ok this is controversial but.. If the question is extremely technical and specific to a certain language, why should it have more votes than a question such as "how do you concatenate strings in C#"? Almost no one cares about the first question, a lot of people care about the second. Therefore, the second is a better question: it helps more people and brings new users to the website from google. If you see the upvote tooltip it says helpful, not difficult. Difficult, localized and highly technical questions are rarely helpful to the bast majority of our users. – Andreas Bonini Mar 6 '10 at 15:02
The "bike shed problem" has been discussed here before:… and somewhat related:… – Robert Cartaino Mar 6 '10 at 16:26
Actually, I totally agree with you Koper. SO should definitely be used to ask easy and hard questions. What irks me is the "subjective" questions getting all the attention, despite the fact that this is explicitly something chartered against. – RickNotFred Mar 6 '10 at 17:30

Because more people are interested in the general questions, and thus attracting more people. And more people visiting the question equals more people upvoting the question.

It's hard to do anything about it, because of this fact.

share|improve this answer

It's the Bikeshed effect, partly. Few people are competent to comment on a deeply insightful answer to a tough technical question, and in fact relatively few people are going to look at it. A whole lot of people can answer soft questions, and will likely upvote, and feel competent to upvote the answers.

share|improve this answer

There are many many ways in which StackOverflow is "inefficient". Questions are rewarded by the time of day in which they're asked, how they're asked (my highest scoring question was closed as subjective and argumentative :), which technologies they ask about (C# vs. S-plus, for instance), etc. Highly technical questions and specific questions are just not as sexy.

IMO, the question is not whether SO rep is working. The question is: is SO rep working somehow to produce a great technical site. The answer is that, in spite of hundreds of thousands (millions) of idiotic tendencies, bad answers, stupid questions, and bad voting, on the hole (whole?) SO is a great place to ask programming questions and get answers.

Back to your question: what can be done about this? You could start making all kinds of strange hierarchies (highly technical question: points doubled; rare technology stack: bonus points) but overly engineered social systems usually backfire and end up with people doing all kinds of weird stuff just to get more rep. Less rules=less gaming... I think.

share|improve this answer
+1 totally agree. Plus, interestingly, even though SO rep is not necessarily a reliable indicator of technical expertise, I have not yet seen a high-rep user who wasn't good at what they are doing. – Pëkka Mar 6 '10 at 14:00

This isn't necessarily true.

Most of the time, if a question is really broad or has far-reaching implications, it's going to end up as a Community Wiki post, which doesn't generate reputation. There are exceptions, of course. But if someone asks a really good question, they definitely should be rewarded for adding a significant amount of value to the community -- as it should be.

That being said, there's nothing stopping people from upvoting a post, even if it's a specific technical question that might be classed as "difficult" -- it's just that perhaps that kind of question wouldn't get the same exposure, or have people be familiar enough with the subject to even say if it's a good question or not. In that sense, it is kind of backwards, but at the same time, if you're asking that specific of a question, it's likely to be an issue localized to only a handful of people and of lesser benefit to the community.

If you think of reputation as a measure of how much value someone has added to the community, then I think your problem will be resolved.

share|improve this answer

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