The Economics of Using AI to C...
Idiots should not #vibecode
I don't know what guardrails cursor has, as Claude code is my thing.
In my workflow, I have claude.md which contains operational directives including backups and docs.
NO COMMAND GETS EXECUTED WITHOUT MY AUTHORITY.
My vibecoding sessions consist (after issuing the prompt) of 1-40 consent commands for every single command that Ai executes.
1. Don't do it
2. Execute blah blah
3. Stop (where I can amend/seek explanation then proceed)
At every step Claude explains what it is doing, I constructed my .md this way.
Sure it may burn more tokens, but I have an idea of the process.
The code monkeys got lazy.
Lesson learned I expect.
Idiots should not #vibecode
I don't know what guardrails cursor has, as Claude code is my thing.
In my workflow, I have claude.md which contains operational directives including backups and docs.
NO COMMAND GETS EXECUTED WITHOUT MY AUTHORITY.
My vibecoding sessions consist (after issuing the prompt) of 1-40 consent commands for every single command that Ai executes.
1. Don't do it
2. Execute blah blah
3. Stop (where I can amend/seek explanation then proceed)
At every step Claude explains what it is doing, I constructed my .md this way.
Sure it may burn more tokens, but I have an idea of the process.
The code monkeys got lazy.
Lesson learned I expect.
I was initially to be super dismissive to the article.
I have seen far too many allegedly "professional" #infosec practitioners being irresponsible towards the new threat vector AND attack surface #Ai offers. But the article is solid IMHO
I will just add, that some top end corpo #vibecode devs use software platform simulacra to test against, including security...presumably