I have to say that I'm not a crowd follower, that's the case for almost everything in my life, I hate feeling like part of the "herd", and yes, I'm talking about the vibe coding thing. I am very skeptic about new technology when they first come out, and try to 'wait a -secure- time' before joining it. That's the case with this AI revolution, it's not about the fear of changing, as you probably are thinking right now, it is much simpler than that.
Look!
I got very excited easily when it comes to technology, I love innovation, I'd love to be the one innovating, actually, is one of my biggest dreams, it is. But, when it comes to work, I prefer to give stability, instead of innovation, I prefer delivering trustiness instead of novelty, so, in order to give my clients that good product they expect from me, I tend to fall a little bit behind, unless the client, want me to go for the latest tech/version available for any of the tools I use, so, that's simply my case, I love to be 'aware' of the cutting edge, but, working just behind enough to give my clients a sense of reliability in the software I deliver.
So, to move forward, I'll start this short story like this:
Last week I started 'seriously' trying vibe coding with Google AI Studio, obviously with Gemini 2.5 pro to see how it feels like.
My experience is that, it is blazing fast, I mean, it will scaffold an app in just a few minutes, and that, bro, that sounds amazing.
But...
I actually take it to the limit asking for things, because, obviously, it just added mock databases to the project until you explicitly asked for it to use a real database, and won't create the full app with just one prompt, forget that stupidity, not even senior humans will do that. It created stupid issues maybe even a junior can easily handle, but it couldn't, literally, I watched it fail the same little task (like properly configuring a firebase rules file) and asking me to review, even though the issue was still there.
Yes, sir, the first thing I thought was "Dang! I'll have to resolve this by myself, because it won't be able to", and, well, as you might expect, I, indeed, had to do it.
The thing is that, after a 'successful' development session, literally two days to build an MVP for a product I had in my mind for years, I know, for sure, a non-developer, normal person, won't be able to have a reasonable result with vibe coding, it's a powerful tool to boost your 'productivity' (yes, in quotes, because, at some point you will get totally disconnected from the project, so you'll need to explore a huge portion of the codebase just to understand how something works or how to properly add a feature or make a fix by yourself) at expenses of both the development of your problem-solving skills (that single little thing that makes this interesting) and the joy of writing code and seeing come to life.
Obviously, I'm not, like, against it, I just say, most hypers (new word invented by me) try to sell it as the solution for no coders to create apps, but, I say, It isn't so, it is a tremendous, advantageous tool for us, coders.
Bye!
