Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

60%
+1 −0
Q&A How do you write a Stack Exchange answer?

I try to always answer in 3 paragraphs whenever possible. Less is often too little for a substantive answer, and more becomes less and less likely for people to read. The first paragraph should a...

posted 7y ago by Chris Sunami‭  ·  last activity 5y ago by System‭

Answer
#3: Attribution notice added by user avatar System‭ · 2019-12-08T08:05:51Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/33620
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by user avatar Chris Sunami‭ · 2019-12-08T08:05:51Z (almost 5 years ago)
 **I try to always answer in 3 paragraphs whenever possible.** Less is often too little for a substantive answer, and more becomes less and less likely for people to read. The first paragraph should always be the most direct answer to the main question in the original post, as asked, with a minimum of editorializing. It should generally cite a [reputable source](https://en.wikipedia.org/wiki/Wikipedia:Identifying_reliable_sources), with a link, but also recapitulate the information that is linked. Sometimes I will boldface a key idea, no more than one per paragraph at the most. The most important thing is to remember that this is audience-oriented, persuasive/informative writing, it must be simultaneously substantive, useful and compelling.

My second paragraph is a place to expand on my answer, or to answer the question that I really think should have been asked, instead of the one that actually was asked. Even when doing so, however, I think it's important to treat every question as legitimate, as reasonable and as asked in good faith (otherwise you shouldn't be answering it). **It's also important to NOT make the querent feel stupid or ignorant for not having your level of knowledge.** Quite often it's not the content that makes for a highly upvoted answer, it's the structure and the _tone_.

Does it even make sense to ask for "the" way to write SE answers, since they are all so different? I do think there are some generally useful structures that aren't content-area specific. For example, if I want to criticize the question itself or offer original or controversial ideas, I reserve those for the last paragraph. I've found that the very same things that enrage people, or cause them to dismiss an answer when contained in the first paragraph, are often accepted without comment in the last paragraph, especially if they are clearly labeled as "original" or "editorial." **It's worth noting that the exact same conceptual content can garner very different reactions, depending on how it is presented, and in what order.** Finally, I nearly always revise frequently, and to do my best to accept all critiques in the comments non-defensively, and to respond to them productively (generally through revisions).

#1: Imported from external source by user avatar System‭ · 2018-02-20T16:14:49Z (almost 7 years ago)
Original score: 37