AI isn't making me a better coder. The way I use AI is.

Lately, I've been thinking about how AI is changing the way we learn software development.

Many developers worry that relying on AI will weaken problem-solving skills. That's a valid concern, especially if AI is doing all the thinking for us.

Personally, I've taken a different approach.

When I'm learning TypeScript, Playwright, or other development concepts, I still write the code myself. I don't rely heavily on autocomplete or ask AI to generate entire solutions.

Instead, I use AI for things like:
✅ Debugging errors I don't understand
✅ Learning how built-in methods work
✅ Exploring different approaches to a problem
✅ Reviewing my code and explaining improvements
✅ Accelerating documentation searches

The goal isn't to get the answer as quickly as possible.

The goal is to understand why the answer works.

I've found that writing code manually forces me to think through the logic, make mistakes, and learn from them. AI then becomes more like a mentor or rubber duck than a code generator.

It's similar to using a calculator while learning math:

• If it solves every problem for you, you don't learn much.
• If it helps you understand concepts and verify your thinking, it becomes a powerful learning tool.

I believe the engineers who thrive in the AI era won't be the ones who avoid AI entirely.

They'll be the ones who can still think independently while using AI to learn faster.

For me, AI is a bicycle, not a taxi.

🚲

It helps me move faster, but I'm still the one doing the pedaling.

How are you using AI in your learning journey?

#softwaredevelopment #ai #typescript #playwright #qualityassurance #automationtesting #learning #programming #webdevelopment #developergrowth | Jessie Caminos

AI isn't making me a better coder. The way I use AI is. Lately, I've been thinking about how AI is changing the way we learn software development. Many developers worry that relying on AI will weaken problem-solving skills. That's a valid concern, especially if AI is doing all the thinking for us. Personally, I've taken a different approach. When I'm learning TypeScript, Playwright, or other development concepts, I still write the code myself. I don't rely heavily on autocomplete or ask AI to generate entire solutions. Instead, I use AI for things like: ✅ Debugging errors I don't understand ✅ Learning how built-in methods work ✅ Exploring different approaches to a problem ✅ Reviewing my code and explaining improvements ✅ Accelerating documentation searches The goal isn't to get the answer as quickly as possible. The goal is to understand why the answer works. I've found that writing code manually forces me to think through the logic, make mistakes, and learn from them. AI then becomes more like a mentor or rubber duck than a code generator. It's similar to using a calculator while learning math: 🟢 If it solves every problem for you, you don't learn much. 🟢If it helps you understand concepts and verify your thinking, it becomes a powerful learning tool. I believe the engineers who thrive in the AI era won't be the ones who avoid AI entirely. They'll be the ones who can still think independently while using AI to learn faster. For me, AI is a bicycle, not a taxi. 🚲 It helps me move faster, but I'm still the one doing the pedaling. How are you using AI in your learning journey? #SoftwareDevelopment #AI #TypeScript #Playwright #QualityAssurance #AutomationTesting #Learning #Programming #WebDevelopment #DeveloperGrowth

linkedin.com