undefined | Better HN

0 points_pdp_17d ago0 comments

You can vibe code safely for sure.

I am not saying vibe coding is the issue. The issue is that a typical developer might be working on a lot more projects that run concurrently then they used to. And because of the various nature of the project the risk is significantly increased.

Scale this across the workforce and you not just doubled the problem.

0 comments

4 comments · 2 top-level

Grimburger17d ago· 2 in thread

You can vibecode docs and tests also but I'm truly not seeing more of those.

In the end it can just be a culture thing. A dev who was going to write docs and tests before is going to have a LLM generate docs and tests today. Same with safe practices and defensive coding. The machine does whatever you want from it, for most that's "just get the job done I don't care". So that's the output.

johnisgood17d ago

If I vibe code a project, that involves docs and tests as well. Obviously I do not, at any point, do anything blindly and there are some iterations for everything. I always double-check, and I do not use "agents", I do everything manually. I always check what the LLM is thinking, in real-time. I might be old school, but that allows me to write code that is not a pile of shit. :P I am still conscious about quality.

whattheheckheck17d ago

Anecdotal.

13 million swe roles with .01% is 130,000 compromised devices.

Process problem

1 more reply

xeonmc17d ago

"Practice safe vibecoding, stop the cycle of infections!"

j / k navigate · click thread line to collapse