I started a post earlier with the topic: Listvars does the trick for me is not regarded as an answer The issue is boiling down to a new issue that I felt worthwhile opening a new post for. What is the responsibility of the questioner and answerer. This site wishes to provide good quality answers. But I feel that people are mixing up good quality for good quantity. In the link provided above, some people feel that the reason as to why my answer is not a good one is because it is of low-content. They feel I should have provided extra detail, such as a link to the documentation or describing the command listvars more and how I applied it in my script. That whole debate is revolving around another issue, which is what is being discussed here: What is the responsibility of a questioner and what is the responsibility of an answerer? As such, this post is not a continuation of the above liked post. I provided that as a relevant example of the issue at hand.
The questioner, he is asking for a favor. Asking a favor is not blameworthy, as long as it doesn't exceed the bounds. As such, his expectations should be likewise. His responsibility is to the best of his ability to provide a question that does not cause discomfort to others. Discomfort can be caused by
- asking something that can be easily retrieved in the documentation.
- making the question ambiguous.
- not giving feedback about answers that were given.
Pertaining the answerer, his responsibility is merely to provide a pathway to the successful outcome and resolvence of the question. He is responsible for insight and informing the questioner of something he can't do independently. The moment he did that, he is absolved of his responsibility. Anything over and above that is his goodwill and an extra favor. If he leaves it out, then nothing can be held against him.
For instance in this discussion about listvars, the answerer provided the questioner with correct information. He directed him and now the onus of documentation rests with the questioner. Why? Because it is something he can do himself. Asking for help is always restricted to the point that you can't manage. To ask over and above that is blameworthy. Listvars is clearly not a difficult command that it requires additional explanation to enable the questioner to correctly implement it. The documentation is more than clear enough on the issue. Likewise, a link to the documentation would be a bonus point. But it is not necessary and not a cause to down vote someones post for.
As such, good and bad answers is not about providing a lot of documentation. It is about whether or not you fulfilled your responsibility as an answerer stated above.
So far the reasons that have been provided are not answering this question. People say that "Listvars does the trick" is not a constructive and helpful way for future users. Or "if you feel that Listvars does the trick is sufficient, then I don't have much to say in response" all of these are not addressing the question. The question is about: What criteria do you use to say whether or not an answer is good or bad? I stated a detailed reason as to why quantity of documentation is not a preferred criteria. I am advocating for judging according to the responsibility of each side, has it been fulfilled or not? But nobody has contradicted my philosophy over here in favor of the superiority of lots of documentation over my criteria presented here. Listvars does the trick was merely an example, don't mix up this issue with that.
But an overwhelming amount of people seem to be unable to separate this question from the previousif you're referring to the downvotes on this question, I don't think that's the reason for them. After all, your last question was (on net) upvoted.