asking a question
that gets an answer

this is a real skill and nobody teaches it. it is worth learning because it pays off with tutors, lecturers, teaching assistants, group chats and every colleague you will ever have.

show the exact point
it stopped making sense

not the chapter. not the topic. the line. "i followed it until they factored out the x and then i lost it" tells someone precisely where to start, and the reply comes back aimed at the gap instead of at the whole subject.

say what you already tried

even when it was wrong — especially when it was wrong. the attempt shows how you are thinking, and how you are thinking is usually where the misunderstanding lives. an answer that fixes your reasoning is worth more than one that just supplies the correct steps.

say what you think
should happen

"i expected the answer to be negative because the force is downward" turns a vague confusion into a testable belief. often the wrong expectation is the problem, and naming it out loud finds it in one line.

include the actual thing

a photo of the problem beats a retyped version, because how the question is worded is frequently the issue. include the whole question, not just the part you think matters — the constraint you skipped is often the one doing the work.

ask for the reasoning,
not the answer

"what is the answer" gets you one mark. "how would i know which method to reach for here" gets you the next five questions too. the useful ask is almost always about the choice, not the arithmetic.

a worked shape

weak: "can someone help with q7"

strong: "q7, photo attached. i used conservation of momentum because it is a collision, got 4.2 m/s, and the answer key says 2.8. i think i am wrong about whether it is elastic — how do i tell from the question?"

the second one gets a genuinely useful answer from anybody. it is also, not coincidentally, the shape of a good post in the app — how it works.

related

notes worth re-reading · how it works · faq