AI tools: pair-programming workflows that don't slow you down

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-tools-ai-pair-programming-workflows-r7a1-creators

1. In AI pair programming, what does it mean to stay in the driver's seat?

   1. The AI writes all the code while you watch and learn
   2. You should let the AI debug your code without supervision
   3. You define intent and decide whether to accept or reject AI output
   4. The AI makes architectural decisions while you handle syntax

2. Which workflow takes advantage of what AI does well?

   1. Letting the AI decide which coding framework to use without input
   2. Having a lengthy conversation with the AI about code style preferences
   3. Asking the AI to generate three different approaches to the same problem
   4. Spending 10 minutes explaining why the AI's previous response was wrong

3. What does it mean that AI 'restarts cleanly' when given a fresh prompt?

   1. The AI remembers previous conversations indefinitely
   2. The AI can completely forget bad suggestions and start fresh without attitude
   3. The AI requires you to re-explain your entire project history
   4. The AI automatically fixes its own errors before responding

4. In the recommended 30-second loop, what should happen in each cycle?

   1. Debug the AI's code, test it, and write documentation
   2. Review the entire codebase for consistency
   3. Write a comment of intent, accept or reject the AI's completion, then move on
   4. Have a detailed discussion about variable naming conventions

5. What should you do if an AI's code suggestion isn't quite right after one attempt?

   1. Restate your intent more precisely or try a fresh prompt
   2. Spend 5 minutes coaxing a better version
   3. Write the code yourself since the AI failed
   4. Explain to the AI why its previous attempt was inadequate

6. Which of these is something AI cannot do in pair programming?

   1. Take real ownership of architectural decisions
   2. Restart cleanly when given a fresh prompt
   3. Produce multiple alternatives on request
   4. Accept rejection without explanation

7. Without explicit feedback, can an AI know when its previous suggestion was bad?

   1. Yes, AI has built-in quality assessment
   2. No, AI doesn't know when its suggestion was bad until you tell it
   3. Yes, AI learns from its mistakes automatically
   4. Yes, AI compares its output to best practices online

8. What risk comes with heavy AI pair-programming use?

   1. The AI might become too powerful
   2. The AI will start writing worse code
   3. You will become dependent on internet access
   4. Your fluency in coding fundamentals may erode because you stop practicing them

9. What is the recommended solution to prevent skill erosion from AI pair programming?

   1. Read more programming books while using AI
   2. Use AI for only half your coding tasks
   3. Reduce the number of projects you work on
   4. Schedule deliberate coding sessions without AI assistance

10. When should you save discussion in an AI pair programming workflow?

    1. When the AI makes syntax errors
    2. For character-level code edits like variable names
    3. For every small problem that comes up
    4. For architectural and design decisions

11. What is the purpose of writing a comment of intent before AI completion?

    1. To add documentation for future developers
    2. To clearly communicate what you want the AI to accomplish
    3. To satisfy the AI's requirement for input
    4. To make the code look more professional

12. What distinguishes effective AI pair programming from ineffective AI use?

    1. Effective use means never writing code yourself
    2. Effective use treats AI as an equal partner with shared responsibility
    3. Effective use requires explaining every detail of your code to the AI
    4. Effective use involves fast rejection and moving on rather than lengthy negotiation

13. How does AI pair programming differ from human pair programming?

    1. AI can work while you sleep
    2. AI can take ownership of the project when you're busy
    3. AI needs explicit direction while human partners can infer intent
    4. AI requires less communication overhead than human partners

14. If an AI produces a flawed solution on the first attempt, what should you generally try before writing the code yourself?

    1. Ask a human developer for help
    2. Restate your intent more precisely or give a fresh prompt
    3. Give up on that approach entirely
    4. Spend 10 minutes arguing with the AI about why it's wrong

15. Why is it valuable that AI accepts rejection without requiring an explanation?

    1. It enables fast rejection cycles without overhead
    2. It improves the AI's future responses
    3. It prevents you from feeling guilty
    4. It makes the AI more intelligent