Ask AI for Better Names in Your Code

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-name-things-well-r10a5

1. What is a 'variable' in coding?

   1. A type of programming mistake
   2. A named storage spot that holds a piece of information in a program
   3. A function that changes something
   4. A line of code that has errors

2. Why is 'numLives = 5' better than 'x = 5' in a game program?

   1. It isn't — 'x' is a classic math variable name that coders prefer
   2. 'numLives' immediately tells you what the 5 represents — number of lives — while 'x' tells you nothing
   3. 'numLives' runs faster than 'x'
   4. 'x' is harder to type so it's better discipline

3. What should you ask AI to do to improve variable and function names in your code?

   1. 'Delete all variables'
   2. 'Rename my variables and functions to be clearer for a beginner'
   3. 'Make my variable names shorter'
   4. 'Add numbers to every variable name'

4. Good variable names should sound like what?

   1. Computer codes nobody else can read
   2. Real English words that describe what the variable holds
   3. Short single letters to save space
   4. Random words that are easy to type

5. The 'naming test' for a variable is: can someone read the name and immediately understand what it holds? Which name PASSES this test?

   1. x2
   2. t
   3. totalScoreAfterBonusRound
   4. nswptt

6. What does 'future-you will thank you' mean when it comes to good variable names?

   1. You'll be paid money in the future for good names
   2. When you revisit your code weeks later, clear names will help you understand what each piece does — saving hours of confusion
   3. Your future computer will run the code faster
   4. Other people will write thank-you notes about your code

7. Why does a function name need to describe what it DOES rather than what it IS?

   1. It doesn't — functions and variables should be named the same way
   2. Because functions are actions — their names should be verbs that tell you what action they perform
   3. Because function names affect how fast the function runs
   4. Because functions don't hold values, so IS names don't apply

8. What is the 'before and after' challenge when working with AI on naming?

   1. Ask AI to write code before naming it, then name it after
   2. Show AI code, ask for renamed version, and compare the before and after to see how clarity improved
   3. Name all variables before writing the code logic
   4. Write code twice — once before asking AI for help, once after

9. Why does a variable name that needs a comment to explain it probably need a better name?

   1. Comments are not allowed in most programming languages
   2. If you need a comment to explain the name, the name isn't doing its job — the name itself should be self-explanatory
   3. Comments slow down the code
   4. Only AI-generated names don't need comments

10. What does asking AI to 'rename everything so a kid could read it' achieve?

    1. It makes the code simpler and less powerful
    2. It replaces technical-sounding names with clear, descriptive ones that any reader can follow
    3. It adds cartoon character names to variables
    4. It makes the code shorter

11. There's a famous joke: 'There are only two hard things in computer science: cache invalidation and naming things.' What does this tell you about naming?

    1. Naming is considered easy and not worth much attention
    2. Even expert programmers find good naming genuinely challenging — it's a skill worth developing seriously
    3. You should avoid naming things and use numbers instead
    4. Only certain programmers need good naming skills

12. Which scenario shows that bad naming caused a real problem?

    1. A student used 'i' as a loop counter and the loop worked fine
    2. A student renamed 'x' to 'playerScore' and the code got cleaner
    3. A student couldn't remember if 'temp2' stored a temperature or a temporary calculation — causing a bug from misunderstanding their own code
    4. A teacher asked a student to use shorter names

13. When is it okay to use a short name like 'i' in code?

    1. Never — always use full descriptive names
    2. For simple loop counters where the variable is used in only 2-3 adjacent lines and its purpose is obvious from context
    3. Whenever the code is private and only you will see it
    4. Whenever you're in a hurry

14. AI renames 'calc()' to 'calculateStudentFinalGrade()'. The new name is much longer. Is this better or worse?

    1. Worse — shorter names are always better in code
    2. Better — the longer name instantly tells you exactly what this function computes, eliminating all ambiguity
    3. Neither — length doesn't affect code quality
    4. Worse — it will cause performance issues

15. A student shares their code and another student can follow exactly what it does just by reading the variable and function names, without any comments. What has the first student achieved?

    1. They cheated by using too many descriptive names
    2. 'Self-documenting code' — code that's so clearly named it explains itself without extra comments
    3. A style error — code needs comments to be complete
    4. Lucky coincidence — readability can't be intentional