upvote
No, it's not a given. AI always finds security issues in the things I just had it write.
reply
But that should be part of your pipeline, no? Personally, the thing I've spent the most time working on with AI is.. a stack to get AI to keep a project on track and follow strict code writing standards that are reviewed. Not everyone is working in that, but I'm sure any serious development will be done via something similar.

Although, at the pace of improvement, I'd bet it won't even be necessary in a year or so.

reply
This is true for human written code too. This is why in the future all written code MUST be run through an internal security sweep before being given to your harness for writing. That's just basic due diligence at this point.
reply
As long as model providers deny access to security-capable models, it can't be basic diligence.
reply
This is something agents already do as part of their normal work. Providing code that you know is vulnerable is in fact a dereliction of duty and negligence. Don't provide a POC. Simply that as it produces code a background agent just checks it without showing the work and points out potential problems.
reply
The slop is cheap but checking will cost extra, what a pricing scheme! Modern day Pharo level of lockin!
reply
Yes but LLMs famously produce vastly more code than humans. My hot take: LLMs will produce more insecure code than they can catch, and will also find ways to smuggle insecure code to avoid extra work.
reply