Ask AI to 'Make This Code Cleaner'

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-rewrite-it-cleaner

1. What does 'refactoring' code mean?

   1. Deleting code that doesn't work
   2. Making code do a different job than before
   3. Cleaning up code so it's easier to read while keeping the same job
   4. Adding lots of new features to code

2. What should you say to AI when you want it to clean up your code?

   1. Delete everything and start over
   2. Rewrite this cleaner but keep the same meaning
   3. Add more features to this code
   4. Make this code do something different

3. After AI refactors your code, what should you always do?

   1. Delete the original code immediately
   2. Trust AI completely and never check
   3. Run and test the code to make sure it still works
   4. Share it online before testing

4. Which of these is an example of refactoring?

   1. Changing code so it adds numbers instead of subtracting them
   2. Renaming confusing variable names to clear, descriptive ones
   3. Adding a new game level to the program
   4. Making the code run on a different computer

5. Why is cleaner code easier to fix when bugs appear?

   1. Cleaner code never has bugs
   2. Cleaner code runs faster so bugs don't matter
   3. When code is easier to read, it's easier to spot where something went wrong
   4. Cleaner code automatically fixes itself

6. You have code that works but has three copies of the same section repeated. What might AI do when refactoring?

   1. Delete all three copies
   2. Combine them into one reusable piece that gets called three times
   3. Leave them as-is since they work
   4. Make six copies instead

7. What is the MOST important thing refactored code must do?

   1. Look impressive
   2. Be shorter than the original
   3. Keep doing the exact same job as the original code
   4. Use more advanced programming techniques

8. Why do professional coders refactor their code?

   1. Because they got bored and wanted something to do
   2. To make code cleaner so it's easier to read, fix, and share with teammates
   3. Because old code always breaks and must be replaced
   4. To make the code run slower but look nicer

9. What should you do after AI refactors your code to prove you understand it?

   1. Immediately use it without reading
   2. Compare the before and after, and be able to explain each change AI made
   3. Show it to a friend without looking at it yourself
   4. Delete the original so you can't compare

10. A student pastes spaghetti code into AI and asks it to clean up. AI returns a shorter version. The student pastes it in without reading it. What problem could happen?

    1. Nothing — AI never makes mistakes
    2. AI might have changed what the code does, not just how it looks
    3. The code will automatically become longer again
    4. Other students will see the code and copy it

11. Which prompt would work BEST for asking AI to refactor your code?

    1. 'Fix this'
    2. 'Make this code different'
    3. 'Rewrite this code to be cleaner and easier to read, but keep the exact same behavior'
    4. 'Delete what you don't like'

12. Code that is 'clean' means it is:

    1. Free from viruses
    2. Written in a style that humans can easily read and understand
    3. Running at maximum speed
    4. Hidden from other coders

13. If AI refactors code and makes it shorter, but you notice it now gives wrong answers, what should you do?

    1. Accept the refactored version since shorter is always better
    2. Go back to the original and tell AI specifically what behavior must be preserved
    3. Delete both versions and ask AI to start fresh
    4. Use the refactored version and hope users don't notice

14. Why is refactoring called a 'skill' and not just a task AI does for you?

    1. Because only AI can truly refactor code
    2. Because refactoring requires judgment about what 'cleaner' means for your specific code
    3. Because refactoring must be done without any AI help
    4. Because it only works in certain programming languages

15. A long chain of if-else statements does the same thing as a neat lookup table. Which is the refactored version and why?

    1. The if-else chain — it shows all the logic explicitly
    2. The lookup table — it achieves the same result in a much cleaner, shorter structure
    3. Neither — they are both equally good
    4. Whichever one was written first is the 'original'