Module Check: Debugging and Iterating with AI
You have covered a lot of ground in this module. You learned that bugs are normal, that error messages are clues, that clear descriptions unlock faster fixes, and that an AI's confidence is not a guarantee of correctness. You practiced describing bugs, building fix requests, verifying changes, and owning the code you ship. This lesson is your chance to see how well all of it stuck — and to consolidate the pieces into one coherent picture before moving on.
Key Terms Review
Flashcards — click each card to reveal the answer
Module Quiz
You encounter an error message for the first time. What is the single most useful piece of information in it?
A classmate says: 'My app is broken. The AI gave me a fix but it is still not working.' Which question would help most?
Which of these is the best example of a controlled experimentation approach to debugging?
You apply an AI fix and the error message disappears. Preferences still reset on page reload. What do you do next?
What is the rule of ownership for AI-generated code?
Your AI assistant confidently says: 'The problem is clearly that your array index starts at 1. Change it to 0.' The explanation sounds reasonable. What is the correct next step?
Debugging is a discipline, not a talent. It has a repeatable process: read the error, describe the bug, build the request, change one thing, test the goal, verify the fix, own the code. Every part of that process makes the next part easier. The more you practice it, the faster and more accurate you become — and the better partner you are for the AI tools that amplify your work.
Capstone: Debug and Document
- This is your module capstone. You will debug a complete scenario from scratch, documenting every step.
- Your teacher will give you a project with three planted bugs. You do not know what they are or where they are.
- For each bug you find:
- 1. Write the full error message (or describe the symptom if there is no error).
- 2. Write the three-part bug description.
- 3. Write the AI fix request you would send (full four-element version).
- 4. State your hypothesis and the one change you would make first.
- 5. After applying the fix (or having a partner apply it): did the goal behavior work? Any regressions?
- 6. Write a two-sentence plain-English explanation of what was wrong and what fixed it.
- This documentation is your deliverable. A complete, honest debugging log for three bugs is the evidence that you have mastered this module.
- Best approach: systematic, curious, one step at a time. Exactly the way you have been practicing.