Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 7
    for the record, suggestion on how to pick between Looks Good and Recommend Deletion is provided here: "1. Does the post attempt to answer the question? No Delete, Yes goto step 2. 2. Would it be possible for a reasonably-intelligent English-speaking person familiar with the topic to understand the solution being presented? No Delete, Yes Looks Good."
    – gnat
    Commented Sep 20, 2013 at 10:56
  • 1
    How should I review answers with code as image? It might help, but the recommendation for such questions is to delete. So what about answers? Commented Jan 12, 2021 at 9:48
  • 1
    How to deal with posts that only have some lines of code without any explanation and where I'm unable to improve the answer?
    – robsch
    Commented Apr 2, 2021 at 18:55
  • Further to what @robsch said: What about an answer that's super brief and without any explanation? On Stack Overflow, these seem to constitute a lot of the auto-flagged answers. Assume we're not a subject matter expert. Do we just assume that they're ok? Commented Apr 9, 2021 at 18:13
  • A quick idea: As long as the answer has low quality, allow upvotes but supress that the author gets the reputation points. On review there should be an option to let the author know that fact. S/he gets (back) the points if the answer or question is considered to be good enough. However, that rmight equire something like a re-review.
    – robsch
    Commented Apr 12, 2021 at 12:38