I asked myself the same question during the renaming. I didn't want to make the data we have now fit my interpretation, so a few days after the change I came up with an hypothesis:
Hypothesis: Over the period of one month, the name change will result in a 20% reduction in the use of the “no debugging” close reason.
Current data for the last 30 days: 517/1241 closed for any reason, of that 177 as debugging. That's 14.26% of all questions. The hypothesis would predict 11.41%. (Data taken from https://softwareengineering.stackexchange.com/tools/question-close-stats?daterange=last30days)
— starting at https://chat.stackexchange.com/transcript/21?m=33068748#33068748, here with fixed typo
Specifically, I'm not interested in the ratio of different close vote reasons to each other, or the total close rate, or the number of questions closed. I am only interested in the percentage of all asked questions that were closed as code/debugging requests.
One month later, I revisited this hypothesis – and it held:
So one month back, I hypothesized that in the wake of the name change, we would see a 20% reduction in questions closed as debugging.
The numbers are in. Debugging questions have been reduced from 14.26% (177/1241) down to 9.04% (86/951). That means the prediction has held, yay :)
However, total question volume has also sunk by 23%. Are these changes caused by the name change? Or are there simply less off-topic questions due to seasonal reasons? I don't know.
But for this one arbitrarily picked metric, the name change seems to have been a success, or at least not have a negative influence.
— starting at https://chat.stackexchange.com/transcript/message/33659633#33659633, here with fixed typos
(For reference, we are currently at 64/897 = 7.13% debugging questions.)
There are still a lot of off topic questions. But so far, it seems that the name change has helped to get the number of debugging questions down dramatically – my 20% prediction was far too conservative.
The debugging questions are no longer the uncontested #1 problem of this site. Debugging questions are now on par with too broad, unclear, or tool-recommendation questions. Of course every closed question is bad, but they are now on more healthy, more manageable levels. And for that I am thankful.