Vibe coding is fun until it isn't.
You're flying through features. AI is writing everything. It feels like a superpower.
Then you hit the context limit.
The model forgets what it built. Starts contradicting itself. Code breaks in ways that make no sense. And suddenly you're spending more time fixing AI mistakes than you would have spent just writing it yourself.
I've been there.
The problem isn't vibe coding itself. The problem is depending on it completely.
If you don't understand what the code is doing you can't fix it when the AI loses the plot. And it will lose the plot.
Use it as a tool. Not a replacement for thinking.
Let AI handle the boilerplate. You handle the logic. You review every line. You stay in control.
The engineers who will win with AI are not the ones who prompt the best. They're the ones who know enough to catch when the AI is wrong.
Don't outsource your understanding. That's the one thing AI can't give back to you.
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (0)