Recently several posts asking for debugging help were cross-posted from Stack Overflow to Code Review after people suggested CR in their comments. Debugging is off-topic on Code Review. From our FAQ:

and your question is not about … Trouble-shooting, debugging, or understanding code snippets [emphasis added]

Please do not encourage cross-posts, especially off-topic ones. If you feel that a question belongs on Code Review, flag it for moderator attention and they will migrate it if necessary. Cross-posting and bouncing questions around the network will only raise tempers and keep questions from being answered.


closed as off-topic by Aza, Azik, Shadow The Princess Wizard, doppelgreener, ProgramFOX May 30 '14 at 7:13

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This question pertains only to a specific site in the Stack Exchange Network. Questions on Meta Stack Exchange should pertain to our network or software that drives it as a whole, within the guidelines defined in the help center. You should ask this question on the meta site where your concern originated." – Aza, Azik, Shadow The Princess Wizard, doppelgreener, ProgramFOX
If this question can be reworded to fit the rules in the help center, please edit the question.

  • Examples of such suggestions? I agree with the sentiment, but it's always nice to have examples instead of just anecdotal evidence. – Daniel DiPaolo May 11 '11 at 14:16
  • 1
    @Daniel I edited one in - I have two, but one was author-deleted on both sites. Also see meta.codereview.stackexchange.com/q/308/110 for more background. – Ghost User May 11 '11 at 14:37
  • 1
    So yes, this is bad, but...two posts? I think every site in the network has gotten two bad migrations at some point – Michael Mrozek May 11 '11 at 15:36
  • 9
    @MichaelMrozek We only got one really bad migration from Super User to Gaming (and vice versa, haha), but I still made a post about it. I figure (and recommended this Michael as such), that when it comes to subjects that can reasonably be interpretted as on-topic for those unfamiliar with the site (debugging can be easily seen as a topic for a code review), being proactive and seeding the knowledge of the off-topic nature into the experienced Meta users early will go lengths to preventing it from developing into a serious problem. – Grace Note May 11 '11 at 16:07

Just to make it clear:

Code Review is for working code.

If the code in the question has (known) bugs, errors, problems, or otherwise is not working, it is not a code review question.

  • I added an updated answer. Correct me if I am wrong. – Aseem Bansal Aug 23 '13 at 8:32

It has been two years from the last answer. I'll add an updated one.

Code Review is for working code whose working OP understands.

If you have working code that has been picked somewhere and you want to understand how it works then codereview isn't the place for you. Before posting you should know how it works.

I think this was needed as questions about "How X works" have come to codereview.SE incorrectly.

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