HAP learning with AI assistance

Station 6: AI as Your Study Partner

Learning WITH AI, not copying FROM AI

Welcome to Station 6! I wondered—if AI can write code, why am I learning this at all? I could ask it to build my whole Robot ID Card!

So I tried it. I asked an AI to "fix my code" without understanding what was wrong. It fixed it. Beautiful! I shipped it. But the next time I hit a similar problem, I was just as lost. I hadn't learned anything—I'd just outsourced thinking.

Prof. Teeters sat me down. "HAP, AI is a study partner, not a substitute for your brain. Use it to understand, not to avoid understanding. Ask it 'why does this work?' not just 'make this work.'"

That changed everything. Let me show you how to use AI as a learning tool, not a crutch... 🟠

🔬 Try it yourself: Robot ID Card →

What You'll Learn

🎓 AI for Understanding

Learn, don't copy

AI explains concepts. When I stopped asking AI to "fix my code" and started asking "why does this happen?", I actually learned. The difference is huge—understanding sticks, but copied code evaporates.

🔍 Better Questions

Context matters

Show your work. Vague questions get vague answers. When I include what I expected, what I got, and what I tried, AI can actually help me understand the gap in my knowledge.

Verify Everything

You own the code

AI makes mistakes. Even when AI explains something, I verify it against what I learned in Stations 1-5. If I can't explain why the answer works, I don't really understand it yet.

HAP surrounded by tangled code with an 'oops' expression

HAP's Confession: I Outsourced My Brain

I asked AI to "fix my code" without understanding the problem. It fixed it. I felt smart for about ten minutes.

Then I hit a similar problem. I was completely lost again. I hadn't learned anything—I'd just borrowed someone else's thinking.

Prof. Teeters helped me see: working code isn't the goal. Understanding is the goal. Now I ask AI to explain, not to fix.

What AI Can and Can't Do for Learning

I had unrealistic expectations about AI. I thought it would be like having Prof. Teeters available 24/7. It's not—but it CAN be a useful study partner when you know its strengths and weaknesses.

AI Excels At

  • Explaining error messages: It can decode cryptic errors into plain English
  • Showing examples: It can demonstrate concepts with multiple examples
  • Answering "why" questions: It can explain the reasoning behind rules
  • Suggesting what to try: It can offer debugging approaches
  • Defining terms: It can clarify vocabulary you don't know
  • Patience: It never gets tired of re-explaining things

AI Struggles With

  • Your specific context: It doesn't know your project or goals
  • What you already know: It can't gauge your level without you telling it
  • Being consistently correct: It sometimes gives confident wrong answers
  • Knowing what you need to learn: Only you know your knowledge gaps
  • Teaching the "feel" of coding: Experience comes from doing, not reading
  • Replacing actual practice: Understanding isn't the same as skill

🟠 HAP's Realization

AI is like a very patient tutor who knows a lot but doesn't know YOU. It can explain anything—but it can't learn FOR you. The understanding has to happen in your head, not in the AI's response.

The Art of Asking Good Questions

The quality of AI's help depends entirely on how you ask. Vague questions get vague answers. Specific questions get useful learning.

❌ Vague Prompt (What I Used to Do)

Bad question:
"Fix my code"

Why this fails:

  • AI doesn't know what "fix" means to you
  • AI doesn't know what behavior you expected
  • AI will guess, and you won't learn anything
  • You'll get code that works but you won't know why

✅ Good Prompt (What I Do Now)

Better question:
I'm learning JavaScript and my code isn't working as expected.

Here's what I wrote:
const score = "5";
const bonus = 10;
console.log(score + bonus);

I expected: 15 (addition)
I got: "510" (they got combined as text)

Can you explain what I'm misunderstanding about how + works?

Why this works: I showed what I wrote, what I expected, what I got, and asked for understanding—not just a fix.

Using AI to Understand Errors

Error messages are confusing at first. AI can translate them into plain English—if you ask the right way.

A Good Error-Understanding Prompt

Asking about an error:
I'm getting this error and don't understand it:

Error: "Uncaught TypeError: Cannot read properties of undefined"

Here's my code:
const robot = {};
console.log(robot.name.length);

What does this error mean, and why is it happening?

Notice: I'm not asking AI to fix it. I'm asking AI to help me understand it. Once I understand, I can fix it myself!

Include the Error

Copy the exact error message. Don't paraphrase—details matter.

Include Your Code

Show the code that caused the error. Context is everything.

Ask "What" and "Why"

What does this error mean? Why is it happening?

Then Try to Fix It Yourself

Once you understand, attempt the fix. That's how learning happens!

Learning Concepts with AI

When you don't understand WHY something works, AI can explain the concept— but you need to ask for understanding, not just answers.

Asking "Why" Questions

Asking for conceptual understanding:
I'm learning about variables in JavaScript.

This code works:
let energyLevel = 100;
energyLevel = 85;

But this code gives an error:
const robotName = "HAP";
robotName = "HyBit";

Can you explain WHY const behaves differently from let?
I want to understand the concept, not just memorize the rule.

The key phrase: "I want to understand the concept, not just memorize the rule." This tells AI what kind of help you need.

Understanding Code That Works

When code works but you don't know why:
This code works, but I don't understand WHY:

const greeting = `Hello, ${robotName}!`;

Why do backticks work differently than regular quotes?
What is the ${} doing? I want to understand the concept.

Working code you don't understand is technical debt. Ask AI to explain it until you could teach it to someone else.

HAP having a breakthrough moment

Breakthrough Moment!

Now I use AI differently. When I'm stuck, I describe what I think should happen and what's actually happening. The conversation helps me learn. The goal isn't working code—it's understanding why it works!

Verifying AI Responses

AI sometimes gives confident-sounding wrong answers. You MUST verify what it tells you against what you've learned.

Test the Code

If AI suggests code, run it! Does it actually work? Does it produce the results you expected?

Check Against Your Notes

Does AI's explanation match what you learned in Stations 1-5? If not, investigate the difference.

Try to Explain It

Can you explain AI's answer in your own words? If not, you don't really understand it yet.

Ask Follow-Up Questions

If something doesn't make sense, ask AI to clarify. Keep asking until you truly understand.

⚠️ AI Can Be Wrong

I once asked AI about semicolons and it gave me advice that contradicted what Grace Hopper taught me. AI was wrong! Always verify against trusted sources—your course materials, documentation, and what you've tested yourself.

Try It Yourself: AI Study Partner Challenge

Practice using AI as a study partner with this challenge:

🎯 The Challenge

You have this code that isn't working:

const userName = "HAP";
let greeting = "Hello, " + userName + "!";
console.log(Greeting);  // Error!

Your Mission:

  1. DON'T ask AI to fix it. That's the old way!
  2. Run the code and see the error message.
  3. Ask AI to explain what the error means and why it's happening.
  4. Try to fix it yourself based on what you learned.
  5. Verify your understanding by explaining why your fix works.

Bonus: After fixing it, ask AI how you could write the greeting using template literals (from Station 4) instead of concatenation.

HAP's Rules for Working with AI

After learning the hard way, I developed these rules. Prof. Teeters approved them!

1

Ask for understanding, not fixes

Instead of "fix my code," ask "why isn't this working?" or "what am I misunderstanding?" You learn from understanding, not from copying.

2

Show your work

Include your code, what you expected, and what you got. Good context leads to good help. Vague questions get vague answers.

3

Verify everything

AI makes mistakes. Test every suggestion. Check against your course materials. If you can't explain why something works, you don't understand it yet.

4

Try first, ask second

Struggle a bit before asking AI. The struggle is where learning happens! Use AI to get unstuck, not to skip the hard parts.

5

Ask "why" not just "what"

Understanding WHY code works is more valuable than knowing WHAT code works. Always dig deeper than the surface answer.

6

You own the code

Whether you wrote it or AI suggested it, YOU are responsible for it. Don't use code you don't understand.

Better Prompt Patterns

Here are templates for common learning situations:

Instead of "Fix my code"

"I expected X but got Y. Here's my code. What am I misunderstanding?"

Instead of "Write code that..."

"I'm trying to do X. I wrote this code but it returns undefined. Can you explain why?"

Instead of copying the answer

"This solution works, but I don't understand why. Can you explain what each part does?"

When completely stuck

"I'm trying to [goal]. I've tried [approaches]. What concept am I missing?"

When NOT to Use AI

AI isn't always the right tool. Sometimes you need to struggle!

When You Haven't Tried Yet

Struggle first. The productive confusion of trying and failing is where real learning happens. Don't skip it!

When Taking Assessments

That's cheating. Assessments measure YOUR understanding. Using AI defeats the purpose and leaves you unprepared.

When Building Muscle Memory

Practice makes permanent. Typing code yourself—even simple code— builds skills that reading AI answers never will.

🟠 Prof. Teeters' Warning

"Using AI to avoid thinking is like using a calculator before you understand multiplication. You'll get answers, but you won't understand math. And when the calculator isn't available, you'll be helpless."

She told me this after I admitted to copying AI code without understanding. I never made that mistake again.

Quick Reference: AI for JavaScript Learning

When is AI helpful for learning JavaScript? Here's a quick guide:

Explaining errors

Excellent

Include: exact error, your code, what you expected

Clarifying concepts

Excellent

Ask: "Why does X work this way? I want to understand the concept."

⚠️ Writing code for you

Risky

Better: Ask it to explain concepts, then write the code yourself

🛑 Replacing practice

Not recommended

Instead: Struggle, make mistakes, learn from them

Congratulations!

You've completed all six stations of HAP's JavaScript Foundations Lab!

What You've Learned

  • Setting up your coding workbench
  • JavaScript grammar (statements, semicolons, comments)
  • Variables with const and let
  • Data types (strings, numbers, booleans)
  • Operators for math and comparisons
  • Using AI as a study partner

What You Built

  • A mental model for how JavaScript works
  • The foundation for your Robot ID Card
  • Skills that transfer to any programming language
  • A healthy relationship with AI tools

🤖 Practice AI as a Study Partner

Use the Robot ID Card to practice what you learned in this station:

Try asking AI: "Can you explain how this code uses const vs let?" Practice asking for understanding, not just answers!

HAP celebrating completion of all stations

Prof. Teeters on Completing All Six Stations

"HAP, you've done something important here. You didn't just learn JavaScript syntax— you learned how to learn."

She smiled at my Robot ID Card displaying in the browser. "Every expert was once a beginner who didn't give up. You've built a foundation. Now build on it."

"The best code you'll ever write is the code you understand completely. Keep asking 'why.' Keep experimenting. Keep breaking things and fixing them. That's how every programmer grows." 🟠