How to Debug Code with AI Quiz

Answers and explanations appear as you take the quiz.

1. Instead of asking the AI to rewrite your whole file, what does the guide recommend asking for?
   • A longer version of the same code
   • The most likely causes and how to check each one
   • A translation of the code into another language
   • More comments throughout the file
2. In a Python traceback, where do you find the exception type and message?
   • On the very first line
   • In the middle of the trace
   • On the final line, because the most recent call is printed last
   • It is not shown in the traceback
3. What is a minimal reproducible example?
   • The smallest code and data that still shows the problem
   • The entire project compressed into one file
   • A screenshot of the error
   • A list of all installed library versions
4. Which bug description gives the AI the most useful information?
   • It doesn't work
   • Please fix my code
   • My code is broken again
   • I expected 10 rows, I get 0, and there is no error
5. Why commit or stash your code before applying an AI's suggested fix?
   • It makes the AI's answers more accurate
   • So you can revert if the suggestion makes things worse
   • It automatically deletes old bugs
   • It uploads your code to the AI
6. Why is the line named in an error message not always where the bug is?
   • Error line numbers are random
   • Compilers often count lines incorrectly
   • The bug is often earlier, where the bad value was created, not where it was used
   • Bugs are always inside third-party libraries
7. After applying a fix, what should you do to confirm it?
   • Close the chat and move on
   • Ask a different AI whether it looks right
   • Assume it works if no error appears
   • Rerun the original failing case plus some normal cases
8. What does the guide suggest doing with your reproduction once the bug is fixed?
   • Turn it into an automated test
   • Delete it to keep the project clean
   • Post it publicly as a tutorial
   • Comment it out for later