Debug With Error Receipts

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-vibecoder-debug-with-error-receipts

1. Which piece of information is LEAST important to include when filing a bug report for an AI coding assistant?

   1. The exact URL where the error occurred
   2. Your emotional reaction to the problem
   3. The console error message if present
   4. The expected behavior versus what actually happened

2. A developer asks an AI to 'fix my broken authentication system' without specifying what specifically is broken. What principle from debugging best practices does this violate?

   1. Inspect the diff before sharing
   2. Check the network tab for errors
   3. Name the job before naming the tool
   4. Run the result as a user, not a fan

3. Why should you run AI-generated code 'as a user, not as a fan of the tool'?

   1. Because tools always work correctly on the first try
   2. Because fans get banned from using AI services
   3. Because the AI might become offended if you test critically
   4. Because uncritical acceptance masks real problems and security gaps

4. What is 'scope creep' in the context of AI-assisted coding?

   1. When a developer keeps adding more features beyond the original request, making fixes too complex
   2. When the AI accidentally deletes your project files
   3. When network requests take too long to complete
   4. When code runs faster than expected

5. RLS (Row Level Security) in Supabase is designed to:

   1. Make database queries run faster
   2. Generate random test data for development
   3. Control which users can access specific rows of data
   4. Automatically fix syntax errors in SQL

6. What does 'inspecting the diff' mean?

   1. Checking your bank account balance
   2. Looking at the price differences between AI tools
   3. Reviewing the changes (differences) between the original and modified code
   4. Comparing different programming languages

7. Before sharing problematic code with an AI assistant, you should first:

   1. Inspect the diff, data access patterns, and failure path
   2. Format the code with as many spaces as possible
   3. Delete all comments so the AI doesn't get confused
   4. Write a detailed apology for the broken code

8. What is the recommended scope when asking an AI to fix a bug?

   1. The entire application should be rewritten from scratch
   2. As many features as possible to ensure completeness
   3. Only the visual appearance, not functionality
   4. The smallest useful piece that can be completed and tested

9. Which of the following is an example of data that should NEVER be exposed to unauthorized users?

   1. Public blog post content
   2. Publicly shared project templates
   3. User passwords and authentication tokens
   4. General feature descriptions

10. What is a rollback plan?

    1. An AI tool that automatically writes tests
    2. A way to return to a previous version if a change causes problems
    3. A method for rolling out new features to users
    4. The process of writing code documentation

11. What does 'vibe coding' refer to?

    1. Using AI to generate code quickly while the human maintains product judgment and safety
    2. The practice of only coding during certain moods
    3. Writing code while listening to music
    4. A programming language designed for beginners

12. In browser developer tools, the Network tab primarily shows:

    1. CSS styling errors
    2. Memory usage statistics
    3. HTTP requests and responses, including status codes and timing
    4. JavaScript syntax errors

13. Why is 'reproduction' important in debugging?

    1. It is required by law
    2. It allows you to reliably trigger and study the problem
    3. It automatically fixes the issue
    4. It makes the bug sound more impressive

14. Comparing 'expected result' to 'actual result' helps you:

    1. Understand the gap between what should happen and what actually happened
    2. Calculate how much money the bug cost
    3. Determine exactly what the AI was thinking
    4. Decide whether to keep using the AI tool

15. Why is recording the exact time of an error useful?

    1. Time information is not actually useful
    2. It helps impress technical support with your thoroughness
    3. It helps correlate the error with server logs, deployment times, or other time-sensitive factors
    4. It is required for all bug reports by law