Vibe coding can make programming feel almost effortless.
You have an idea, describe it to an AI coding assistant, and a few minutes later you have working code. You can ask for another feature, fix an error with a prompt, redesign a page, add an API and keep going.
It's incredibly useful.
But there is a question that many developers eventually start asking:
"How much of my coding ability now depends on AI?"
This vibe coding test is designed to help you find out.
Take the full 25-question test →
Before You Start
This isn't a test of whether you are a "good" or "bad" programmer.
It doesn't measure how many lines of code you write or how many hours you spend using AI.
Instead, it looks at something more useful:
How much control do you still have over your own development process?
For each statement, choose:
- Never — 0 points
- Rarely — 1 point
- Sometimes — 2 points
- Often — 3 points
- Almost always — 4 points
The Vibe Coding Test
1. I ask an AI coding tool for a solution before trying to solve the problem myself.
2. I use AI even for programming tasks I already know how to do.
3. I find it difficult to start coding without an AI assistant.
4. I regularly use code that I don't fully understand.
5. When something breaks, my first reaction is to ask AI to fix it.
6. I rely on AI to decide how I should implement features.
7. I have become less interested in learning programming fundamentals.
8. I would struggle to continue working if my preferred AI coding tool stopped working.
9. I spend more time prompting AI than reviewing what it produces.
10. I sometimes feel that AI is doing the actual programming while I'm simply directing it.
Your Score
Add your points.
0–10: Independent
You appear to use AI primarily as a tool rather than as a necessity.
You may still use it extensively, but you haven't given up your ability to reason through programming problems yourself.
11–20: AI-Assisted
AI has become an important part of your workflow.
That's not necessarily a problem. You may simply have found a highly productive way of working.
Still, occasional AI-free practice is a good idea.
21–30: Highly AI-Dependent
AI appears to be involved in many stages of your development process.
Consider deliberately handling some tasks yourself—particularly debugging, architecture and small implementation problems.
31–40: Strong AI Reliance
Your workflow may have become heavily dependent on AI.
The most useful next step isn't necessarily to stop using it. Instead, identify the skills you now routinely outsource and start practicing those independently.
The One Question Your Score Can't Answer
There is a simple experiment that can tell you something a questionnaire can't.
Turn off your AI coding assistant.
Choose a small programming task.
Give yourself an hour.
Can you make progress?
You might be slower. You might need documentation. You might make mistakes.
That's completely normal.
The important thing is whether you can still think your way through the problem.
What Healthy Vibe Coding Looks Like
A healthy workflow might look like this:
You define the problem → AI suggests an implementation → you inspect it → you test it → you make the final decisions.
A problematic workflow looks more like:
Problem → prompt → copy → error → prompt → copy → repeat.
In the second scenario, the application may work, but the developer can gradually lose visibility into how it works.
How to Keep Your Skills Sharp
You don't have to give up vibe coding.
Try three simple rules.
Think before prompting
Spend a few minutes forming your own solution before asking AI.
Understand important code
You don't need to understand every generated line, but you should understand authentication, data handling, APIs, architecture and other critical parts.
Keep some AI-free practice
Build small things manually.
Debug without assistance.
Read documentation yourself.
These activities keep your programming skills active.
Final Result
A high score doesn't mean you're "bad at programming."
It simply means AI has become deeply integrated into the way you solve programming problems.
The real goal isn't to become independent of AI.
It's to remain capable with or without it.