13
\$\begingroup\$

Inspired by this off-topic question as an example, this is a follow-up question to this answer.

If it's true that that we won't (can but won't) ask for another close reason, should we modify this answer ...

Questions asking for code to be written to solve a specific problem are off-topic here as there is no code to review.

... to make it recommend that the OP ask their question on Programmers.SE including:

  • A hyperlink to Software Engineering
  • A brief explanation (if some questions are off-topic at Software Engineering) of what is an on-topic question at Software Engineering

Also rolfl posted a succinct explanation of the difference between Programmers, SO, and CR, which deserves to be more widely published (perhaps in the on-topic Help of all three sites):

  • Software Engineering - I have no source code: I don't know how to do it right, how do I do it?
  • Stack Overflow - I have broken source code: I tried to do it right, but it's broken, how do I fix it?
  • Code Review - I have finished source code: now that I've done it, can it be made better?
\$\endgroup\$
  • 1
    \$\begingroup\$ See also Changing wording of the code-to-be-written and working-code off-topic reasons \$\endgroup\$ – ChrisW Mar 24 '14 at 13:41
  • \$\begingroup\$ I love the idea, but I think the Programmers part needs some more clarity. As it is currently worded, it sounds like the short question "How can I make a Java game?" (almost "give me the codez") is on-topic there, but I believe it wouldn't be on-topic for Programmers unless you describe how you have planned it etc... kinda like a "Design review without any code written" (Please correct me if I'm wrong) \$\endgroup\$ – Simon Forsberg Mar 25 '14 at 11:46
  • 1
    \$\begingroup\$ @SimonAndréForsberg Yes I think one could summarize what's on- and off-topic at Programmers. Perhaps that means looking at Programmer's Meta, and/or inviting their participation in the answer, and/or posting a question "Please summarize what is on- and off-topic?" on their meta. It's because a multi-sentence explanation might be necessary, too long for a close reason, that I thought of putting a link to a meta-topic in the close reason (instead of stuffing the whole explanation into the close reason itself). \$\endgroup\$ – ChrisW Mar 25 '14 at 11:58
  • \$\begingroup\$ The new close reasons include links to Stack Overflow and Programmers. \$\endgroup\$ – 200_success Apr 2 '14 at 6:21
4
\$\begingroup\$

I suggest:

  1. Create a meta-question titled "Code Review, Stack Overflow, or Software Engineering"
  2. Make the second part of the OP above an answer to that question; optionally expand/improve it
  3. Add a hyperlink to that topic to the custom close reason(s):

    Questions asking for code to be written to solve a specific problem are off-topic here as there is no code to review: please see Code Review, Stack Overflow, or Software Engineering?, which explains where to post different types of question.

\$\endgroup\$
  • \$\begingroup\$ Having the meta question as a FAQ is (a great idea) worth doing and whether it makes it to be a close reason yet is step 2. I recommend you set up that question anyway. \$\endgroup\$ – rolfl Mar 25 '14 at 10:37
1
\$\begingroup\$

Out of interest, the very first question on Meta.CodeReview, is What should our FAQ contain?.... and, guess what:

What belongs here vs what belongs on StackOverflow.

\$\endgroup\$

You must log in to answer this question.

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