[dudefeliciano]

> Vibe-coders might not visit this forum for example and might not be aware of a security exploit that must be fixed asap.

This is true of "regular" coders too, i've worked with/for extremely experienced programmers who, while knowing the security risks, implemented (or even worse, asked me to implement) flakey authentication systems, exposed databases, etc. I don't think this is an AI issue, it's a "care about your users" issue.

> is only going to increase the demand for professional services

Then shouldn't we be happy that more people are embracing vibe coding?

[Aurornis]

> Then shouldn't we be happy that more people are embracing vibe coding?

I don’t know about you, but I’m not looking forward to reverse engineering and maintaining someone else’s vibe coded mess.

It’s like when someone makes a quick and dirty proof of concept to impress management and then hands it off to another team to make it usable in production. They did 20% of the work but took 80% of the credit. Now you have to to the remaining 80% of the work to make it into what it needs to be, but management is only going to be disappointed because you’re moving so slowly relative to the proof of concept creator.

[itishappy]

I am! I've always enjoyed tutoring junior coders. I'm not that advanced either, and I tend to focus more on the conceptual than practical side of things, so it gives me an excellent lever to improve myself as well.

[wakawaka28]

There's a big difference between someone knowing about security and taking a calculated risk, and someone who understands neither the risks nor the semantics of code handed to them. There are also legal issues. Even in the most optimistic cases, I think we're 50 years away from this making sense for most software.