Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Poorly asked questions should be closed. Why they are poorly asked (with confusing being only one instance of that) should have no bearing on closure. Whether a question has answers or not should...
Answer
#1: Initial revision
Poorly asked questions should be closed. <i>Why</i> they are poorly asked (with confusing being only one instance of that) should have no bearing on closure. Whether a question has answers or not should also have no bearing on closure. Closure is about the <i>question</i>. Just because someone may have guessed correctly what a badly worded question is asking, doesn't make the question good. Beside, how do we really know the guess is correct? Even if the question author ultimately says it answer the question, the whole Q&A does not leave a useful record. Someone else may come along later and interpret the question differently, then be misled by the answer. Closing bad questions also makes a statement of what kinds of questions we want here, and what the minimum tolerated quality level is.