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.
Comments on Give actionable feedback when closing questions
Parent
Give actionable feedback when closing questions
Having had the dubious honor of experiencing the closing process from the perspective of a question author, it seems to me that closing does not adequately communicate why the question was closed, and which aspects need improving in order to make the question work here.
Specifically, for feedback to be actionable, it needs to
- specifically identify the problem
- explain why it is a problem
- and ideally explain a way to move forward
So, how did our process measure up? The close reason given was:
This post contains multiple questions or has many possible indistinguishable correct answers or requires extraordinary long answers.
That lists 3 different reasons for closure, leaving it unclear which one applies to the question.
Also, the second possible reason is not conveyed clearly, because "many possible indistinguishable answers" does not make grammatical sense: if the answers are indistinguishable, they are duplicates - why is that a fault of the question?
And it doesn't explain why that is a problem.
And it most definitely doesn't show a way forward.
Of course, people are smart. They can ask for further information if they care, and then wait a day for that further information to arrive.
I did, and received:
I closed this post because it's asking for personal anecdotes; there's an infinite number of possible answers to such a question, and as such doesn't fit so well into a Q&A format. It might be better suited to chat, or possibly a series of blog posts (which you might want to discuss in the Meta category). See also How to ask a great question in the Help Center.
That's much better:
- It clearly identifies the problem.
- It attempts to explain why it is a problem (but doesn't quite succeed, because it doesn't explain why "many answers" make a question "a bad fit for Q&A")
- It attempts to show a way forward (but doesn't quite succeed: why chat? how do I blog? Does he mean the currently disabled article feature?)
but it also shows how challenging it can be to communicate and explain site policy in a comment box. And how time consuming. And that's probably why Mythical gave that link to the help center. Alas, as the "how to ask" page does not appear to mention "many answers" at all, the link didn't help me much ...
So ... can we find a better way to give feedback when closing a question?
Post
We rather need to make a close reason for every kind of off-topic reason.
In this specific case, the reason could for example be Purely subjective question rather than the old "primarily opinion-based". Because we hope to allow some form of best practice & design questions here and not be as strict as SO.
We need to define the reason in detail. One example could be (I just made this up here and now):
This question was closed as purely subjective, because it is asking for subjective opinions, discussions or anecdotes.
- When asking for best practices, please make sure to specify what qualifies as "best". Fastest execution, most readable, most portable and so on.
- Questions asking to discuss a topic with no clear goal or outcome, or asking for anecdotes or personal past experiences are not suitable for the Q&A format used by this site. Instead focus on a specific problem you are facing, what behavior you expect and what behavior you encountered.
1 comment thread