Trying to make AI do what you want just with instructions didn't work for me. In a new system I am designing, I've implemented a set of algorithmic checks to make sure that every to-do affects only the area it needs to and does not create deltas which are unintended. I developed a system of fingerprinting pieces of code to not do the checks every time as well for performance reasons. It's working great so far and I'm building more and more layers of algorithmic checks and the model is beginning to work extremely well with it. I am now able to fill out a limited to-do list and be absolutely certain that only the pieces that I wanted were changed and nothing was broken. Maybe it's nothing new for most of you, but it added so much more confidence in my results in this new system, which will be a hundred percent AI generated. I was very tired with the old way of doing this by relying only on a set of loops and instructions. In it was never giving me this feeling of confidence that I have in this new system I'm developing. I could write about it if there is interest
Do you have any more details about this or maybe a repo? I feel like I'm running into the same issues, especially with agents wanting to run insane amounts of test s and check and measuring for every little change.
We're staring down the vulnpocalypse we predicted earlier this year. What matters now is how fast you can react to it. Trail of Bits has developed these capabilities to dramatically increase how fast fixes can go out.
Coordinated disclosure serves little purpose now. It used to require effort to go from vulnerability to exploit, but now we have nearly unlimited, capable expertise on tap with AI. As a product owner, you need to ramp your dev speed to make patches instantaneously after external reports.
Please use our patching-bugs and regression-hunt skills to ship fixes faster!
> What matters now is how fast you can react to it.
You can't turn a vulnerable piece of software into a secure one by just fixing the vulnerabilities as they are discovered. That didn't change when vulnerabilities get discovered more quickly.
I agree with that, but these are two parts of a whole. Even software with reduced attack surface needs the ability to react quickly to discovered issues.
Trying to make AI do what you want just with instructions didn't work for me. In a new system I am designing, I've implemented a set of algorithmic checks to make sure that every to-do affects only the area it needs to and does not create deltas which are unintended. I developed a system of fingerprinting pieces of code to not do the checks every time as well for performance reasons. It's working great so far and I'm building more and more layers of algorithmic checks and the model is beginning to work extremely well with it. I am now able to fill out a limited to-do list and be absolutely certain that only the pieces that I wanted were changed and nothing was broken. Maybe it's nothing new for most of you, but it added so much more confidence in my results in this new system, which will be a hundred percent AI generated. I was very tired with the old way of doing this by relying only on a set of loops and instructions. In it was never giving me this feeling of confidence that I have in this new system I'm developing. I could write about it if there is interest
Do you have any more details about this or maybe a repo? I feel like I'm running into the same issues, especially with agents wanting to run insane amounts of test s and check and measuring for every little change.
We're staring down the vulnpocalypse we predicted earlier this year. What matters now is how fast you can react to it. Trail of Bits has developed these capabilities to dramatically increase how fast fixes can go out.
Coordinated disclosure serves little purpose now. It used to require effort to go from vulnerability to exploit, but now we have nearly unlimited, capable expertise on tap with AI. As a product owner, you need to ramp your dev speed to make patches instantaneously after external reports.
Please use our patching-bugs and regression-hunt skills to ship fixes faster!
> What matters now is how fast you can react to it.
You can't turn a vulnerable piece of software into a secure one by just fixing the vulnerabilities as they are discovered. That didn't change when vulnerabilities get discovered more quickly.
I agree with that, but these are two parts of a whole. Even software with reduced attack surface needs the ability to react quickly to discovered issues.