Post History

Source: https://writers.stackexchange.com/a/33626
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/

Source: https://writers.stackexchange.com/a/33626
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/

I like [Secespitus' answer](https://writing.stackexchange.com/a/33617/4216), and I also like [Sphennings' point](https://writing.stackexchange.com/a/33614/4216) about actually answering the question. But I didn't see an answer which combined those two things, and addressed everything I've found important. So I'll write that answer.

## Answer the Question

Not to steal any thunder from sphennings, but I believe this is probably the most important criteria for providing answers. It seems like an obvious rule, but I can fairly consistently find answers which do not answer the question, and instead explain how the OP should in fact be asking something else, or go in a different direction. While potentially quite helpful, these answers also assume the OP hasn't considered all the options. This is a problem when what they talk about is in fact something the OP is already aware of, and knows won't work.

A better practice would be to ask in a comment if the OP has considered X, Y, or Z. If not, and if X, Y, or Z would solve the problem, _then_ post it as an answer. As leftaroundabout pointed out in his comment below, a likely _better_ practice would be to open your answer by actually answering the question, and _then_ explain why you think that answer isn't what the OP is really after. If they've considered that option, then you've already answered the question above. And if not, then your answer will likely help them, not to mention anyone else in the future who might have the same question.

## Clarity

Next to answering the question, it is imperative that the OP can read the answer. This obviously starts with basic writing skills and a knowledge of English grammar, but extends to the use of headers and things like a tl;dr section.

Headers are great for breaking up long answers, as they make it a lot easier to read, and also easier to go back and check a particular section. Secespitus had a great point about getting to the answer quickly, and if that's not an option, a tl;dr at the top is a great addition. Instead of a tl;dr, I will sometimes simply supply a 'short answer', often only one word long, and then label the rest of my answer as my 'long answer'.

## Be detailed

As [Mark pointed out](https://writing.stackexchange.com/a/33615/4216), answers coming in late on a hot question are usually buried under all the early answers and not seen as much. This certainly doesn't happen 100% of the time, as Todd Wilcox pointed out, but it does happen, especially on hot questions where there are lots of answers, and where those answers have at least 3 or so upvotes. Those two things tend to keep your answer at the bottom of the pile.

However, that doesn't mean that you should rush to create your answer. We're after quality here, so that's what you should deliver. I'll often be the first to spot a question, but because I take a long time to write my answer, I've seen as many as three answers come in while I'm writing. This has happened on this question, in fact.

The truth is that a lot of those quick answers are pretty short. They aren't wrong, but they also aren't as detailed as a longer quality answer. They don't take the time to fully explain a concept, and possibly even illustrate it. You can sacrifice being first for having better quality. It consistently gets my answer accepted.

* * *

These are the main criteria I adhere to. There are some obvious ones, like know what you are talking about, but I figure that those go without saying.

Original score: 42