...not literally, of course. But what happened to the previous menu of close-vote options?
I find the current set unsatisfactory. Take this question that boils down to a typical
java.lang.NullPointerException for example. Obviously, the question is worthless, because it's an exception that even a n00b programmer should be able to debug on his own. There is nothing special about this bug, and it will help no one in the future.
What could I possibly select as a close reason?
duplicate of... - Maybe. There's the classic What is a NullReferenceException and how do I fix it? which has been linked to 527 times. While the debugging techniques are the same, that's for .NET. Besides, there are any number of other common exceptions / simple development bugs that wouldn't apply.
This question was caused by a problem that can't be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting.
unclear what you're asking - No, it's clear that the programmer just needs to debug his code.
too broad - No, it's quite specific.
primarily opinion-based - Nope.
When it was introduced, I was happy to see a "typo" reason, to rid out all the stupid indentation or bracket questions. But... we no longer have a "lacks minimal understanding" reason, which I think is incredibly important. After all, Stack Overflow is here to solve problems that "professional and enthusiast programmers" encounter... not teach users how to code or debug.
So.... what do I pick? Can we have another revision on the close vote reasons?
I did a cursory search, but couldn't find a Meta post to the intent behind this latest set of reasons. Edit: I believe this is it: Improving "demonstrate a minimal understanding" close reason
Edit 1/20 Ah, how could I forget about the classic copy & paste homework assignment?
Right or wrong, my close vote was cast with
off-topic because it shows zero desire to actually understand the problem.
Here we see a moderator closing a question about an incorrect number of function parameters as lacks sufficient information to diagnose the problem. Of course, there probably is sufficient information, and the wording should really be changed to You're too lazy to RTFM.