The Help Center page and its Deficiencies
How do I write a good answer?
Thanks for taking the time to contribute an answer. It’s because of helpful peers like yourself that we’re able to learn together as a community. Here are a few tips on how to make your answer great:
Pay it forward
Saying “thanks” is appreciated, but it doesn’t answer the question, and such answers will be removed. Instead, upvote the answers that helped you the most! If these answers were helpful to you, please consider saying thank you in a more constructive way – by contributing your own answers to questions your peers have asked here.
Have the same problem?
Still no answer to the question? Help us find a solution by researching the problem, then contribute the results of your research as a partial answer. That way, even if we can’t figure it out, the next person has more to go on. You can also vote up the question or set a bounty on it so the question gets more attention.
Answer the question
Read the question carefully. What, specifically, is the question asking for? When you answer a question, you don't need to cover each point; in fact, covering only a few points and having a small answer can even be good. Be sure to explain why you made each change you made instead of just providing a code dump with the improved code.
Provide context for links
Links to external resources are encouraged, but please add context around the link so your fellow users will have some idea what it is and why it’s there. Always quote the most relevant parts of an important link, in case the target site is unreachable or goes permanently offline.
Write to the best of your ability
We don't expect every answer to be perfect, but answers with correct spelling, punctuation, and grammar are easier to read and tend to get upvoted more frequently. Remember, you can always go back at any time and edit your answer to improve it.
Answer well-asked questions.
Not all questions can or should be answered here. Save yourself some frustration and avoid trying to answer questions which...
- Are unclear or lacking specific details that can uniquely identify the problem.
- Solicit opinions rather than facts.
- Require too much guidance for you to answer in full, or request answers to multiple questions.
- Include broken, hypothetical, or missing code. Please flag such questions as off topic.
- Are not about code review request as defined in the help center.
Don't forget that you can edit the question you're answering to improve the clarity and focus - this can reduce the chances of the question being closed or deleted.
Always be polite and have fun
It’s fine to disagree and express concern, but please be civil. There’s a real human being on the other end of that network connection, however misguided they may appear to be. We’re here to learn from our peers, not to yell at each other.
