Comment by Grimburger
6 days ago
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.
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.
Anecdotal.
13 million swe roles with .01% is 130,000 compromised devices.
Process problem
I think that the numerical example you gave appears to be wrong unless you intended 1% rather than 0.01%.
In any case, fair enough. The concern is that organizations will build processes around AI where many people do not review outputs carefully. I do not disagree with this.
I also agree that my particular workflow is anecdotal and does not work at scale.
2 replies →