post #60 is right about the mechanism and I think understates the practical bit.
For anyone arriving from a search: the marked solution above is the direct answer, and the replies underneath it add the caveats that make it safe to use.
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1 · go to the accepted answer.
post #60 is right about the mechanism and I think understates the practical bit.
For anyone arriving from a search: the marked solution above is the direct answer, and the replies underneath it add the caveats that make it safe to use.
Worth separating two things that post #58 runs together.
What you have already read matters. Saying "I read the maintained page on this and I still have a gap" tells people they do not need to point you at the same resource you have already found. That is a genuine time saver.
Context that matters: compound, how long in, current dose, relevant history. Context that does not matter: how you feel, your hopes for the outcome, your medical history beyond what affects this specific question. The first set gets you answered. The second set makes the reply longer without making it better.
Five questions in one post gets you one answer: the easiest one, usually not the one you needed most. Post them separately or pick the one that depends on the others least and ask that one first.
post #64 answers the question as asked. The question underneath it is different.
Avoid "any advice?" at the end. It is so generic that people do not know which part of the post it refers to. Pick the specific part and ask that specific question instead.
Two things before anyone answers the substance.
First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.
Asking a follow-up: new topic or reply in the old one? If the answer depends on the previous post, reply. If it is a question that makes sense without the previous post, new topic. The second gets faster answers.
Coming back to post #66, because the follow-up matters more than the original answer.
Disagreement-style questions: "I read this and it contradicts what I heard here, which is right?" is answerable. "Is this a bad idea?" without giving the context is not.
Questions you cannot explain: "I cannot say why I am asking this, but is this compound stable at room temperature?" is more productive than no question at all. People here know that some questions cannot be asked in public and they will work with that constraint.
Units. Everything needs units. This is why we ask every single time. I have seen the same arithmetic done three different ways depending on whether the person was thinking mg/mL or mg/dose or something else entirely. Stating the units makes that impossible.
Context that matters: compound, how long in, current dose, relevant history. Context that does not matter: how you feel, your hopes for the outcome, your medical history beyond what affects this specific question. The first set gets you answered. The second set makes the reply longer without making it better.
Thank you for the correction. I have edited my earlier post with a note rather than silently, so the thread still makes sense to read. The error was mine and it was the kind that comes from remembering a figure instead of looking it up.
On post #69 — agreed on the reasoning, with one qualification.
Arithmetic questions: write out the steps. "I have a 10 mg vial, I added 2 mL, I want a 0.25 mg dose, and I get this number for the syringe mark" is answerable. "How many units" is not.
post #73 answers the question as asked. The question underneath it is different.
Chromatogram questions: describe the method first. Column type, gradient, wavelength, detection method. Everything else follows from method. A chromatogram without method is a number without context.
Worth separating two things that post #73 runs together.
The specific question in the title is more useful than you might think. A title like "a question I have" forces the person answering to guess what you want to know. A title with the actual question gets you an answer in two hours instead of two days.
What you have already read matters. Saying "I read the maintained page on this and I still have a gap" tells people they do not need to point you at the same resource you have already found. That is a genuine time saver.
Five questions in one post gets you one answer: the easiest one, usually not the one you needed most. Post them separately or pick the one that depends on the others least and ask that one first.
Picking up post #77: that is the part I would want checked first.
Asking a follow-up: new topic or reply in the old one? If the answer depends on the previous post, reply. If it is a question that makes sense without the previous post, new topic. The second gets faster answers.
Disagreeing with an answer you got: cite what you disagree with, say what contradicts it, and ask which one holds. Do not open with "I think you are wrong". Lead with the evidence.
I read post #80 twice before replying, because I had assumed the opposite.
Avoid "any advice?" at the end. It is so generic that people do not know which part of the post it refers to. Pick the specific part and ask that specific question instead.
post #82 is right about the mechanism and I think understates the practical bit.
Thank you for the correction. I have edited my earlier post with a note rather than silently, so the thread still makes sense to read. The error was mine and it was the kind that comes from remembering a figure instead of looking it up.
Questions you cannot explain: "I cannot say why I am asking this, but is this compound stable at room temperature?" is more productive than no question at all. People here know that some questions cannot be asked in public and they will work with that constraint.
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Coming back to: How much context is too much context in a first post?
Asking directly, because I could not find a straight answer: How much context is too much context in a first post? Question in the title. Context below, and I have tried to include the things people here…
|
+2 | 6 | 7.5k | 1d |
|
How to disagree with an answer you were given, well
How to disagree with an answer you were given, well — that is the question, and I have not found it answered plainly anywhere I have looked. Question in the title. Context below, and I have tried to include…
|
+9 | 13 | 1.6k | 1mo |
|
Revisiting: Five questions in one post gets you one answer — how to split them
Revisiting: Five questions in one post gets you one answer — how to split them Writing it up because I had to work it out twice and would rather nobody else did. Question in the title. Context below, and I…
|
+2 | 6 | 13k | 20mo |
|
Rewriting my first post: a before-and-after, with commentary — what changed since
Posting this under the heading it deserves: Rewriting my first post: a before-and-after, with commentary — what changed since Everything below is what sits behind that. I want to check my reasoning rather…
|
+15 | 19 | 12k | 13h |
|
The anatomy of a question that gets answered within an hour
The anatomy of a question that gets answered within an hour — 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…
|
+113 | 127 | 2.7k | 13h |
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
When to stop reading forums, including this one — the long version
Asking directly, because I could not find a straight answer: When to stop reading forums, including this one — the long version General question, not a request for advice about my own care — I know the…
|
+23 | 27 | 8.3k | 14mo |
|
Follow-up: What this community means by "a source", in practical terms
The question in the title: What this community means by "a source", in practical terms I will give what I have already checked below so nobody repeats it. I want to check my reasoning rather than get a…
|
+16 | 20 | 7k | 18mo |
|
An ABAB design with a data table and honest limitations — a second dataset
On the subject in the title: An ABAB design with a data table and honest limitations — a second dataset Working notes rather than a conclusion. Session topic: STEP 2 ( Lancet , 2021). Please read it before…
|
+106 | 118 | 25k | 4mo |
|
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 |
|
Coming back to: Why most self-reports here are not experiments, and that is fine
The question in the title: Why most self-reports here are not experiments, and that is fine I will give what I have already checked below so nobody repeats it. Comparing LEADER ( N Engl J Med , 2016) with…
|
+56 | 62 | 11k | 4mo |