Vibe Coding

I grew up coding by actually typing code - I know, I'm a psycho.

It's weird because a lot of people now are coding with AI agents, and sometimes they aren't even writing a single line of code, simply asking the agent to make everything from scratch. Again, there's no problem with this. People should be able to use these agents as tools to help them learn coding with no background. The workforce is becoming more and more tricky now, though. How can we actually tell if someone can code if all they do is ⌘C, ⌘V?

I know how to code. I remember when I had to build a project for OOD and actually debug my code by stepping through it and looking at the values, trying to see what wasn't working. I remember this feeling - the feeling of architecting something from scratch.

The funny thing with vibe coding is that it's kind of just brain rot. I've done it - I'm just on my bed watching some Death Note and accepting all the Copilot suggestions without even coding. Are you even a programmer at this point? I mean, it's fun once in a while, but can you really say you are a coder?

An argument for using agents or vibe coding is efficiency. Apparently, these agents are faster and develop cleaner code than us, which could be true. But as much as I hate using this term, "prompt engineering" actually comes into play.

See, when you understand computer science architecture, you can develop OOP projects by giving the agent as many specifications as possible, making your life easier, more tailored, and better. Just saying "make a chatbot for me" might work, but it will try to emphasize functionality over scalability, which is not a feasible solution for coding, especially in the long term or when working at FAANG companies with a large codebase.

Vibe coding might be the future, but it's kind of scary to think about.