---
title: "TLDRs go first or they lose their value"
description: "TLDRs go first or lose their value. However, most content includes it at the end. Why is that?"
canonical_url: "https://www.ungu.info/thoughts/tldrs-go-first"
---

> Index of every page on this site: [llms.txt](https://www.ungu.info/llms.txt)

# <span className="text-h1">TLDRs go first or they lose their value</span>

<br />

<br />

<br />

<v-alert type="info">

TLDR: TLDRs should be provided at the beginning of long content. Otherwise, what's the point?

</v-alert>

<br />

<br />

Have you found yourself reading a long blog post or documentation entry just find a "TLDR" section at the end?

<br />

I know I did.

<br />

[TLDR](https://www.oxfordlearnersdictionaries.com/definition/english/tl-dr) stands for "Too Long, Didn't Read" and
serves as a way to provide a brief summary of what the bigger content is about.

<br />

The point of having such a thing in your content is to say something along the lines of:

<br />

> <span className="blockquote">
> 
> "hey, this post is long, if you're not interested in reading the whole thing, this is a summary".
> 
> </span>

<br />

However, if you're placing this at the end, you're almost forcing me to read your content before getting what I came
here for: the answer to whatever question I had for which you might provide the answer.

<br />

<br />

Even if I search for the term "tldr" or quickly scroll past your long content, I still have to remember that your
article might have this summary section and actually look for it.

## Sitemap

See the full [sitemap](https://www.ungu.info/sitemap.md) for all pages.