AI Can Help You Find Bugs in Code

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-the-bug-hunt-r10a5

1. What is a 'bug' in computer coding?

   1. An actual insect inside the computer
   2. A mistake in code that makes it do the wrong thing or crash
   3. A feature you added by accident that turned out great
   4. Any line of code that is very long

2. What should you give AI when asking it to help find a bug?

   1. Just describe the bug in words — no code needed
   2. Only the line number where you think the problem is
   3. The code AND the error message AND what you expected vs what happened
   4. Just the error message — code is too long to paste

3. AI finds a missing comma in your code in seconds. What does this show about AI as a debugging tool?

   1. AI is lucky sometimes
   2. AI is great at spotting small syntax mistakes that are easy for human eyes to miss
   3. AI already knows your code so it's cheating
   4. AI only helps with comma problems

4. How is AI like a 'code doctor'?

   1. It makes your computer healthy by deleting bad code
   2. You describe the symptoms (what went wrong), and AI diagnoses the problem and suggests a cure (the fix)
   3. AI performs surgery on your code without you watching
   4. AI charges a fee to look at broken code

5. What does 'I expected X but it did Y' tell AI when reporting a bug?

   1. Nothing useful — AI doesn't understand expectations
   2. It gives AI the gap between what should happen and what did happen — the most useful clue for finding the bug
   3. It tells AI to rewrite the code completely
   4. It tells AI the variable names used

6. What is an 'edge case' bug?

   1. A bug that only happens at the edges of the screen
   2. A bug that occurs only in unusual situations — like when a number is zero, or when input is empty
   3. A bug that is very small and doesn't matter
   4. A bug at the beginning or end of the code file

7. After AI helps you fix a bug, what question should you ask to learn the most?

   1. 'What is the next bug?'
   2. 'Why did this bug happen and how do I avoid it in the future?'
   3. 'Can you delete the rest of the bugs for me?'
   4. 'How many bugs are left?'

8. What is the 'perfect bug report to AI'?

   1. 'Something is broken'
   2. 'Here is my code [paste], it should do X but does Y, the error says Z. What is wrong?'
   3. 'Fix everything'
   4. 'Find the bug on line 10'

9. Which type of bug is the TRICKIEST to find?

   1. Bugs that cause an error message — those tell you exactly what went wrong
   2. Bugs that crash the code — those are obvious to spot
   3. Bugs that give wrong answers silently — the code runs without errors but produces incorrect results
   4. Bugs that make the code run very slowly

10. A bug only shows up when a user enters a number that's bigger than 1000. What kind of bug is this?

    1. A syntax bug — the code has grammar mistakes
    2. An edge case bug — it only appears with unusual input values
    3. A naming bug — variables are confusingly named
    4. A performance bug — the code is too slow

11. Grace Hopper found the 'first actual bug' in 1947. Why is this piece of history important to coders today?

    1. It proves that moths are attracted to computers
    2. It shows that bugs are as old as computing itself — every coder faces them, even pioneers
    3. It means modern computers don't have real bugs anymore
    4. It explains why debugging tools have animal names

12. AI suggests a one-line fix for your bug. Before applying it, what should you verify?

    1. Nothing — one-line fixes are always safe
    2. That the fix makes sense for your specific situation and doesn't break other parts of the code
    3. That the fix is exactly one character long
    4. That the fix uses the same variable names you have

13. Why does saving a copy of your code BEFORE asking AI to fix a bug matter?

    1. It doesn't matter — AI's fix is always better than the original
    2. If AI's fix makes things worse, you can restore the version that at least had only the original bug
    3. AI requires you to save first before it will help
    4. Saved copies make AI's analysis faster

14. A coder says 'I've been staring at this code for an hour and can't find the bug.' Why might AI find it quickly?

    1. AI has been watching them work the whole time
    2. AI reads the code fresh — without the assumptions and blind spots built up from an hour of staring at it
    3. AI has access to a secret bug database
    4. AI works faster than humans

15. What is the MOST valuable outcome of debugging a bug with AI's help?

    1. The code works again
    2. Understanding WHY the bug occurred so you can avoid the same class of mistake in future code
    3. Proving to others that AI is helpful
    4. Having a shorter conversation with AI