Where should I put my tl;dr?
By definition
TL;DR, short for "too long; didn't read", is Internet slang to say that some text being replied to has been ignored because of its length. In slang it can also stand for "Too lazy; didn't read". It is also used as a signifier for a summary of an online post or news article.
Wikipedia
Usually the author of a long post gives a tl;dr, a summary of the what the post about in a short paragraph or sentence. This can be put before the post begins, or the after.
tl;dr We are asking you to start saving water and electricity for the sake of our environment.
Blahblahblah...
I've seen two types of people, who scrolls down to see the tl;dr, and those who looks for the summary on the top of the post. This makes me unsure where to put my post summary. If I were to write a post, a letter, etc. how can I decide which position is the most beneficial to me, i.e avoid people skipping my question entirely and getting the message across.
tl;dr How can I decide that putting my tl;dr at the top of the post, or bottom, will benefits me the most? What factors should I consider?
I'm thinking more about the types of the post: informational post might be better with bottom summary, while question better with top summary. What other factors affecting this?
Note: Some put a notification at top of the post, informing a tl;dr is available at the bottom of the post.
This post was sourced from https://writers.stackexchange.com/q/32819. It is licensed under CC BY-SA 3.0.
3 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
Where to put the a tl;dr or summary is going to vary depending on the piece.
For example, an email from I.T. warning about a change will include the most important information and what users need to do upfront, and then may include further details beneath that for those who are curious.
Having the tl;dr at the beginning means people are more likely to see it.
In other pieces of writing it makes more sense to have it at the end. For example, someone sharing a story might include the tl;dr at the end to avoid spoiling anything for someone reading the whole thing.
tl;dr If the tl;dr is important information, put it at the top. If it's for convenience, put it at the bottom.
0 comment threads
I'd be inclined to put a summary at the beginning, similar to an abstract in an academic paper. That way people would see it first, those who were interested could read further, and those who were not would still see the summary. Putting it at the end might lead those who weren't particularly interested to feel they had wasted time getting there, and those who were to think "what do you mean? That was just fine."
You've already identified "tl;dr" as slang, so all the usual questions about where slang works and where it doesn't will apply. This particular one isn't one of my favourites - if the writer really thinks the post is too long, why didn't they do something about it?
The other thing about slang is it can date quite quickly. It might look groovy now, but in a year or so the posts might look like they were written by a square.
This post was sourced from https://writers.stackexchange.com/a/32828. It is licensed under CC BY-SA 3.0.
0 comment threads
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.
This post was sourced from https://writers.stackexchange.com/a/32821. It is licensed under CC BY-SA 3.0.
0 comment threads
0 comment threads