Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
And I hope it never does. On the flipside I'd like to see SE keep the frame of Q and A rather than border the realm of a discussion forum or short story board where excessive irrelevant information exists un governed and masks answers. Users should not have to extract answers from 200 - 300 word "essays" when it is plain that a more articulate answer exists. in slhck's example, yes, explain this caveat but do not randomly include the history of bash and the historical context of why such a problem exists.
superuser.com/questions/486684/… Here is an example I guess of a question I answered in 1 - 2 sentences. Look at the answer below mine, you'll see how it is very akin to flogging a dead horse. I understand it isn't always this simple but ALOT of the times it is and people just aren't aware of the overkill. I know it wasn't a complicated question but my point is that there were complicated answers when 1 - 2 sentences sufficed.
Agreed, some questions and querants lack substance and direction which is fine. Nothing you can do about that. But for the questions and answers that are spot on, a verbose answer that benefits those with a curious mind with the luxury of time, and a shorthand version for those just wanting to Git 'r done would only add to the super user experience and reach a broader spectrum of answer seekers.
My concern is with the "here do this" answer being flogged like a dead horse, 300-500 sentences long when all that needed to be said was "here do this." Your second and third bullet points are simply potential answers that can eventually be drilled down to a "here do this" answer once all the information is present. Again, the conciseness is really to benefit the person who needs a quick "here do this" answer. There are times when nobody gives a shit how something works as long as it does. The opposite is also true which is why providing a "long" and "concise" answer are both attractive.
Verbose answers are great for those who spend the majority of their life on Superuser and little time anywhere else. But for the person finding the answer in a Google search who is deep in the trenches of an I.T. project with deadlines etc, the answers need to be concise or the searcher will go elsewhere. Long answers are OKAY but why not include a consolidated version in say, 10 sentences or less that just gets to the core of the solution and cuts out the bullshit?
