🤖 How I Actually Use AI While Learning to Code

How I Actually Use AI While Learning to Code

When I started learning programming, I thought AI would mostly be useful for generating code.

I was wrong.

Now, while working on projects and learning new concepts, I use AI for much more than writing code.

I use ChatGPT and Claude as learning and debugging companions — but I've also learned that simply copying whatever AI gives me doesn't actually help me learn.

Here's what my experience has looked like.

💻 1. Sometimes I Use AI for "Vibe Coding"

I'll be honest — sometimes I don't know exactly how something should be implemented.

I have an idea of what I want, so I explain it to AI and ask it to help me build it.

That's probably what people now call vibe coding.

It can be incredibly useful when you're stuck at the beginning of something.

But there's a problem.

You can end up with code that works without actually understanding why it works.

And when something breaks later...

You're back to square one.

🐛 2. Errors Are Where I Use AI the Most

One of the biggest things I've learned while building projects is that writing code and debugging a real project are completely different experiences.

Sometimes I get an error and genuinely don't understand:

What caused it
Which file caused it
Whether it's a Python problem
Whether it's Flask
Whether it's the database
Whether it's deployment
Or whether I somehow broke something completely unrelated 😭

This is where AI has helped me a lot.

Instead of just asking:

"Fix this error."

I've started asking:

"Explain what this error means, why it is happening, and what I should check."

That difference matters.

Because fixing an error is useful.

Understanding the error is learning.

🧠 3. If I Don't Understand Something, I Learn the Concept

Another thing I frequently do is ask AI to explain concepts that I don't understand.

Sometimes I'll encounter something new while working on a project and realize:

"Wait... I don't even know what this is."

Instead of blindly continuing, I stop and learn the concept.

I've also discovered new tools and websites this way.

For example, while working on my projects, AI has helped me understand things like UptimeRobot, deployment-related concepts, and different tools that I didn't even know existed before.

It has basically become a way for me to discover:

"What else do I need to know to make this project work?"

🔧 4. AI Doesn't Always Get It Right

This is probably one of the most important lessons I've learned.

I've used AI-generated code many times.

And yes, sometimes it works perfectly.

But sometimes...

It creates another error. 😭

Then I have to go back and tell it what happened, show it the new error, and ask it to figure out what went wrong.

That's when I realized something:

AI is a tool, not a replacement for understanding.

If I don't understand my own project at all, I can easily get stuck in an endless cycle of:

AI gives code → code gives error → AI fixes it → another error → AI fixes that → repeat.

That's not really learning.

✍️ 5. I've Also Learned That My Prompt Matters

Earlier, I would sometimes write a huge prompt explaining everything I was thinking.

Now I'm trying to be much clearer.

Instead of overthinking the question, I try to explain:

What I'm trying to do → What happened → What I expected → What went wrong.

And then ask for a clear explanation.

For example:

"Explain this error in simple terms. Tell me what caused it, which part of my code is responsible, and what I should change."

That's much more useful to me than simply saying:

"Fix this."

🚨 The Biggest Lesson

Using AI while learning to code has changed the way I approach problems.

But it has also taught me something important:

Don't use AI to avoid learning. Use AI to learn faster.

If I don't understand something, I ask.

If I get an error, I investigate it.

If AI gives me unfamiliar code, I try to understand what it is doing.

And if I discover a new concept while building something, I learn that concept instead of blindly moving forward.

🌱 Where I Am Right Now

I'm still learning.

I still get confused.

I still get errors.

I still ask AI for help.

And sometimes I still have absolutely no idea why something stopped working. 😭

But I think that's part of the process.

I'm slowly learning that becoming a better developer isn't about never getting stuck.

It's about becoming better at figuring out why you're stuck.

And AI has become one of the tools I use to do that.

💭 One thing I'm trying to remember

Don't ask AI to do everything for you.

Ask it to help you understand what you're doing.

Because the goal isn't just to have working code.

The goal is to eventually understand the code you built.