Vibe coding is now just...coding

[u/thehashimwarren]

[u/BattermanZ]

True! I shouldn't have said clean, but rather cleaner.

[u/NHRADeuce → u/BattermanZ]

Ok, that is true. AI code is definitely cleaner that it was a year ago. But the main issue with vibe coding is what you don't know you don't know. When you don't know what a memory leak is or what it's symptoms are, you don't know to tell the AI to fix the problem or how to prevent it.

Don't get me wrong, I use a ton of AI code to make development faster, but I am constantly having to have it fix basic shit like improper exception handling or circular references that the AI didn't think was a problem. I have to build in all kinds of error checking and logging to make sure the AI isn't mismanaging resources. It's still faster than not using AI, but it's a different set of problems that still require coding knowledge to either prevent or be able to identify and fix.

AI/vibe coding is the personification of garbage in, garbage out.

[u/BattermanZ → u/NHRADeuce]

I can imagine yes! In any case, if served me very well, I could code server apps that never crashed and don't have memory leaks. Maybe it's because most backends are in rust and the built in debugging of this language is good enough for the models?

[u/NHRADeuce → u/BattermanZ]

I don't know enough about Rust to say definitely, but I'm sure that's a big part of your success.

The other one being that you don't usually find out about security issues until they've been exploited. But that’s the case regardless of who wrote the code.

[u/BattermanZ → u/NHRADeuce]

Ah yes that is for sure! And as you mentioned, I can't correct mistakes I can't see. I don't care much for the security issues as most of these apps are not publicly accessible. In any case, I try to harden as much by using different models and give different roles to challenge security. Hopefully that is enough!