Skip to main content
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
Source Link

The Help Center pageHelp Center page and its Deficiencies

How do I write a good answer?


Thank you 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.

What goes into an answer

Every answer must make at least one insightful observation about the code in the question. Answers that merely provide an alternate solution with no explanation or justification do not constitute valid Code Review answers and may be deleted. In addition to criticisms, pointing out good practices in the code is also a form of helpful feedback.

Answers need not cover every issue in every line of the code. Short answers are acceptable, as long as you explain your reasoning. Do not provide suggestions for improvements in a comment, even if your suggestion makes a very short answer.

Before answering

Not all questions can or should be answered here. Save yourself some frustration by flagging off-topic questions for closure instead. Also, if a question is ambiguous, it may be better to write a comment asking for clarification rather than writing an answer based on an incorrect assumption.

Read the other answers so you don't cover duplicate points. While it is fine to mention points in multiple answers, each answer should contain at least one novel observation.

Organizing your thoughts helps make your answer more readable by grouping related points together.

Tailor your advice to the apparent level of the author of the question, because our goal is to help programmers learn to improve.

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.

Always be polite and have fun

It’s fine to disagree and express concern, but please be civilplease be civil. There is a real human being on the other end of that network connection, however misguided they may appear to be. We are here to learn from our peers, not to yell at each other.

The Help Center page and its Deficiencies

How do I write a good answer?


Thank you 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.

What goes into an answer

Every answer must make at least one insightful observation about the code in the question. Answers that merely provide an alternate solution with no explanation or justification do not constitute valid Code Review answers and may be deleted. In addition to criticisms, pointing out good practices in the code is also a form of helpful feedback.

Answers need not cover every issue in every line of the code. Short answers are acceptable, as long as you explain your reasoning. Do not provide suggestions for improvements in a comment, even if your suggestion makes a very short answer.

Before answering

Not all questions can or should be answered here. Save yourself some frustration by flagging off-topic questions for closure instead. Also, if a question is ambiguous, it may be better to write a comment asking for clarification rather than writing an answer based on an incorrect assumption.

Read the other answers so you don't cover duplicate points. While it is fine to mention points in multiple answers, each answer should contain at least one novel observation.

Organizing your thoughts helps make your answer more readable by grouping related points together.

Tailor your advice to the apparent level of the author of the question, because our goal is to help programmers learn to improve.

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.

Always be polite and have fun

It’s fine to disagree and express concern, but please be civil. There is a real human being on the other end of that network connection, however misguided they may appear to be. We are here to learn from our peers, not to yell at each other.

The Help Center page and its Deficiencies

How do I write a good answer?


Thank you 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.

What goes into an answer

Every answer must make at least one insightful observation about the code in the question. Answers that merely provide an alternate solution with no explanation or justification do not constitute valid Code Review answers and may be deleted. In addition to criticisms, pointing out good practices in the code is also a form of helpful feedback.

Answers need not cover every issue in every line of the code. Short answers are acceptable, as long as you explain your reasoning. Do not provide suggestions for improvements in a comment, even if your suggestion makes a very short answer.

Before answering

Not all questions can or should be answered here. Save yourself some frustration by flagging off-topic questions for closure instead. Also, if a question is ambiguous, it may be better to write a comment asking for clarification rather than writing an answer based on an incorrect assumption.

Read the other answers so you don't cover duplicate points. While it is fine to mention points in multiple answers, each answer should contain at least one novel observation.

Organizing your thoughts helps make your answer more readable by grouping related points together.

Tailor your advice to the apparent level of the author of the question, because our goal is to help programmers learn to improve.

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.

Always be polite and have fun

It’s fine to disagree and express concern, but please be civil. There is a real human being on the other end of that network connection, however misguided they may appear to be. We are here to learn from our peers, not to yell at each other.

replaced http://meta.codereview.stackexchange.com/ with https://codereview.meta.stackexchange.com/
Source Link
replaced http://meta.codereview.stackexchange.com/ with https://codereview.meta.stackexchange.com/
Source Link
replaced http://meta.codereview.stackexchange.com/ with https://codereview.meta.stackexchange.com/
Source Link
Loading
updating to match implemented version
Source Link
Pops StaffMod
  • 101
  • 1
  • 7
  • 19
Loading
Reorganized. Removed requirement for including concrete suggestion for improvement, since praise is also valid.
Source Link
200_success Mod
  • 145.7k
  • 4
  • 114
  • 284
Loading
reworded to avoid redundancy
Source Link
200_success Mod
  • 145.7k
  • 4
  • 114
  • 284
Loading
Tweak grammar.
Source Link
user34073
user34073
Loading
deleted 530 characters in body
Source Link
200_success Mod
  • 145.7k
  • 4
  • 114
  • 284
Loading
deleted 530 characters in body
Source Link
200_success Mod
  • 145.7k
  • 4
  • 114
  • 284
Loading
Updates
Source Link
user34073
user34073
Loading
Updates
Source Link
user34073
user34073
Loading
Source Link
200_success Mod
  • 145.7k
  • 4
  • 114
  • 284
Loading
Post Made Community Wiki by 200_successMod