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 Where should I put my tl;dr?

I've usually seen it posted at the bottom, end of post, usually quoted or bolded to stand out. It could be placed in the top of the post, but I think the purpose (whether stated or not) is there t...

posted 6y ago by BugFolk‭  ·  last activity 4y ago by System‭

Answer
#3: Attribution notice added by user avatar System‭ · 2019-12-08T07:46:49Z (over 4 years ago)
Source: https://writers.stackexchange.com/a/32821
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by user avatar BugFolk‭ · 2019-12-08T07:46:49Z (over 4 years ago)
I've usually seen it posted at the bottom, end of post, usually quoted or bolded to stand out.

It could be placed in the top of the post, but I think the purpose (whether stated or not) is there to summarize what the author posted. At the front doesn't have the same impact. It seems more like an intro/ summary. They are hoping you read their post, or skimmed over enough of it to have an idea what is being posted. The tl;dr is a summary of the long post. It is a hook to help the reader remember the key points of the post. The "tl;dr" is more less a "cute" way of addressing and phrasing the summary.

**tl;dr** Post it at the end as a summary of your post. Those who read it see the highlighted points. Those who haven't read the full post get a general idea and can choose to go back and reread or not.

Also is this a question about you writing a "tl;dr" type post or a blog, or is it a question based on what you are reading?

* * *

Another possibility for the "tl;dr" is the author is having trouble finding their own point in the post. I know I am guilty of it. Watch out, reread a few times and make sure you're getting to the point and not writing around the point. It may take a few passes to realize that and go back and trim the post. (that's why I heavily edit most of my posts.) The first pass is usually an incoherent jumbled mess. The second pass is a little more cleaned up. More words spell checked and some clean-up attempted. I may expand some points or cut points. Further passes I'll focus on how each sentence reads and try to fix fragments. I'll try to further expand or cut irrelevant clutter. Depending on how much time and how many edits are allowed (if any at all) a post may get stuck as less than polished.

That said Putting tl;dr, could be used as an excuse to avoid doing further editing. If you're tempted to put one in, you may want to go over and reread your post and see what you can trim, shorten, or condense before resorting to putting a "tl;dr" type disclaimer in.

#1: Imported from external source by user avatar System‭ · 2018-01-27T00:09:46Z (over 6 years ago)
Original score: 3