Asking Good Questions

Some questions get answered in two minutes. Others sit in Slack for three days, or get a one-word reply that doesn't help at all. The difference usually isn't luck, and it isn't about how senior the person asking is. It's about how the question is built.

Nobody teaches this. You learn to code, then you get dropped into a codebase you don't understand, working with people who are busy, and you're expected to figure out how to ask for help without wasting their time or looking like you didn't try. This guide is the part nobody explains: what makes a question fast to answer, a template you can reuse under pressure, and how to pick the right channel so your question actually lands.

The phases

1. Why Some Questions Get Answered Fast and Others Get Ignored - specificity, showing your work, and the XY problem: asking about your attempted fix instead of the real problem.
2. The Question Template That Actually Works - a reusable structure for any question, plus a bad question rewritten into a good one.
3. Async vs. Sync, and Reading the Room - Slack versus a ticket versus a meeting versus walking over, respecting focus time, and when to escalate.

Read them in order. If your question is already solid and you only need to know where to send it, start with Phase 3.