I would really encourage not to DV short answers. Commenting about elaboration is good. But if it technically answers the question (what you included), then it is a good answer. There are so many "maybe" answers which should be DVed.

But if you want more details that you'd see yourself that could be added - why not make it a community answer? Or post your own answer with more details and see if it get's UVed?

I know, brilliant and detailled answers are wanted. But UV a good answer to encourage answering at all. If all answers get DVed just because they could be improved, that's cutting your own branch you're sitting on. This site is not about questions only but about answers. And if technically answered it's a help for people who search for answers.

Not to forget: DV means (as its tooltip explains) "This answer is not useful". So if the answer is technically right but only could be elaborated, you should better not vote than vote and express that it is not useful at all. You should instead probably just UV because you can clearly see that the technical answer is given. And might drop a comment encouraging to elaborate.

And feedback here should be more encouraging, right? Not discouraging with DVs (even more without a comment about why).

I would really encourage not to DV short answers. Commenting about elaboration is good. But if it technically answers the question (what you included), then it is a good answer. There are so many "maybe" answers which should be DVed.

But if you want more details that you'd see yourself that could be added - why not make it a community answer? Or post your own answer with more details and see if it get's UVed?

I know, brilliant and detailled answers are wanted. But UV a good answer to encourage answering at all. If all answers get DVed just because they could be improved, that's cutting your own branch you're sitting on. This site is not about questions only but about answers. And if technically answered it's a help for people who search for answers*.

Not to forget: DV means (as its tooltip explains) "This answer is not useful". So if the answer is technically right but only could be elaborated, you should better not vote than vote and express that it is not useful at all. You should instead probably just UV because you can clearly see that the technical answer is given. And might drop a comment encouraging to elaborate.

And feedback here should be more encouraging, right? Not discouraging with DVs (even more without a comment about why).

* consider that as a programmer I myself often stumble over questions that I have as well and just searched for it in Google and with a bit of a more specific topic I get more hits nowadays on SO than on Forums which is a great thing. And People often look for answers and if they find a technically correct one it will really help them out. When there are open points/details left out, the comment section is the place where one can ask for them. This might remind the author to elaborate. And it might new users to register to ask for more details - and if they get them (probably in another more detailled answer that you just posted later) they might consider sharing their knowledge as well.
I think, it's about answers first and foremost. Elaboration is a process in time. So don't hinder this process from evolving with a DV. ;-)

I would really encourage not to DV short answers. Commenting about elaboration is good. But if it technically answers the question (what you included), then it is a good answer. There are so many "maybe" answers which should be DVed.

But if you want more details that you'd see yourself that could be added - why not make it a community answer? Or post your own answer with more details and see if it get's UVed?

I know, brilliant and detailled answers are wanted. But UV a good answer to encourage answering at all. If all answers get DVed just because they could be improved, that's cutting your own branch you're sitting on. This site is not about questions only but about answers. And if technically answered it's a help for people who search for answers.

And feedback here should be more encouraging, right? Not discouraging with DVs (even more without a comment about why).

I would really encourage not to DV short answers. Commenting about elaboration is good. But if it technically answers the question (what you included), then it is a good answer. There are so many "maybe" answers which should be DVed.

But if you want more details that you'd see yourself that could be added - why not make it a community answer? Or post your own answer with more details and see if it get's UVed?

I know, brilliant and detailled answers are wanted. But UV a good answer to encourage answering at all. If all answers get DVed just because they could be improved, that's cutting your own branch you're sitting on. This site is not about questions only but about answers. And if technically answered it's a help for people who search for answers.

Not to forget: DV means (as its tooltip explains) "This answer is not useful". So if the answer is technically right but only could be elaborated, you should better not vote than vote and express that it is not useful at all. You should instead probably just UV because you can clearly see that the technical answer is given. And might drop a comment encouraging to elaborate.

And feedback here should be more encouraging, right? Not discouraging with DVs (even more without a comment about why).