Are you actually coding or just vibing?

The idea of vibe coding (coined by Andrej Karpathy) might seem new—copying and pasting code from LLMs until it works and being too lazy to understand it all.

But I believe vibe coding has always existed—at least since Google became a thing. Before LLMs, our main destinations were Stack Overflow and Google: just copy the error, paste it, and try all the solutions until one worked.

Back then too, 90% of the time, if it worked, we didn’t bother understanding why. But LLMs have taken this to another level—with the answer now just one query away.

Programmers are becoming lazier than ever, skipping the logic behind the code. (Trust me, I’m one of them.) I strongly believe vibe coding is okay only when you're completely non-technical or just really, really tired of trying to understand the logic.

It is especially dangerous when you are learning how to code or working on a production-grade system.

The vibe coding culture is like short-form content (Reels & TikTok)—it’s addicting and doesn’t require much thinking.

In conclusion: The very thing that makes coding fun is solving hard problems—including the errors and bugs that challenge you.

In the end, the choice is ours to make.