= Session =
Prompt-driven Security: when Vibe Coding goes into production
First we had Shadow IT. Then we had Shadow AI. Now we have Shadow Code. And in each iteration the first thing on our mind is getting benefits quickly. But with Shadow Code, the end result becomes our product. And nobody's really sure how easily it can be hacked.
Vibe coding is not going away. It's here to stay, and we need to learn to live with it. Let's take 30 minutes to build out practical techniques and reminders to do some Vibe security as well. A little more prompts may go a long way towards sleeping better.
The same techniques are a good refresher for the non-vibe coders, because we are all human, and we can all slip.
Related Sessions
QA Commandments: 10 Must-follow security practices to secure your web apps
TalkIn today’s digital landscape, QA isn’t just about making sure things work - it’s a ...
Pair Programming 2.0: AI Agents are Changing the Way We Think About Code
TalkAre we shifting away from the traditional two-keyboard setup? The landscape of collaborative coding ...
I've built 99 CRUDs, I hope this ain't one
TalkThere is a whole generation of new developers stuck in the CRUD space writing those same API handler ...
Reviving Express: A challenging road for Express 5.0
TalkThe Node.js world celebrated its 15 years this year, with the Express Framework turning the same age ...