I often encounter answers on SO are only one line, and later they are not improved.
One of the rules suggests that a user should comment on the question instead of providing a one-line answer (especially in close questions).
Is it fine to have one-line answers?
I'll answer this by explaining how I handle these when they reach the moderator queue. We see a few distinct types.
First, you have Bob Blogger and Glen Github:
Click this link, it will solve yer problumz.
... May contain a solution, but unless it answers the question completely within the answer itself it's not very useful. Link only answers are also removed, as we know. Barring exceptional cases, I delete these.
Then you get Mr. Negative:
No, that's simply not possible
... Does answer some questions. You could expand that to explain why something can't be done as explained, or perhaps suggest an alternative, but I tend to leave these answers as they are technically answering the question (correctly or otherwise). Votes can take care of the rest. The reverse of that, Mr. Sunshine that simply asserts something as possible - I just delete.
Don't forget Function Q. Junction:
You should use [link]function()[/link]
... Helpful, but at best a comment. There's nothing in the answer that explains how this would help, how to use the function or what to look out for. All you're doing is linking to documentation. Most of the time I convert these to comments, or expand them if the answer happens to be the one that is accepted.
And Terse Tony:
Put the -lm last in the command line, so the linker knows what symbols are needed when scanning the lib.
... Tony may even offer several additional words of explanation. Still, a perfectly valid answer, just a lot of room for improvement .. and syllables.
Finally, the try guy:
Try setting (something) to (something else) and frob the domino boilers
... These can sometimes be highly voted or even accepted, but in essence it started off as little more than a comment. If it appears the guess was correct I'll usually edit it to be more assertive and less of a guess. Otherwise, if it seems like a reasonable suggestion, I'll convert it to a comment so others can see what the OP might have tried.
Everything else such as 'me too', 'thanks', 'asdfgh', 'hi mom!' etc are cut and dry enough to not need explanation. If you think a one line answer is useful enough to keep around, but doesn't constitute an answer just flag it as other and indicate why it should be a comment.
Also note that flagged answers that the community deletes still show up in our queue, so we're usually the final step in the review process anyway.
-lm last in the command line, so the linker knows what symbols are needed when scanning the lib.", even giving a bit of explanation. Perfectly valid - but much improvable - answer.
Commented
Nov 28, 2012 at 11:47
No, not always.
This answer is a shining example of why one liners are usually bad. Any question that can be answered in one line fully doesn't deserve to be open in the first place.
One liner answers aren't bad simply because they are one-liner answers. However, an answer that doesn't consist of much information is a red flag, and many times this is a symptom of an actual problem with the answer.
For instance, answers that are shorter tend to have a higher chance of failing to answer the question completely or failing to explain why the answer works. On a site dedicated to making the Internet a better place and being useful to future visitors, having a thorough explanation is critical.
The Low Quality Review queue consists of questions and answers that are short. The system automatically flags these as being potentially low quality. Stack Overflow users review them individually and either upvote them, edit them, downvote them, comment on them, or recommend deletion depending on whether or not the material is useful.
So, if the one liner answer is useful or helps someone solve a problem, then it's probably worth leaving. Of course, it's never harmful to suggest that someone add an explanation to their answer, for clarity. :)
In short, judge the answer based on it's own merits. Length alone shouldn't be used to judge an answer.
It depends how good they are, but they'll probably end up in the poor quality answers queue for human checking anyway.
