Asking for Help: Talking to a Grown-Up

Learning Objectives Formulate a specific question about a coding problem using the 'Goal, Tried, Happened, Expected' pattern. Deconstruct a large coding problem into smaller, testable parts before asking for help. Use precise vocabulary (e.g., 'infinite loop,' 'syntax error,' 'variable value') when describing a problem to an adult. Create a simple 'help request' algorithm using conditional logic. Translate a computer error message into a plain-language question. Create a Minimal Reproducible Example (MRE) to demonstrate a bug. Ever felt your brain turn into a spinning rainbow wheel when your code just won't work? 😵‍💫 What's your next move? Asking for help is one of the most important skills a programmer can have!...

TermDefinitionExample Debugging MindsetThe belief that problems can be solved step-by-step and that getting stuck is a normal part of coding, not a failure.Instead of saying 'My code is broken!', you think 'Okay, where is the first point of failure? Let's trace the variable’s value inside the loop.' Problem DecompositionBreaking a big, confusing problem down into smaller, manageable pieces.Instead of asking for help on 'my game doesn't work,' you first test just the character's movement. You ask for help on that one small piece: 'Why won't my character jump when I press the spacebar?' Minimal Reproducible Example (MRE)The smallest possible piece of code that shows the bug you're experiencing, separate from the rest of your p...

The 15-Minute Rule IF you are stuck on a problem, THEN work on it by yourself for 15 minutes. ELSE IF you are still stuck after 15 minutes, THEN ask for help. This rule ensures you try to solve the problem on your own first, which is how you learn best. But it also prevents you from wasting too much time being frustrated. It's a balance between independence and getting help when you need it. The 'Rubber Duck' Algorithm 1. Find an object (like a rubber duck). 2. Explain your code to the object, line-by-line. 3. Describe what you expect each line to do. 4. Explain the bug out loud. Use this *before* asking a person. The act of explaining the problem out loud often helps you find the solution yourself. The duck doesn't need to understand; you just need to ta...