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?

Get to the point first. On most SE websites, the main flow of traffic is people coming from Google/DDG for quick answers. If there is code which solves the problem, make sure it's correctly formatt...

posted 7y ago by Luc‭  ·  last activity 5y ago by System‭

Answer
#3: Attribution notice added by user avatar System‭ · 2019-12-08T08:06:25Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/33701
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by user avatar Luc‭ · 2019-12-08T08:06:25Z (almost 5 years ago)
Get to the point first. On most SE websites, the main flow of traffic is people coming from Google/DDG for quick answers. If there is code which solves the problem, make sure it's correctly formatted (e.g. using `code formatting` for code) because many people skip straight to it.

Details are appreciated, but only after making your point and giving (or proposing) the solution. It's an explanation for your point, not a story leading up to your point.

While writing 200 answers on various SE sites, I've also noticed that writing summarizing answers can be very helpful: when there are some answers which each mention part of the answer, or which are all inferior in some situations, it is appreciated to write up a single good answer. Usually those questions are old and upvotes will only trickle in over time, but it does seem to be appreciated by future visitors.

The writing here is often very impersonal: no "hi user249" or "thank you" needed; it's encyclopedic rather than a chat. Upvotes are how you say "thank you", because an upvote also implies a recommendation for others to read the answer (or question). But it's also not formal to the point of a scientific paper: you can say "I think" and "I did" rather than "one might assume" or "we performed".

#1: Imported from external source by user avatar System‭ · 2018-02-22T18:25:28Z (almost 7 years ago)
Original score: 7