Key Terms: How to Ask for Help
Generated with AI assistance — review for accuracy and compare against your course materials.

---

CONTEXT (IN A HELP REQUEST)
The background information that lets someone understand your situation without having to ask follow-up questions. A good help request includes what you are trying to do, what you have already tried, and what happened when you tried it.

DEBUGGING
The process of finding and fixing the cause of an error or unexpected behavior. Before asking for help with a bug, attempting to debug it yourself — by reading the error message, checking recent changes, and isolating the problem — often resolves it and always improves your question.

DOCUMENTATION
Written reference material explaining how to use a tool, library, function, or system. Documentation is often the fastest path to an answer for "how do I do X" questions and should be the first place you look.

ERROR MESSAGE
A message generated by a program or system when something goes wrong. Error messages often contain the exact type of problem, the file and line number where it occurred, and sometimes a suggested fix. Reading the error message carefully before asking for help is the most overlooked step.

FORUM ETIQUETTE
The norms and expectations for asking questions in online communities such as Stack Overflow, Reddit, or Discord servers. This typically includes: searching for existing answers first, providing a minimal reproducible example, showing what you have already tried, and responding politely to answers.

HELP REQUEST
A specific, structured question that gives someone enough information to help you effectively. A good help request is not "it's broken" — it describes the expected behavior, the actual behavior, and the steps taken so far.

MINIMAL REPRODUCIBLE EXAMPLE (MRE)
The smallest, simplest version of your problem that still demonstrates the issue. Creating an MRE often reveals the cause of the problem before you even ask the question, and makes it much easier for others to help you.

OFFICE HOURS
Scheduled time when an instructor, TA, or support person is available to answer questions. Widely underused; going to office hours with a specific, prepared question is one of the most efficient ways to get unstuck in an academic context.

QUESTION FRAMING
How you structure and present a question. A well-framed question is specific, includes context, shows what you have already tried, and makes it easy for the other person to understand what you need without additional back-and-forth.

RUBBER DUCK DEBUGGING
The practice of explaining a problem out loud — to a rubber duck, a person, or an AI — as a way to find the solution yourself. The act of articulating the problem often reveals the answer before anyone else responds.

SELF-SUFFICIENCY
The ability to solve problems independently using available resources such as documentation, search engines, and error messages. Not the same as never asking for help — it means making a genuine attempt before escalating.

STACK OVERFLOW
A popular question-and-answer website for programming problems. Before posting a new question, searching Stack Overflow for your error message or problem often returns an existing answer.

TROUBLESHOOTING
A systematic approach to diagnosing and resolving a problem: identify the symptoms, form a hypothesis about the cause, test it, and repeat. Troubleshooting before asking for help narrows down the problem and improves the quality of any help request you do send.