Timeline for How do you write a Stack Exchange answer?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2018 at 10:33 | comment | added | celtschk | @MGOwen: What you should avoid is not being long, it's being long-winded. You don't need to be brief, you need to be concise. And BTW, I think your linked answer overtook the accepted one not because of its briefness, but because it actually provided the code to do it. | |
| May 17, 2018 at 2:16 | comment | added | MGOwen | @celtschk yes some answers must be long, of necessity. But it still should be as short as possible while still answering the question clearly and correctly (within reason). | |
| May 16, 2018 at 4:39 | comment | added | celtschk | Sometimes short answers are called for. Other times, long answers are called for. I strongly doubt that I would have gotten 100 points on this answer if it had been a one-liner. | |
| May 16, 2018 at 0:32 | history | edited | MGOwen | CC BY-SA 4.0 |
added 2 characters in body
|
| Feb 21, 2018 at 14:45 | comment | added | Discrete lizard | Note that a useful consequence of this is that if you insist on writing a novel, you can use headings in such a way that only reading the headings is also an answer! | |
| Feb 21, 2018 at 10:06 | comment | added | BSalita | Right. I have no patience to read lengthy questions or answers. Writers on this forum seem to have infinite time to polish the turd and assume their audience does too. Seems unique to this forum. | |
| Feb 21, 2018 at 2:15 | history | answered | MGOwen | CC BY-SA 3.0 |