Checklist for migration to Code Review

1. Is the question off-topic on the originating site?

• Are you sure? Do not migrate if there is doubt.

2. Is the question on-topicon-topic for Code Review?

• The question must contain working code. Code Review is not a debugging service. Reviewers may discover bugs in the course of answering, but the code should be generally correct in the first place.
• If the code is hosted externally, the code that lies at the heart of the question must still be written directly in the question itself.
• Code excerpts are fine, but they must be recognizable as code that would appear in a real project. Hypothetical code (such as code that uses foo as an identifier), stub code (with unimplemented placeholders in places central to the question), or pseudocode (not in a real programming language) are not suitable for Code Review.

3. Is the question calling for a code review?

• The author of the question must be an author or maintainer of the code.
• Requests to explain others' code are off-topic.
• In Code Review, answers may cover any aspect of the code, including the algorithm, data structures, code organization, naming, and style. (The code in the question must be preserved as the author intended — including whitespace.)

4. If there are answers already, they must be good answers on Code Review too.

• Good Code Review answers explain how to improve the code.
• Answers that just contain code with no explanation are not allowed.
• If the answer proposes a completely different solution, there should also be a mention of why the approach is superior to the original code.

5. Has the question already been asked on Code Review?

• Please check for duplicate questions from the same author.
• Questions with different code to perform the same task are not considered duplicates on Code Review.

If you are unsure whether a question is a good candidate for migration to Code Review, feel free to ask for an opinion in our chat room.

Checklist for migration to Code Review

1. Is the question off-topic on the originating site?

• Are you sure? Do not migrate if there is doubt.

2. Is the question on-topic for Code Review?

• The question must contain working code. Code Review is not a debugging service. Reviewers may discover bugs in the course of answering, but the code should be generally correct in the first place.
• If the code is hosted externally, the code that lies at the heart of the question must still be written directly in the question itself.
• Code excerpts are fine, but they must be recognizable as code that would appear in a real project. Hypothetical code (such as code that uses foo as an identifier), stub code (with unimplemented placeholders in places central to the question), or pseudocode (not in a real programming language) are not suitable for Code Review.

3. Is the question calling for a code review?

• The author of the question must be an author or maintainer of the code.
• Requests to explain others' code are off-topic.
• In Code Review, answers may cover any aspect of the code, including the algorithm, data structures, code organization, naming, and style. (The code in the question must be preserved as the author intended — including whitespace.)

4. If there are answers already, they must be good answers on Code Review too.

• Good Code Review answers explain how to improve the code.
• Answers that just contain code with no explanation are not allowed.
• If the answer proposes a completely different solution, there should also be a mention of why the approach is superior to the original code.

5. Has the question already been asked on Code Review?

• Please check for duplicate questions from the same author.
• Questions with different code to perform the same task are not considered duplicates on Code Review.

If you are unsure whether a question is a good candidate for migration to Code Review, feel free to ask for an opinion in our chat room.

Checklist for migration to Code Review

1. Is the question calling for a code reviewoff-topic on the originating site?

• The author of the question must be an author or maintainer of the code.
• Requests to explain others' code are off-topic.
• In Code Review, answers may cover any aspect of the code, including the algorithm, data structures, code organization, naming, and style. (The code in the question must be preserved as the author intended — including whitespace.)

2. Is the question off-topic on the originating site?

• Are you sure? Do not migrate if there is doubt.

3. Is the question on-topic for Code Review?

2. Is the question on-topic for Code Review?

• The question must contain working code. Code Review is not a debugging service. Reviewers may discover bugs in the course of answering, but the code should be generally correct in the first place.
• If the code is hosted externally, the code that lies at the heart of the question must still be written directly in the question itself.
• Code excerpts are fine, but they must be recognizable as code that would appear in a real project. Hypothetical code (such as code that uses foo as an identifier), stub code (with unimplemented placeholders in places central to the question), or pseudocode (not in a real programming language) are not suitable for Code Review.

3. Is the question calling for a code review?

• The author of the question must be an author or maintainer of the code.
• Requests to explain others' code are off-topic.
• In Code Review, answers may cover any aspect of the code, including the algorithm, data structures, code organization, naming, and style. (The code in the question must be preserved as the author intended — including whitespace.)

4. If there are answers already, they must be good answers on Code Review too.

• Good Code Review answers explain how to improve the code.
• Answers that just contain code with no explanation are not allowed.
• If the answer proposes a completely different solution, there should also be a mention of why the approach is superior to the original code.

5. Has the question already been asked on Code Review?

• Please check for duplicate questions from the same author.

If you are unsure whether a question is a good candidate for migration to Code Review, feel free to ask for an opinion in our chat room.