I'm pretty new to the Stack Exchange network. I'm currently teaching myself programming and have been getting help with code issues on Stack Overflow. I've used Code Review a couple times and found it helpful, but users want working code to review. So my question is (if one wanted to stick to just one website), which site it better for help with code?

  • 4
    Also, multi-posting (we incorrectly call it "cross-posting" around here) is explicitly not allowed. Do not post the same message on two different sites.
    – JDB
    Sep 2 '13 at 13:55


Stack Overflow is there to help with specific coding issues.

Code Review is there for making working code even better.

There is no Stack Exchange site for debugging code for you.

  • I very much agree, but it seems to me we're not voting to close such debugging questions a lot. And now that "too localized" is gone, I wouldn't even know which close reason to select?
    – Arjan
    Sep 2 '13 at 20:43

Adding on to Oded's answer, the purpose of the Stack Exchange sites is to create a repository of knowledge for future visitors. Asking a specific question, like "Why does calling foo from bar when baz is set to qux result in error xyz?" may be useful to other visitors with the same specific issue.

But debugging questions, like "This code doesn't work. Can you spot the problem?" really is not useful to others. It's useful only to you and only for today. Even if you learn something, it's unlikely that that information will be discoverable by others. That's why we don't allow general "I don't know where the problem is" debugging questions.


Neither site will work for you unless you learn to use the tools and focus the problem.

Code review is to ask people, 'is there a better way to do this?' People there are not going to be great enthusiasts for 'this has a bug it it, can you please locate Waldo for me?'

And stackoverflow is legendarily unsympathetic.

If you need help learning to use a debugging tool, stackoverflow is there for you. You'll need to phrase questions that focus on the tool, not your buggy code.

If you need help coming up with a debugging approach to some complex misbehavior, you'll again need to phrase a question in terms of your need for help with an approach or technique for isolating the problem, rather than for someone to do your work for you and find the bug.


Don't stick to just one site: use each for what it's intended. Asking for a code review of working code on SO will fail, just as asking a "Why doesn't my fobricate() call work?" will fail on CodeReview.

Learn to use the right tool for the job.

  • 4
    Learn to use the right tool for the job. - I think that's what the OP is trying to do.
    – JDB
    Sep 2 '13 at 13:41
  • 2
    @Cyborgx37: quite possibly, but the "if one wanted to stick to just one website" shows that he's not quite there yet. Sep 2 '13 at 13:51
  • I wish I had enough rep to see the up/down breakdown on that one... Sep 2 '13 at 18:32
  • 2
    +4/-5, @retailcoder. (And this used to work for anyone who was logged in, I think.)
    – Arjan
    Sep 2 '13 at 18:34
  • @Arjan That link is unfortunately broken, but it's okay, it just struck me to land here and see an accepted answer with -3 net votes! Sep 2 '13 at 18:39
  • Ah, I was confused with the API, @retailcoder. ;-)
    – Arjan
    Sep 2 '13 at 18:42
  • Ironically, I've recently read a MSO post about flagging as off-topic questions that would belong on CR, as SO and CR are (according to that post) "the same thing"... which I don't agree with, hence my +1 to this answer. Sep 2 '13 at 20:46

You must log in to answer this question.

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