imnotreadingal.lat
please don't post a wall of text
Long context can be useful. A giant unstructured message usually is not. People should be able to scan your message, understand the ask, and decide how to help without doing a reading assignment first.
so basically the app broke and I tried a bunch of stuff yesterday and there was this auth page thing maybe it was the API but the docs said something else and I changed the config because the deploy was weird and then I thought maybe cache and...
What is the actual issue?
This makes the reader find the problem, the request, and the useful details for you.
Login returns 401 after token refresh. Expected: new session.
Tried clearing cache and reinstalling packages. Route, error, and repro steps are below.
Perfect. Send the log.
Now the reader knows what broke, what should happen, and where to look next.
A wall of text asks everyone else to spend effort before they even know whether they can help. It buries the important part under backstory, side thoughts, and guesses.
If you want a useful answer, make the message useful first. State the problem, include the evidence, and keep the rest available below the summary.
Problem: What is broken?
Expected: What should happen?
Tried: What did you already check?
Details: Logs, screenshots, links, or examples.
Put the summary first. Put the long stuff after it. People are much more likely to read the details when they know why the details matter.