I haven't been reviewing long, but it seems like almost daily I see questions closed due to programming or data requests. But to me the majority of these are more often statistical questions rather than programming questions (which statistics often is going to involve I'm afraid). A good example is this question:
To me this is not about programming. The OP is clearly asking about whether or not the structure of their clusters in the mixed model is correctly defined and how to program this. This to me doesn't scream "I need somebody to debug code" but rather "I need to understand how hierarchical structures work in these models." Oftentimes there are questions I pose here about GAMs that almost inevitably require some programming feedback on because that is the nature of the beast.
This is only one example, but can someone here clearly define what is considered programming-only and what is considered CV-worthy? I am more often leaned towards keeping these kinds of questions open, but not sure if that is correct.
Another example recently that gets to the heart of my issue.
One more that doesn't seem to fit this specific close vote:
And another that I would consider borderline given it's not clear if it's a programming question or stats question (as it's currently phrased, this could be a contender for a close given they really only highlight the error code).