AI Helps You Find the Sneaky Bug

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-explorers-ai-coding-AI-and-debugging-fun

1. What is a 'bug' in coding?

   1. A real insect that crawls into your computer
   2. When code does the wrong thing due to a mistake
   3. A feature that makes your game harder
   4. A type of computer virus

2. Where did the word 'bug' in coding come from?

   1. A programmer named Mr. Bug invented it
   2. A real moth got stuck inside a computer in 1947 and caused it to malfunction
   3. Bug is short for 'Bad Ugly Glitch'
   4. It comes from a video game character named Bug

3. When you ask AI to help debug your code, what should you share?

   1. Just the error message, not the code
   2. Just the code, not the error message
   3. Both the broken code AND the error message
   4. Only the line number where the bug is

4. What is a 'syntax error'?

   1. When your code runs but gives the wrong answer
   2. A typo or mistake in the code's special rules and symbols
   3. When your computer is too slow to run the code
   4. When you forget to save your file

5. Your code runs without any errors, but the score in your game keeps going up by 2 instead of 1. This is MOST likely a:

   1. Syntax error
   2. Logic error
   3. Computer crash
   4. Keyboard problem

6. You paste your code into AI and say 'It's not working!' AI reads it and says 'Look at line 3 — you forgot a colon.' What type of bug did it find?

   1. A logic error
   2. A syntax error
   3. A computer virus
   4. A network error

7. Why is AI described as being like a 'detective' when debugging?

   1. AI wears a detective hat while it works
   2. AI reads clues (your code and error) and figures out what went wrong
   3. AI detective games are the most popular type
   4. Debugging always involves solving a mystery game

8. Your friend says bugs in coding are embarrassing and you should hide them. Is this TRUE or FALSE?

   1. True — only bad coders have bugs
   2. True — professionals never have bugs
   3. False — every coder, even the best ones, has bugs every day
   4. False — only beginners have bugs

9. What does AI show you when it finds a bug in your code?

   1. It just fixes the code without explaining anything
   2. It explains what went wrong and often shows the fixed code next to the broken code
   3. It deletes the broken code automatically
   4. It sends you a warning email

10. You try to debug by changing 5 things at once. What's the PROBLEM with this approach?

    1. Nothing — changing more things means you fix it faster
    2. You won't know which change actually fixed the bug
    3. The computer can't handle 5 changes at once
    4. AI will get confused by too many changes

11. Grace Hopper found the 'first actual case of bug being found' in 1947. Who was Grace Hopper?

    1. A famous video game designer
    2. A computer scientist who helped invent modern computing
    3. The inventor of the internet
    4. A teacher who taught kids to code

12. You ask AI: 'Walk me through what each line does without fixing it yet.' Why is this a GREAT debugging strategy?

    1. It wastes time — you should just ask AI to fix it directly
    2. Understanding WHY it broke helps you avoid the same bug next time
    3. AI requires this format or it won't help you
    4. Walking through lines makes AI work faster

13. An error message tells you the bug is on 'line 7.' You look at line 7 but it looks fine. What should you try next?

    1. Delete line 7 entirely
    2. The bug might actually be on the line BEFORE it — check line 6 too
    3. Restart your computer to reset the line counter
    4. The error message must be wrong, ignore it

14. What does 'debugging' mean?

    1. Adding more features to your code
    2. Finding and fixing mistakes in code
    3. Making your code look prettier
    4. Saving your work to the computer

15. Liam is really frustrated because his code has bugs. What should he remember?

    1. Only bad coders have bugs, so he should give up
    2. Bugs mean his computer is broken and needs to be replaced
    3. Bugs are normal — every coder has them and fixing them is how you get better
    4. He should never share code with bugs in it