Return to Answer

They should probably each be short and encapsulate the idea that:

1. You want a review on every facet of the code, not just some.
2. The code in question works as intended.
3. The code in the question is actual code, not hypothetical or pseudocode.

Phrancis brought up a good point in chat: There should also be something to the effect of

If all three criteria are met, please delete this question and post it on Code Review.

Put all that together, and you get something like this:

This question looks like it might be a pretty good fit for Code Review.SE, provided that (a) you want every aspect of your code reviewed, not just some, (b) your code is already working, and (c) you're asking for a review of concrete, real code, not abstract design (whether or not it's expressed as code). If you agree with all of those, please read about what's on topic, and, if your question fits that, delete it here and repost it on CR.

Or, in copypasta-friendly format:

This question looks like it might be a pretty good fit for [Code Review.SE](http://codereview.stackexchange.com/), provided that (a) you want _every aspect_ of your code reviewed, not just some, (b) your code is _already working_, and (c) you're asking for a review of _concrete, real code_, not abstract design (whether or not it's expressed as code). If you agree with all of those, please read about [what's on topic](http://codereview.stackexchange.com/help/on-topic), and, if your question fits that, delete it here and repost it on CR.

Reminder: The character limit for comments is 600 characters. The current one is 541 characters.

NOTE: This post is Community Wiki for a reason, but I'd appreciate it if you gave others a chance to provide input on changes by commenting before you edit, unless it's something trivial like fixing a spelling mistake.

They should probably each be short and encapsulate the idea that:

1. You want a review on every facet of the code, not just some.
2. The code in question works as intended.
3. The code in the question is actual code, not hypothetical or pseudocode.

Phrancis brought up a good point in chat: There should also be something to the effect of

If all three criteria are met, please delete this question and post it on Code Review.

Put all that together, and you get something like this:

This question looks like it might be a pretty good fit for Code Review.SE, provided that (a) you want every aspect of your code reviewed, not just some, (b) your code is already working, and (c) you're asking for a review of concrete, real code, not abstract design (whether or not it's expressed as code). If you agree with all of those, please read about what's on topic, and, if your question fits that, delete it here and repost it on CR.

Or, in copypasta-friendly format:

This question looks like it might be a pretty good fit for [Code Review.SE](https://codereview.stackexchange.com/), provided that (a) you want _every aspect_ of your code reviewed, not just some, (b) your code is _already working_, and (c) you're asking for a review of _concrete, real code_, not abstract design (whether or not it's expressed as code). If you agree with all of those, please read about [what's on topic](https://codereview.stackexchange.com/help/on-topic), and, if your question fits that, delete it here and repost it on CR.

Reminder: The character limit for comments is 600 characters. The current one is 541 characters.

NOTE: This post is Community Wiki for a reason, but I'd appreciate it if you gave others a chance to provide input on changes by commenting before you edit, unless it's something trivial like fixing a spelling mistake.

They should probably each be short and encapsulate the idea that:

1. You want a review on every facet of the code, not just some.
2. The code in question works as intended.
3. The code in the question is actual code, not hypothetical or pseudocode.

Phrancis brought up a good point in chat: There should also be something to the effect of

If all three criteria are met, please delete this question and post it on Code Review.

Put all that together, and you get something like this:

This question looks like it might be a pretty good fit for Code Review.SE, provided that (a) you want every aspect of your code reviewed, not just some, (b) your code is already working, and (c) you're asking for a review of concrete, real code, not abstract design (whether or not it's expressed as code). If you agree with all of those, please read about what's on topic, and, if your question fits that, delete it here and repost it on CR.

Or, in copypasta-friendly format:

This question looks like it might be a pretty good fit for [codereview.SE], provided that (a) you want _every aspect_ of your code reviewed, not just some, (b) your code is _already working_, and (c) you're asking for a review of _concrete, real code_, not abstract design (whether or not it's expressed as code). If you agree with all of those, please read about [what's on topic](http://codereview.stackexchange.com/help/on-topic), and, if your question fits that, delete it here and repost it on CR.

Reminder: The character limit for comments is 600 characters. The current one is 541 characters.

NOTE: This post is Community Wiki for a reason, but I'd appreciate it if you gave others a chance to provide input on changes by commenting before you edit, unless it's something trivial like fixing a spelling mistake.

They should probably each be short and encapsulate the idea that:

1. You want a review on every facet of the code, not just some.
2. The code in question works as intended.
3. The code in the question is actual code, not hypothetical or pseudocode.

Phrancis brought up a good point in chat: There should also be something to the effect of

If all three criteria are met, please delete this question and post it on Code Review.

Put all that together, and you get something like this:

This question looks like it might be a pretty good fit for Code Review.SE, provided that (a) you want every aspect of your code reviewed, not just some, (b) your code is already working, and (c) you're asking for a review of concrete, real code, not abstract design (whether or not it's expressed as code). If you agree with all of those, please read about what's on topic, and, if your question fits that, delete it here and repost it on CR.

Or, in copypasta-friendly format:

This question looks like it might be a pretty good fit for [Code Review.SE](http://codereview.stackexchange.com/), provided that (a) you want _every aspect_ of your code reviewed, not just some, (b) your code is _already working_, and (c) you're asking for a review of _concrete, real code_, not abstract design (whether or not it's expressed as code). If you agree with all of those, please read about [what's on topic](http://codereview.stackexchange.com/help/on-topic), and, if your question fits that, delete it here and repost it on CR.

Reminder: The character limit for comments is 600 characters. The current one is 541 characters.

NOTE: This post is Community Wiki for a reason, but I'd appreciate it if you gave others a chance to provide input on changes by commenting before you edit, unless it's something trivial like fixing a spelling mistake.

They should probably each be short and encapsulate the idea that:

1. You want a review on every facet of the code, not just some.
2. The code in question works as intended.
3. The code in the question is actual code, not hypothetical or pseudocode.

Phrancis brought up a good point in chat: There should also be something to the effect of

If all three criteria are met, please delete this question and post it on Code Review.

Put all that together, and you get something like this:

This question looks like it might be a pretty good fit for Code Review.SE, provided that (a) you want every aspect of your code reviewed, not just some, (b) your code is already working, and (c) you're asking for a review of concrete, real code, not abstract design (whether or not it's expressed as code). If you agree with all of those, please read about what's on topic, and, if your question fits that, delete it here and repost it on CR.

Or, in copypasta-friendly format:

This question looks like it might be a pretty good fit for [Code Review.SE](http://codereview.stackexchange.com/), provided that (a) you want _every aspect_ of your code reviewed, not just some, (b) your code is _already working_, and (c) you're asking for a review of _concrete, real code_, not abstract design (whether or not it's expressed as code). If you agree with all of those, please read about [what's on topic](http://codereview.stackexchange.com/help/on-topic), and, if your question fits that, delete it here and repost it on CR.

Reminder: The character limit for comments is 600 characters. The current one is 541 characters.

NOTE: This post is Community Wiki for a reason, but I'd appreciate it if you gave others a chance to provide input on changes by commenting before you edit, unless it's something trivial like fixing a spelling mistake.

They should probably each be short and encapsulate the idea that:

1. You want a review on every facet of the code, not just some.
2. The code in question works as intended.
3. The code in the question is actual code, not hypothetical or pseudocode.

Phrancis brought up a good point in chat: There should also be something to the effect of

If all three criteria are met, please delete this question and post it on Code Review.

Put all that together, and you get something like this:

This question looks like it might be a pretty good fit for Code Review.SE, provided that (a) you want every aspect of your code reviewed, not just some, (b) your code is already working, and (c) you're asking for a review of concrete, real code, not abstract design (whether or not it's expressed as code). If you agree with all of those, please read about what's on topic, and, if your question fits that, delete it here and repost it on CR.

Or, in copypasta-friendly format:

This question looks like it might be a pretty good fit for [codereview.SE], provided that (a) you want _every aspect_ of your code reviewed, not just some, (b) your code is _already working_, and (c) you're asking for a review of _concrete, real code_, not abstract design (whether or not it's expressed as code). If you agree with all of those, please read about [what's on topic](http://codereview.stackexchange.com/help/on-topic), and, if your question fits that, delete it here and repost it on CR.

Reminder: The character limit for comments is 600 characters. The current one is 541 characters.

NOTE: This post is Community Wiki for a reason, but I'd appreciate it if you gave others a chance to provide input on changes by commenting before you edit, unless it's something trivial like fixing a spelling mistake.