Reading order is one of those subjects where the general answer and the answer for a specific case diverge, and the thread will go in circles until someone says which one is being asked for.
Reading order for a first week here, and what to skip until later posts 91–118
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
The tag pages are usually a better entry point than the categories for a first read. A tag cuts across categories, so following one shows you how the same subject is treated by the analytical people and the practical people at once.
For anyone finding this later: the short answer on reading order is that it depends on one thing, and the rest of the thread is people identifying which thing.
I keep a log for reading order specifically because my memory of it turned out to be systematically wrong in one direction. Six weeks of notes cost nothing and settled it.
Introducing yourself is fine and requires no question. Post in this subcategory, describe the context that matters for why you are here, and lurk for a bit before posting technical questions. That order works well.
Marked solutions are the site's way of saying that someone asked a good question and someone else gave an answer that actually worked. It is not a competition and it does not appear on your record — it is just how the site learns which topics stay useful six months later.
Where the reading order reasoning breaks down for me is the step from the group result to the individual case. That step is almost never argued for.
The moderation log is public. Every staff action is logged with the rule cited and the reasoning stated. If you get moderated, the explanation is there and it is worth reading even if you disagree with the action.
Worth saying I have only my own numbers here, and n is small.
Marking my uncertainty on reading order explicitly. I am confident about the direction, much less confident about the size, and not confident at all that it generalises past the case in the first post.
Reading the guidelines before you post is genuinely worth the twenty minutes. Not because you will break one, but because the rules explain why the place reads the way it does.
The uncertainty is in the assumption, not in the calculation.
A methods point on reading order rather than a substantive one: if the comparison is not like for like, the difference you are measuring is the difference in method.
The version of reading order that circulates here is a simplification of a simplification. It is not wrong, but it has lost the conditions under which it holds, and those conditions are where the interesting cases live.
First week here. The thing I would tell someone arriving behind me is that the answers are slower and much better than anywhere else I have looked, and that trying to hurry one does not work.
Reading it back, the second half matters more than the first.
Asking as the newest person in the thread: is there a canonical order to read the documentation set in? I have been going alphabetically and that is clearly not it.
I would want to see it done twice before believing it once.
That is the distinction I keep failing to hold on to. Written down now.
The Lounge is a real category rather than a dumping ground. The sourcing rule still applies there, which surprises people, but the register is looser and nobody minds a digression.
I would hold that lightly until someone with a larger sample weighs in.
A note on scope: what I am saying about reading order applies to the case in the first post and I would not extend it further without checking.
Welcome. Two practical notes from staff. Your first few posts are rate-limited, which is an anti-spam measure and not a comment on you, and it lifts on its own. If you hit it and have something to add, edit the post you already made.
Collapsed as off-topic by two members at trust level 3 or above
The Lounge is a real category rather than a dumping ground. The sourcing rule still applies there, which surprises people, but the register is looser and nobody minds a digression.
One more caveat and then I will stop qualifying: the sample selected itself.
Reading the guidelines before you post is genuinely worth the twenty minutes. Not because you will break one, but because the rules explain why the place reads the way it does.
Someone should write this up properly, and it should probably not be me.
The compound and evidence pages are updated regularly and they are worth reading when you are new. They answer the meta questions like "do we have data on this" and "what do the trials actually show" before you ask them.
Reading order has been discussed here with more heat than it deserves, mostly because two definitions have been in play the whole time.
Clear enough that I do not think I have a follow-up, which is unusual.
Suggested topics
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
About the Welcome category
Introductions, orientation, and the pinned reading list for new members. This post is a community wiki: any member at trust level 3 or above can edit it, and every edit is recorded with its author and a note.…
|
+3 | 8 | 11k | 27d |
|
Coming back to: A newcomer's list of things that confused me, and the fixes
Posting this under the heading it deserves: A newcomer's list of things that confused me, and the fixes Everything below is what sits behind that. Question in the title. Context below, and I have tried to…
|
+4 | 8 | 57k | 23d |
|
The five documentation pages worth reading before you post anything — a second dataset
On the subject in the title: The five documentation pages worth reading before you post anything — a second dataset Working notes rather than a conclusion. Posting a small dataset on five documentation pages.…
|
2 | 24k | 1d | |
|
Which categories are strict and which are relaxed, honestly
Which categories are strict and which are relaxed, honestly I have a specific reason for asking rather than idle curiosity, and the context is below. I want to check my reasoning rather than get a conclusion.…
|
+46 | 53 | 1.8k | 2d |
|
[2026 update] Are there stupid questions here? A staff answer, at length
Are there stupid questions here? A staff answer, at length — that is the question, and I have not found it answered plainly anywhere I have looked. Counting it rather than describing it, because the count is…
|
+36 | 40 | 2.4k | 1mo |
Related topics — sharing the tags onboarding, guidelines, beginner friendly
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Which categories are strict and which are relaxed, honestly
Which categories are strict and which are relaxed, honestly I have a specific reason for asking rather than idle curiosity, and the context is below. I want to check my reasoning rather than get a conclusion.…
|
+46 | 53 | 1.8k | 2d |
|
What to bring: records that a clinician can actually use
Asking directly, because I could not find a straight answer: What to bring: records that a clinician can actually use A question about how to describe something to a clinician rather than about the thing…
|
+15 | 19 | 6.4k | 1d |
|
A friction point in the promotion workflow — the long version
On the subject in the title: A friction point in the promotion workflow — the long version Working notes rather than a conclusion. A narrow question about friction point, deliberately narrow, because the…
|
+1 | 5 | 46k | 13mo |
|
A newcomer's list of things that confused me, and the fixes
A newcomer's list of things that confused me, and the fixes — setting out what I have, and where I think it stops being reliable. Question in the title. Context below, and I have tried to include the things…
|
+9 | 13 | 34k | 12mo |
|
[2026 update] Hello from a laboratory that does not do peptides
Hello from a laboratory that does not do peptides Writing it up because I had to work it out twice and would rather nobody else did. Saying hello, and stating my interest so that it is on the record rather…
|
2 | 49k | 4mo |