What a terrible article. I'm sorry for the rant, but this really pissed me off.

Admittedly, I don't participate in StackOverflow that much right now - I sort of go through an ebb and flow where I get really gung ho about answering questions, then it sort of wears off for a while - but this guy sounds a lot like he wants to game the system, and is only in it for the points.

I'm not trying to put words in Jeff/Joel's mouth, but I think the "answer before you comment" system is constructed the way it is so that noise can be reduced. By that, I mean that the system wants you to actually contribute something to the site to get used to how it works before you can "join the discussion". Comments aren't downvotable, presumably because they don't want to silence dissenting opinions in a discussion, and the average comment doesn't get upvoted at all. If anyone could just walk in off the street and leave a comment, you would end up with a bunch of "YouTube comments" being left by random passersby.

For a newbie, your only way to contribute to a question is to write an answer. Answering has a different social contract than does commenting. When you answer a question, you are expected to provide, well, an answer! If your answer is incorrect, then it will be downvoted to distinguish good information from misinformation. Downvoting is a way of saying "this content is harmful", and this is a perfectly valid response to a bad answer, but not a valid response to a bad opinion (i.e. a comment you disagree with).

If the OP provided answers on StackOverflow and was downvoted, then his answer most likely was simply wrong. I haven't seen many, if any, correct answers with negative scores on StackOverflow. The system tends to be fairly self-correcting in that respect. If someone is downvoted wrongly, there is more often than not another user who will upvote the answer back to zero. If the OP is simply lamenting that he isn't receiving upvotes (in contrast to the idea that he's being downvoted, which is a separate concept), then maybe his answer simply isn't as good as he thinks it is, and the "flawed answer" he wants to comment on simply isn't that flawed.

If the flawed answer is indeed flawed, then there is no harm in adding a new answer. Simply write your own detailed answer and include evidence explicitly proving that the current top voted answer is incorrect. When you post an answer, the site will kick the question back to the front page of the site, so you should get the opportunity for your "correct" answer to get exposure, and if it's any good, it should get upvotes.

What I take the most issue with in this article, however, is the OP's lament that any question he wants to answer is already answered. That's the whole point of the site! If the question is already answered, then the system is working. The site doesn't exist for answerers to get points; it exists for askers to get answers to their questions. If a question gets a lot of responses, that is a Good Thing.

Now, OP used to have a valid point about having a lot of "in progress" answers being posted. This was the so-called "Fastest Gun in the West" problem, and was solved by modifying the site to display same-scored answers in a randomized order. At this point, an "in progress" answer which doesn't yet provide enough value shouldn't have any upvotes, and therefore a new answer would have the same opportunity to be viewed as that answer. If you get your answer into a steady-state first, then you will get upvotes and you will get views. If someone else does, and gets upvoted, then at least the asker will get a proper answer to their question. If you're complaining about other people giving "minimum viable answers" which nonetheless help the asker, then you're probably just "rep whoring".

For my part, I tend to answer questions in the same way. I'll quickly add an answer which provides a technically correct answer that at least gives the asker enough to finish the answer on their own (for example, "This can be accomplished using the some_function function" is enough of a hint that it's useful - the asker can look up the some_function documentation and learn for themselves). Once that answer is in place, I'll go back and edit the answer to include links to the documentation (I'll usually save at this point), then add a thorough explanation of how the answer works and how to use it.

I've been commended by askers and other users for my in-depth answers to questions, and I've even beaten the "horde of already submitted answers" due to my quality. O a few occasions, I've come to a question that already had 5+ answers with "minimal correct answers", some of which have upvotes, and have written an answer with a lot of detail which ended up either the highest voted, or accepted by the asker (or both).

Basically what I'm saying is that if you're only trying to be a "rep whore" then yes, the system is against you, but that's a Good Thing. If you're in it to actually help people, then taking the time to write a detailed, quality answer is the best way to go, and it'll often net you points to boot.