Using AI to Become a Better Developer (A Promise to Myself)

Alright, let's be honest. I ask Claude for code. I read maybe three lines of it. I think "yeah that looks right" and paste it into my editor or just accept it in to my repo. Quick test. Ship it. Move on.

That's my current workflow. Sloppy but honest.

And it works. Most of the time. Which is the exact problem.

When something works, there's no incentive to understand it. No incentive to question it. No incentive to actually learn anything from it. I'm not becoming a better developer. I'm becoming faster at not thinking.

This ends next week.

Why This Matters

I've got enough experience that I can get away with this for a while. But I can feel it. The edges are getting blurry. There's code in repos I've written that I couldn't explain to someone else. Not because it's complex. Because I never actually understood it in the first place.

That's not sustainable. That's not how you stay sharp.

The difference between using AI as a tool and using AI as a crutch is simple. It's the difference between asking "why" and just accepting.

When I stop asking why, I stop learning. And when I stop learning, I stop being useful.

So next week, that changes. I'm going to Claude with a different mindset. Not "give me the answer." But "help me understand this."

How I'm Going to Use It Differently

Instead of copy, paste, ship, I'm going to actually engage with it. When Claude gives me something, I'm going to ask myself better questions.

Why did it choose this approach? What's the alternative? What could go wrong here? Is there a trade-off I'm missing?

Sometimes Claude's right and I'll learn why. Sometimes it's half-right and I'll learn how to adapt it. Sometimes it's confidently wrong and I'll learn more from fixing it than if it had been perfect.

The key thing is that I'm actually thinking now. Claude's the rubber duck that talks back.

What changes:

I stop asking for solutions. I start asking for explanations.

I stop reading three lines. I read it all and actually process it.

I stop shipping immediately. I challenge the output. Play devil's advocate with the code.

I use it to learn new patterns, not to skip learning patterns I should already know.

I ask "why this way" instead of just accepting "here's a way."

The Challenge to You

If you're doing what I'm doing right now, I get it. It's faster. But you're missing out on actually learning anything.

Start next week. Change one habit. When you get an answer from AI, before you do anything else, ask it why it chose that approach. Make it explain its reasoning. Make it justify it.

You'll be surprised how often that extra five minutes of questioning reveals something you didn't know.

The Prompts That Actually Work

These are the ones I'm going to use. Steal them if they help.

Stop saying: "Write me a function that does X"

Start saying: "Show me how to [specific task]. Walk me through why you'd approach it this way instead of [alternative approach]."

Forces them to explain the thinking, not just dump code.

Stop saying: "Fix this code"

Start saying: "This code does X but I think there's a better way. What are the trade-offs between my current approach and alternatives? Which would you recommend and why?"

Now you get the reasoning behind the fix, not just a quick patch.

Stop saying: "How do I do X"

Start saying: "I need to [outcome]. What are the three most common approaches? What's the trade-off between them? What would you pick for [your specific context] and why?"

Forces options and reasoning, not just one answer.

Stop saying: "Write me some code"

Start saying: "I'm trying to solve [problem]. Before you write code, help me understand the concepts and patterns I should know about. Then show me how they apply here."

Learn the foundation first. The code comes after.

And always follow up with:

"I don't understand why you chose this. Explain it like I've never seen this pattern before. What could break? What are the limitations?"

Push back. Ask the hard questions. Don't accept the first answer.

Actually Doing This

The developers getting real value from AI aren't the ones who use it to skip thinking. They're using it to think better.

So next week. That's when I start. I'm going to use Claude to learn, not just to ship. I'm going to ask why instead of just accepting the answer.

And maybe you should too.

We'll see how this goes.