I found myself looking for some place to point a new user on why his answer wasn't a good answer. I couldn't find anything except the fairly unhelpful Help page's "How do I write a good answer".

So, I'm putting it to the community. What makes for a good code review? What are the essential parts? What pitfalls should we avoid?

I think this answer to a different question is a pretty good start.


1 Answer 1


In a different context, I listed contents of a good answer.

I'll do something slightly different here, which is to list some attributes of a good answer. Good answers…

  • 4
    \$\begingroup\$ Would you consider adding something like - aim to educate about not just what but why a change is suggested \$\endgroup\$
    – Phrancis
    Commented Jun 18, 2014 at 21:50

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .