Learn the vocabulary and structure for asking effective technical questions in English — in Slack, Stack Overflow, GitHub Issues, or with a senior colleague.
0 / 10 completed
1 / 10
What is an 'MRE' (or 'MWE') in the context of asking for help?
An MRE (Minimal Reproducible Example) or MWE (Minimal Working Example) is the smallest, self-contained code snippet that reliably demonstrates the problem. Providing one is the most effective way to get help — it shows you've already isolated the issue.
2 / 10
Which question provides the most useful context when asking for debugging help?
A good technical help request includes: what you expected, what actually happened, the error message, and what you've already tried. This context prevents the helper from repeating steps you've already taken.
3 / 10
What does 'rubber duck debugging' mean?
Rubber duck debugging is the practice of explaining your code or problem out loud, step by step — often to a rubber duck. The act of articulating the problem clearly often causes you to spot the issue yourself before even needing to ask for help.
4 / 10
Which phrase is the best way to frame a question when you are not sure if your understanding is correct?
Framing your question around your mental model ('my understanding is...') invites the helper to correct your assumptions directly. It shows intellectual honesty and makes it easy to identify exactly where your understanding breaks down.
5 / 10
What is 'XY problem' when asking for help?
The XY problem: you want to do X, you think Y is the solution, Y doesn't work, so you ask about Y — but the real problem is X. Always describe your underlying goal, not just the specific approach you got stuck on.
6 / 10
In a GitHub issue, which phrase best introduces the steps to reproduce a bug?
'Steps to reproduce:' is the standard GitHub/GitLab issue convention, typically followed by a numbered list. It signals to the maintainer exactly what they need to do to see the problem themselves.
7 / 10
You've asked for help and the person gave a suggestion that didn't work. What is the most productive response?
Closing the loop with the helper — explaining what you tried, the result, and current state — is efficient and respectful. It lets the conversation build progressively toward the solution rather than repeating ineffective suggestions.
8 / 10
Which phrase is correct when you are escalating an issue to a more senior engineer?
Good escalation summarises what you've already investigated (showing you're not escalating prematurely), states your current hypothesis, and makes a specific request. 'Could you take a look?' is appropriately polite.
9 / 10
What does 'I've been going in circles' mean in a debugging context?
'Going in circles' is an idiom meaning repeatedly cycling through the same (unsuccessful) approaches. When you say this, it signals to your helper that you need a fundamentally different approach, not another attempt at the same strategy.
10 / 10
After a colleague helps you solve a bug, which response is best practice?
Closing the loop with a thank-you and a brief explanation of the solution is good engineering culture. It acknowledges the helper's time and creates a useful reference for anyone who searches for the same error later.