Database Migrations Are Not Suggestions

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-coder-database-migrations-creators

1. What is the primary purpose of a database migration?

   1. To speed up query performance
   2. To automatically generate test data
   3. To delete all existing data from the database
   4. To create an explicit, reversible record of schema changes

2. Before an AI agent modifies a database schema, what should be defined first?

   1. The exact model of GPU running the agent
   2. The color scheme of the application
   3. The specific SQL syntax the agent should use
   4. The rollback procedure if something goes wrong

3. Why does the lesson advise running code 'as a user, not as a fan of the tool'?

   1. To verify the change actually works for end users, not just in theory
   2. To avoid triggering rate limits
   3. To impress the AI agent with your skills
   4. To save computational resources

4. What does the lesson mean by 'vibe-coded apps break most painfully at the database layer'?

   1. Database changes made without proper planning cause the most difficult failures to recover from
   2. AI-generated code works perfectly in databases but fails elsewhere
   3. Database servers are physically more fragile than other components
   4. Visual design errors are most noticeable in databases

5. Which approach best follows the lesson's advice on scoping agent tasks?

   1. Give the agent full access to modify anything in the codebase
   2. Break the task into the smallest useful piece the agent can complete successfully
   3. Ask the agent to refactor the entire codebase in one prompt
   4. Have the agent generate code without any specific requirements

6. What three things should be inspected before sharing an AI-generated schema change?

   1. The server location, electricity cost, and cooling requirements
   2. The diff, data access patterns, and failure path
   3. The marketing copy, user interface colors, and font choices
   4. The code comments, variable names, and indentation

7. What information should be documented about what the user can do when a database change is finished?

   1. The user's favorite color
   2. The specific workflows and capabilities the user gains
   3. The AI model's temperature setting
   4. The internal database table names

8. According to safe database practices, what should an application never expose?

   1. Technical documentation
   2. User interface buttons
   3. Error messages
   4. Sensitive data such as passwords, API keys, or personal information

9. What is a 'rollback path' in the context of database migrations?

   1. The visual route users take through a UI
   2. The network route between the app server and database
   3. The path the AI agent takes to generate code
   4. A documented procedure to reverse the database change if it causes problems

10. The lesson mentions that AI can make a working demo quickly. What distinguishes a real coder from just demo generation?

    1. Choosing fancier variable names
    2. Making the demo observable, reversible, and safe for production use
    3. Using more expensive AI models
    4. Writing longer code comments

11. What does 'name the job before naming the tool' mean in this lesson?

    1. Choose a cool project name before coding begins
    2. Pick a database name first, then create tables
    3. Decide on a username before creating an account
    4. Define what needs to be accomplished before selecting how to accomplish it

12. Why should an AI agent never 'freestyle production tables'?

    1. Because unscripted schema changes can cause data loss or corruption without recovery options
    2. Because AI cannot write SQL syntax
    3. Because it uses too much electricity
    4. Because production databases don't exist

13. What type of test proves that a database schema change works correctly?

    1. A test that verifies the actual functionality and data integrity the change was meant to enable
    2. A test that counts the number of code comments
    3. A test that measures how fast the AI generates code
    4. A test that checks the screen resolution of the display

14. What is a schema in the context of databases?

    1. The visual layout of a website
    2. The structure defining tables, columns, relationships, and constraints
    3. The physical location of the database server
    4. The programming language used to write the application

15. What makes a schema change 'explicit and reviewable' as the lesson recommends?

    1. Hiding the change in compiled binary code
    2. Making the change as vague as possible
    3. Using cryptic variable names to make it hard to understand
    4. Creating a documented migration that can be examined before application