Vibe Coding Is Making Us Worse Developers

Last week, I needed to write a function.

A simple one. Filter an array, map over the results, return the clean data. Basic stuff. Stuff I've written a hundred times.

I opened Cursor. Typed my prompt. AI wrote the code in 3 seconds. I copied it. It worked. I closed the file.

Then a junior developer tapped me on the shoulder.

"Hey, can you explain how this works?"

I stared at the screen. My mouth opened.

Nothing came out.

I had generated the code. But I didn't understand it. Not really. I had outsourced not just the typing — but the thinking.

That's when it hit me. I'm not coding anymore. I'm "vibe coding." And it's making me worse at my job.

What Even Is Vibe Coding?

Vibe coding is what happens when you stop thinking and start prompting.

You have a problem. You type it into AI. You get code. You paste it. It works (mostly). You move on.

You don't ask:

• Why does this work?
• Are there edge cases I'm missing?
• Is this actually efficient?
• Could I have written this better?

You just... vibe.

It feels productive. You're shipping faster. Tickets are closing. Your manager is happy. You feel like a 10x developer.

But here's what's actually happening: you're not learning. You're outsourcing your brain.

The AI is getting smarter every month. And you? You might be getting dumber. Slowly. Quietly. Without noticing.

The Skills I've Lost in One Year

This is the part I'm embarrassed to admit.

1. Problem decomposition.
I used to look at a complex problem and break it into small, logical steps. It was satisfying — like untangling a knot. Now I just describe the whole problem to AI and let it figure out the steps. My brain doesn't practice splitting anymore. It's gotten lazy.

2. Syntax recall.
I used to know array methods cold. .map, .filter, .reduce — I could write them without thinking. Now I pause. I second-guess myself. The muscle memory is fading because I never practice it anymore.

3. Debugging from first principles.
This one hurts the most. When AI-generated code breaks, I don't know where to start. I didn't write it. I don't fully understand it. So instead of debugging — I re-prompt. And hope the next version works.

4. Confidence.
The worst one. I used to trust myself to solve problems. Now I reach for Cursor before I've even thought about the problem for 30 seconds. And when AI isn't available — I freeze.

These aren't random nice-to-have skills. They're the fundamentals. The things you need when things go wrong. And they're fading.

The Moment I Couldn't Hide It Anymore

Last month, I was in a technical interview.

No AI. No Cursor. No Copilot. Just me, a shared screen, and a problem I'd absolutely solved before.

The problem wasn't hard. I should have knocked it out in 10 minutes.

I froze.

My brain literally reached for Cursor. I caught myself mid-thought: "I'll just prompt this real quick—" But there was no prompt box. There was no AI. Just me and a blinking cursor.

I solved it. Eventually. But it took 45 minutes. I stumbled through it. I second-guessed every line.

The interviewer didn't say anything. They were polite. But I knew.

I wasn't the developer I used to be. And it was my own fault.

But I Ship Faster! — I Know. I've Said It Too.

I know what you're thinking. Because I've thought it too — every time I felt a flicker of guilt about copy-pasting AI code.

"But I ship faster. I close more tickets. My velocity is through the roof. Isn't that what actually matters?"

Yes. Speed matters. Shipping matters. Delivery matters.

But here's the question nobody is asking out loud: what happens when the AI isn't there?

When the API goes down? When you need to debug something in a part of the codebase AI can't fully see? When you're whiteboarding with your team and someone asks you to just think through a problem? When you're in an interview?

And here's the darker truth: the code you're shipping today with AI is code you'll have to debug tomorrow — without fully understanding it. That's not velocity. That's debt.

Vibe coding feels efficient. But it's borrowing speed from your future self. And the interest rate is your skill.

What I'm Actually Doing Differently Now

I'm not quitting AI. That would be stupid. AI is a genuinely useful tool and I'm not going to pretend otherwise.

But I'm changing how I use it:

1. I write the first draft myself.
No AI until I've genuinely tried. Even if it's slow. Even if what I write is wrong. The attempt is the point.

2. I explain every line AI writes — out loud.
If I can't explain what a piece of AI-generated code does, line by line, I don't ship it. Simple rule. Hard to follow. Worth it.

3. No AI for fundamentals.
Loops, conditionals, basic array methods, simple data transformations — I do those by hand. Every time. To keep the muscle memory alive.

4. One hour of "no AI" coding every day.
Just me and the problem. No Cursor. No Copilot. It's humbling. Some days it's painfully slow. But it's the only thing that's actually making me better again.

5. One question at the end of each day:
"Did I actually learn something today — or did I just generate?"

I still relapse. Some days I vibe code the entire afternoon and don't notice until I'm shutting my laptop. But I'm catching it more. And that's better than nothing.

The Truth Nobody Wants to Say Out Loud

AI isn't making you a 10x developer.

It might be making you a 0.1x developer who can write really good prompts.

The skill you're not practicing today is the skill you won't have tomorrow. And AI can't save you from that — because AI is the exact reason you stopped practicing in the first place.

Vibe coding is a trap. A comfortable, fast, ticket-closing trap. It feels like progress. It looks like productivity. But it's quietly hollowing out the fundamentals you spent years building.

Use AI. Seriously — use it. It's an incredible tool.

But use it like a calculator, not like a brain replacement. Because one day, the calculator won't be there. And you'll want to still be a developer.

Not just a really good prompter.

One Honest Question Before You Close This Tab

When was the last time you wrote code without AI?

Not fixed someone else's code. Not debugged with Copilot's help. Not refactored with a suggestion.

Wrote it. From scratch. With your brain.

If you had to think about it for more than 5 seconds — that's the answer.

I'll go first in the comments. Your turn. 🙌

Disclosure: I used AI to help structure and organize my thoughts — but every experience, feeling, and word in this article is my own.