10
\$\begingroup\$

As mentioned in my question about the definition of "debug my code" questions, I'd like to propose that we merge two existing close reasons and make room for a new close reason dedicated to addressing "debug my code" questions.

I'm going to post, as an answer to this question, what I think we should do now based on the general consensus from previous question on the definition. Feel free to upvote that answer or propose your own solution (including a post saying we shouldn't do this, if that's how you feel).

\$\endgroup\$
1
  • 3
    \$\begingroup\$ This is now live! \$\endgroup\$ Commented Feb 22, 2014 at 22:16

1 Answer 1

Reset to default
14
\$\begingroup\$

I propose the merging of our current close reasons that cover "which technology" questions and "what to learn next" questions. For reference, these reasons are currently:

Questions that are about "which tech to use" are outside the scope of the site. For more information, see this meta post

and

Questions about "how to get started" or "what should I learn next" cannot reasonably be answered with anything other than opinion polling and therefore are off topic for the site. For more information on how to ask a better question, see the help center

I suggest we combine them as follows:

Questions about "how to get started," "what to learn next" or "which technology to use" are discussion-oriented questions which involve answers that are either based on opinion, or which are all equally valid. Visit our help center for more information.

and then add the following new close reason:

Questions about debugging a problem in your project must present a concise selection of code and context so as to allow a reader to diagnose the issue without needing to read all of your code or to engage in extensive back-and-forth dialog. For more information, see this meta thread

\$\endgroup\$
8
  • \$\begingroup\$ I don't know if that should say "to read to read" but it looks like a good idea to me otherwise. :) \$\endgroup\$ Commented Feb 20, 2014 at 3:19
  • \$\begingroup\$ Since we really are allowed only 3 custom reasons, I think this is an excellent proposal. \$\endgroup\$ Commented Feb 20, 2014 at 7:40
  • 1
    \$\begingroup\$ My only quibble: Can we trim off "on asking questions here", so it's just "Visit our help center for more information."? The help center contains more information not just on asking questions but also on why we have such rules, among many other useful things. \$\endgroup\$ Commented Feb 20, 2014 at 7:45
  • 1
    \$\begingroup\$ I was going to ask about why not bring back too localized but based on the opinions in this meta post and the way you've worded your debugging close reason I would say you've really got a good solution here. \$\endgroup\$ Commented Feb 20, 2014 at 12:18
  • \$\begingroup\$ @Anko, I like that idea. \$\endgroup\$ Commented Feb 20, 2014 at 16:09
  • \$\begingroup\$ Looks good to me as well. But if we are going to trim off "on asking questions here", I think there should be a comma after "information". \$\endgroup\$ Commented Feb 22, 2014 at 0:38
  • 1
    \$\begingroup\$ I've added the reasons and they are pending approval by another moderator. \$\endgroup\$ Commented Feb 22, 2014 at 4:47
  • 2
    \$\begingroup\$ ...and it's now live! \$\endgroup\$ Commented Feb 22, 2014 at 22:16

You must log in to answer this question.