Add a new close reason for implementation and troubleshooting questions

Question

Code troubleshooting and code implementation questions are not in Programmers' site scope. Although there is an option to migrate such questions to Stack Overflow, the vast majority of them are not of sufficient quality to migrate there. Thus ensues a long-winded explanation of how we don't accept troubleshooting or implementation questions, but your question is not of sufficient quality to be migrated to Stack Overflow, yada yada.

The close reason ought to be simple enough:

Question about writing specific code (i.e. troubleshooting and implementation) are off-topic on Programmers. You might be able to get help on Stack Overflow, but read their Help Center first.

Answer 1

At first glance, this actually does not appear to be a problem (keep reading!!); I used this SEDE query to see what custom close reasons we are using for this; only 24 of these 171 questions have a comment that includes the characters implementation, debug, or verflow.

However, this is not a complete picture of the story. Sometimes other things happen to these questions:

1. These questions get deleted. This happens often, and therefore cannot be analyzed using SEDE.
2. These questions are migrated to Stack Overflow, even when they are of low quality. This also happens often. Robert Harvey can probably speak to this better than I can.
   • A famous Jeff Atwood quote comes to mind: Don't migrate crap!! Without this custom close reason, we will migrate crap far more often than we ought to.
3. People use less accurate close reasons.
   • Of course, this is fine from the principle of crap getting closed, but...
   • It's not fine from the principle of "educating users exactly why things are happening".

We need this custom close reason. These questions are already getting closed and deleted by the community anyway; having an extra close reason isn't going to change that. What it will do is organize these questions more appropriately, and educate future users on how and where to ask questions.