Meta Stack Exchange is a question and answer site for meta-discussion of the Stack Exchange family of Q&A websites. It only takes a minute to sign up.
Sign up to join this community
I asked a question recently, looking for examples of an online tool. Per the FAQ, I answered my own question with a few examples that I had already found. I did this so that these examples would be included in the answers, along with the rest.
The question has received only down votes and insults saying that this shouldn't be done.
Should I not answer my own questions?
You should answer your own question, and you can get the Self-Learner badge for doing so if the answer has 3 votes.
Furthermore, in order to keep your accept rates up, you should consider answering and accepting those tricky questions nobody answered properly.
Jeff & Joel have specifically said this is allowed.
No, it's okay to answer your own question. Ignore the trolls. Every web community, no matter how good, has a few.
You should, as Jeff Atwood repeatedly states in the podcasts, this site is about building a knowledge base.
Answering your own question is perfectly fine, especially if it's the right answer.
The guy doesn't know what he's talking about. Jeff & Joel have specifically said this is allowed. However, posting a question for which you obviously have an already prepared answer is often seen as 'begging' for reputation, and therefore may not get as many upvotes. On the other hand, asking a question often leads the asker to find the answer for themselves, so they usually aren't downvoted either.
It's a tricky situation. I have questions in my head where I can think of a few answers, but they aren't the only answers.
Posting my own answers looks like I'm fishing for points; not posting makes everyone repeat work I've already done. Marking my answers as Community Wiki helps avoid that stigma.
Answering your own question is fine by me. However, for FAQ-type questions such as this one, I think we ought to make them community wikis, so the rep is mainly based on programming knowledge.
Yes, you can definitely do this.
I've even seen people post a question, and then post a fully thought out answer to it about 30 minutes later. It was clear they knew the answer - they just felt it was an unanswered question that they could answer for the community. So feel free!
It seems we all agree that answering your own question is acceptable.
I'd like to point out that the alert box that appears when you do so is intimidating. It certainly gives the impression that you may be doing something wrong.
Other than the haters, this may be a reason people may get confused on the issue. I was. I do understand the purpose of the box is to be sure you are entering responses in the correct spot (comments vs. answers).
I've done this, but explicitly stated in my question that I would give my answer separately. In your case, yours is the only answer to the question and may give the impression that you are just seeking votes to increase your reputation. I did not take it that way, though.
I also agree with @ScottieT812. This should be a community wiki question.
Lately, in cases where I saw that the original asker answered their own question (either as a direct addition to the collaborative wisdom or after some research), I tend to add a straight copy of the original answer (making my copy community-owned and stating clearly in a small header that this is a copy), in order to be chosen as "the" answer, and let the upvotes be given to the original answer (or any other the voters deem helpful).
I don't know if this helps, but I believe so. I like to see answered questions as answered. I also suggested in uservoice that self-answered questions should be allowed (and chosen!) only if your answer is community-owned (and therefore no rep points are given).
So others would vote up the question if it's helpful, vote up the answer if it's helpful (and no karma-whoring), and no-one would think that the person asking is just showing off or whatever.
It is great to answer your own question and it is great that you found the answer yourself.
Keep in mind, answering any question in a clear, concise manner is great for someone down the road that stumbles upon this question and easily gets the answer to the same question he or she had.
There is at least one situation where I find answering your own question mildly annoying.
If I'm perusing the list of questions, looking for something I can answer, then see a question which I know the answer to, I like to jump on it. Help a fellow out.
Then I'm halfway done writing an answer and the little "Another answer has been posted" banner pops up. I refresh the page to see that the asker has immediately answered his own question, meaning that there was no actual question.
No one wanted to know the answer, because the asker wasn't actually having a problem when he wrote the question. Even if I beat him to his own answer, it wouldn't matter because I wouldn't be helping him, he already knows a working answer.
This situation just wastes my time.
I don't mind answering your own question, but I would like it if one would only post a question if they (at the time) want an answer that they don't have. It's fine to answer your own question later if you discover the answer, be it trial-and-error, research, or a combination of other people's answers.
The difference would be akin to a man asking for the time.
The man asks if anyone has the time. No one answers right away, but someone does mention that it's sometime after 10 o'clock. He realizes that there is a clock on the wall and mentions aloud "Oh, never mind, I see that it is 10:40."
The man asks if anyone has the time. One person speaks up "It's ten fo..." but is interrupted by the first man who, while checking his watch, states "It's 10:40, just in case anyone wanted to know."
For the sake of argument, let's assume that it will always be 10:40 in whatever room this man is in.
Answering your own question is perfectly acceptable, so I don't know why you got downvoted.
Considering that in the question you referred to, the timestamps between the post and your answer were less than two minutes apart, I guess asking a question just to immediately answer it comes off a little bit like showing off to some ;)
Might be better to put your examples in the question in future.
I think that the main reason that people bagged on you was because you posted an answer only seconds after posting the question.
If your question was one where a solution could be worked out from the question (eg math questions, what’s wrong with this line of code, etc.), then it could have been explained in that typing out the question in a formal way caused you to view the problem in a new way that led to a Eureka! moment, allowing you to answer it immediately.
However, your question was one whose answer could not be derived from the problem (you asked for examples of sandbox webapp sites). Therefore, the fact that you posted an answer in less than a minute of the question, people (in my opinion rightly) found it to be quite suspicious, and that’s why you got hit.
If you’re going to do that sort of thing, at least wait an hour or so before posting an answer. That way it looks like you continued researching the problem while waiting for someone to post an answer, and found one on your own (ie, the whole point of having a self-learner badge).
I was reading through this question, and it made me think of a few simple rules for questions + answers. Some of these are in the official question guide, but not all:
Don't ask a question you have the answer to already - If you figured it out, likely others will too. Let someone else who doesn't know the answer ask the question - then you can legitimately help them. If you really struggled to find the answer to your question you might consider posting with the last bullet point in mind.
Ask Real Questions - Don't try to imagine a situation then ask questions about it to get points. This doesn't help the community as much as a real question and situation would and it just creates clutter.
Don't try to create a wiki - Often if you are going to try to create a wiki it will end up being too broad of a topic for a simple Q&A site like stack. These types of articles are best left to a blog. Of course, there are some cases for posting "articles" as questions (see: Posting articles on Stack Exchange), but I think this should be done with the next rule in mind.
Remember that stack is a community -- expect feedback. That means you want to get feedback back from your question. This feedback might be more correct, easier to understand or simply more elegant than what you already wrote. Give your question some time to allow the community to respond then honestly consider these answers. Make sure you award the accept badge to the answer you consider to be the best, even if it wasn't your answer.
By the way, of course all the normal rules still apply (Research before you ask, look at other stack questions to avoid asking duplicate questions, include relevant code examples, etc).
