2
\$\begingroup\$

When we first discussed the "debug my code" close reason we settled on the following wording that is in-use today:

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

Many of the questions we got back then that this reason would pertain to were large, context-free code dumps. Recently I've noticed we're getting a lot of "debug my code" questions that either aren't strictly code-related or do include very concise (but not at all relevant) code samples.

Consequently I think we should update the close reason.

\$\endgroup\$
4
\$\begingroup\$

I think we should change the reason to include wording requiring a minimal example that would reproduce the problem. I've created the What's a "minimum complete verifiable example" (MCVE) and how do I provide it? meta post, cribbed from the StackOverflow help pages (an idea I stole from Vi and Vim), which we can use to request users provide such an example. I propose we update the close reason text as follows:

Questions about debugging a problem must provide a minimal, complete, verifiable example of the issue so that readers can diagnose it without needing to guess, read all of your code, or engage in extensive back-and-forth dialog. For more information, see this meta thread.

\$\endgroup\$
  • \$\begingroup\$ This is now live. \$\endgroup\$ – Josh Jul 11 '16 at 19:05

You must log in to answer this question.

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