Quantcast
Channel: Reviewing some awful questions is just a waste of time, can we have a "no comment" close reason for these? - Meta Stack Overflow
Viewing all articles
Browse latest Browse all 5

Reviewing some awful questions is just a waste of time, can we have a "no comment" close reason for these?

$
0
0

When handling close votes, I find myself spending more time mapping the question to a proper close reason than the OP spent energy writing the question. I'd like for there to be an option "no comment" for these kind of questions.

Case in point:

How Do i find how many section headers in PE file - C

What is an Section Header in PE file ? And how with c code can i count them ? I already tried to search in the web but didnt fount somthing that halped me .

    asked Apr 21 at 11:21

See also the very illustrative comments:

"Too broad" isn't an appropriate reason, the only appropriate reason is that the OP doesn't know how to use a search engine. Why can't we be explicit or totally generic and avoid reviewers wasting time on this?

The point of this question is to be able to make a clear distinction between questions that cannot be salvaged because the asker is clearly not capable or willing to do so.

It's about weighing the risk of wasting the reviewers' time against the risk of applying this reason to the wrong group of newbies. This question got closed as 'Too broad', and that prompts me to edit it. Sometimes prompting an OP to come back and edit is a waste of everyone's time.

Stack Overflow is quite good at protecting the system from spam, it's also great at improving itself, but it's not so good at protecting it from carelessness.


Viewing all articles
Browse latest Browse all 5

Trending Articles





<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>