4 ms·
You're countering vibes with vibes. If the tests aren't good enough, break them. Red team your own software. Exploit your systems. "Sitting with the code" is s
by CuriouslyC 9mo ago
You're countering vibes with vibes.
If the tests aren't good enough, break them. Red team your own software. Exploit your systems. "Sitting with the code" is some Henry David Thoreau bullshit, because it provides exactly 0 value to anyone else, whereas red teamed exploits are objective.
- kranner 9mo agoThe way you come up with ideas on how to break, red team and exploit; when to do this and how to stop: that part is not objective. The machine can't do this for you sufficiently well. There is a subjective process in there that you're not acknowledging. It's a good approach! It's just more 'negative space' than direct.
- CuriouslyC 9mo agoPeople who pentest spend more time running a playbook than puzzling over the logical problem of how to break a piece of software. Even a lot of zero days are more about knowing a pattern and mass scanning for it across a lot of code than playing chess vs a codebase and winning.
- kranner 9mo agoFine, but is that the entirely of software development? It even seems a waste of time by your own reasoning if it's so automatable already.
- nkohari 9mo agoYou're over-rotating on security. Not that it isn't important, but there are other dimensions to software that benefit heavily from the author having a deep understanding of the code that's being created.