I was applying for jobs. Sending CVs left and right, hoping someone would give me a chance. Then one day, a recruiter actually replied.
I thought it was my moment.
Then came the question.
"Did You Actually Write This Code?"
They had looked at my GitHub. Clean projects, working features. I was proud of them.
But they asked directly —
"Some of this looks very polished. Did you write it yourself?"
I told the truth. I had followed YouTube tutorials and used AI coding tools to help.
The conversation ended shortly after.
That Night
It wasn't just the rejection. It was the question that kept replaying.
"Did I actually write that code?
The honest answer was complicated. I knew the basics — variables, functions, loops. But applying them on my own, without a tutorial guiding me or AI filling the gaps? I couldn't.
I looked at my own GitHub and thought: if someone asked me to explain why I wrote this, what would I say?
Silence.
It wasn't that I knew nothing. I knew things — I just didn't know how to use them. Like having tools in a box but not knowing when to pick them up.
The Search
I went looking that night. Forums, Reddit, YouTube comments. And I found them — developers who felt the exact same thing. People who had shipped projects held together by Stack Overflow and AI suggestions, feeling hollow about it.
That helped. But I didn't just want to feel less alone. I wanted to actually know something.
What Changed
I stopped trying to memorize code and started trying to understand the process.
Instead of "what do I type here?" I started asking "why does this work?" I broke things on purpose. I read documentation. I wrote slowly and made sure I could explain every line before moving on.
I didn't stop using AI tools — I changed how I used them. Less "write this for me." More "explain why this works."
But Isn't Vibe Coding a Thing Now?
Fair question. AI is writing code, shipping features, building entire apps. Do fundamentals even matter anymore?
I think they matter more than ever.
AI is a tool. And when something breaks — it will break — you need to understand enough to know why. If you can't read the code AI writes, you can't review it, debug it, or fix it. You're just hoping it works.
There's a difference between a developer who uses AI to move faster, and someone who uses AI because they have no idea what's happening. One can ship fast and fix fast. The other is just waiting for things to fall apart.
If you know the basics but feel unsure how to apply them — you're not behind. You're just missing the bridge between knowledge and application.
That bridge isn't built by more tutorials. It's built by slowing down and thinking.
The recruiter's question stung. But it was the most useful thing anyone asked me. It showed me the gap between what I knew and what I could actually do — and made me close it.
I'm still learning. But now I write code I can explain.
That feels like something real.
Have you felt this way? Drop it in the comments — you're probably not alone.
Top comments (0)