Skip to main content
Meta Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 14
    It's clearer, thanks. It still isn't entirely helpful; because how much information is considered enough to understand the answer? Is that skill level dependent? I may understand an answer that says, "Use a group by" and you may not. Does that mean the answer is 'not an answer'? What's a "reasonable level of detail" For an answer? For a question, it's when we can use the code to reproduce the problem. What is it for an answer? I'm not trying to come down hard on you, just trying to pre-empt the many questions and finanglings we'd get if this were policy. Commented Mar 20, 2014 at 12:24
  • @GeorgeStocker: I understand your point. As MSO newbie I am having trouble sometimes formulating it in a way it can be converted to policy. I will update the answer to make myself clear. Commented Mar 20, 2014 at 12:27
  • 81
    It's an answer, but it isn't a very good one. It's not "thanks that worked" or "I have this problem" or "buy Gucci purses here" - it's an answer. You can downvote it or leave a comment suggesting that the poster expand it a little (This would be a better answer if you explained how the FileOutputStream could be applied) or even edit it yourself if you have 2K and know how the FileOutputStream could be applied. None of which you can do to things that aren't answers. Commented Mar 20, 2014 at 12:53
  • 3
    @KateGregory: but is a link without any explanation an answer? In my opinion not. Commented Mar 20, 2014 at 13:08
  • 50
    Forget links, @patrick. They're a red herring in all these discussions. A post that does not contain any information is not an answer. Commented Mar 20, 2014 at 13:22
  • 69
    Without any information - "try this", "click here", "tutorial" - it's not an answer. With a class name or function name etc it's a poor answer, but an answer. Ignoring what the link is to and just reading the text. Explanations turn bad answers into better answers. Commented Mar 20, 2014 at 13:23
  • 2
    @KateGregory: but should they be comments then? Commented Mar 20, 2014 at 13:27
  • 7
    There are times I'm too busy for an answer and will comment "look into LongComplexAPIName I think it might work for you" but I would be wary of saying a particular style of answer must be flagged, converted to a comment deleted etc. We have downvoting for a reason. Commented Mar 20, 2014 at 13:30
  • 51
    @PatrickHofman No, it shouldn't be converted to a comment because it's an answer to the question. It's a low quality answer, but still an answer. I can have this problem, read that answer, not click the link, and still learn enough to understand how to solve my problem. That makes it an answer. Now you feel that it is lacking in detail, and doesn't go into enough depth. That's fine. It's entirely okay to feel that way. Downvote it if you think that, that's fine. But don't say that it's not an an answer just because it's a low quality answer. It's still an answer. Commented Mar 26, 2014 at 14:29