Asking for Help

Learning Objectives Identify the difference between a helpful and an unhelpful question about a coding problem. Explain what they want their code to do (the expected outcome). Describe what their code is actually doing (the actual outcome). List at least two debugging steps they tried before asking for help. Formulate a complete, specific question about a coding problem involving loops or conditionals. Create a minimal, reproducible example of their coding problem. Have you ever been stuck on a coding puzzle and just wanted to shout, 'It's broken!'? 🙋‍♀️ Let's learn how to turn that shout into a super-smart question that gets you unstuck faster! This lesson teaches you the most important secret skill of expert programmers: how to ask for help effectivel...

TermDefinitionExample DebuggingThe process of finding and fixing errors, or 'bugs,' in your code. Asking for help is a part of debugging!You run your code and the character moves left instead of right. You look through your code line-by-line to find the mistake. That's debugging. Expected OutcomeWhat you want your program to do. It's the goal you are trying to achieve with your code.I expect my loop to run 5 times and print the numbers 1, 2, 3, 4, 5. Actual OutcomeWhat your program actually does when you run it. This might be different from what you expected.My loop actually runs forever and never stops. This is the bug I need to fix. Reproducible ExampleA small, simple piece of code that shows the problem you are having. It lets someone else run your code and see the...

The 'Try Three, Then Ask' Rule Before asking for help, try to solve the problem on your own in at least three different ways. Use this rule when you first get stuck. It helps you become a better problem-solver and shows the person you ask that you've already put in effort. Your three tries could be: 1. Rereading your code carefully. 2. Adding a print statement to see a variable's value. 3. Searching for a similar example in your notes. The 'What, How, Why' Question Pattern 1. WHAT I want to do. 2. HOW I tried to do it (show code). 3. WHY it's not working (actual vs. expected outcome). This is the best way to structure your question. It gives the helper all the information they need to understand your problem quickly without having to ask lo...