Save Code Versions Before AI Changes Them

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-version-saves-r10a5

1. What is a 'version' of your code?

   1. A different programming language to run the same program
   2. A saved snapshot of your code at a specific point in time
   3. The official release of a programming language
   4. A copy of AI's suggestions

2. When should you save a copy of your code BEFORE asking AI for help?

   1. Never — AI will remember the original version
   2. Only when you have a LOT of code
   3. Always, before any significant AI-suggested change to your code
   4. Only on Fridays before the weekend

3. What is a beginner-friendly way to save code versions without learning 'git'?

   1. Email yourself the code
   2. Take a screenshot of the screen
   3. Duplicate the file and name it with a version number, like 'game-v1.py,' 'game-v2.py'
   4. Print the code on paper

4. What is 'git' in coding?

   1. A type of bug that hides in code
   2. A free professional tool that automatically saves every version of your code and tracks all changes
   3. Another name for a backup drive
   4. A keyboard shortcut for saving

5. AI improves your code but accidentally removes a feature you liked. What does having a version save let you do?

   1. Nothing — once AI changes code, the original is gone forever
   2. Go back to your saved version and try a different approach or rescue the removed feature
   3. Complain to AI and ask for an apology
   4. Wait a week and the feature might reappear

6. What is a good name for a version you save when basic movement in your game is working?

   1. 'stuff'
   2. 'game-v1-basic-movement.py'
   3. 'save1'
   4. 'temp'

7. Why are versions described as turning 'scary experiments into safe adventures'?

   1. Because adventures are fun and experiments are not
   2. Because with a saved version to fall back on, trying risky changes becomes low-risk — you can always go back
   3. Because version numbers look like adventure level numbers
   4. Because AI codes faster when it knows you have versions

8. What should you save a version of, even when your code isn't finished yet?

   1. Nothing — only save when fully complete
   2. Only when you've been coding for more than an hour
   3. Any state where specific features are working well — even if other features are still missing
   4. Only when AI has reviewed the code

9. How is a code version like a 'time machine'?

   1. It makes code run at different speeds
   2. It lets you travel forward in time to see future bugs
   3. It lets you go back to exactly how your code was at a previous moment
   4. It remembers future versions of code you haven't written yet

10. The 'version-before-AI rule' says: always save a copy before AI makes changes. Why is this especially important compared to other types of edits?

    1. Because AI changes are always wrong
    2. Because AI can make large sweeping changes quickly — sometimes changing much more than intended
    3. Because AI refuses to help if you haven't saved first
    4. Because AI code doesn't work with version control tools

11. A student has 'game-v1.py,' 'game-v2.py,' and 'game-v3.py.' v3 is broken. What are their options?

    1. They have no options — v3 is the current version
    2. They can open v2 (or v1) to find the last working state, compare with v3 to see what changed, and fix from there
    3. They must delete v1 and v2 since they're outdated
    4. They must start completely from scratch

12. What is the main advantage 'git' has over the numbered-file approach to versions?

    1. Git is free and numbered copies cost money
    2. Git automatically tracks every change, who made it, and when — making it easy to compare any two versions or undo specific changes
    3. Git only works with certain programming languages
    4. Git is faster to type than long file names

13. A student says 'I didn't save a version because I only asked AI for a small change.' What risk did they take?

    1. No risk — small changes are always safe
    2. Even small AI changes can have unexpected side effects elsewhere in the code
    3. Only large changes need version saves
    4. AI small changes automatically undo if they cause problems

14. What does 'backups = safety net for code experiments' mean in practice?

    1. Experiments should be avoided entirely when coding
    2. Knowing you can go back makes you willing to try bold changes — increasing what you learn and discover
    3. Safety nets slow down coding experiments
    4. Backup files count as experiments

15. What is the 'one time you really needed to' warning about versioning?

    1. There is only one time in a coding career when versions matter
    2. The one time you skip versioning before an AI change will be the one time that change goes badly wrong — and you can't recover
    3. You only need versions when working with teammates
    4. The warning is that you need at least 10 versions to be safe