Your developers are the attack surface now and vibe coding as a vulnerability | Tanya Janca

Episode notes

Developers are like water: if you make your security protocols too difficult, they will find a way to flow right around them. This week on Dev Interrupted, bestselling author and OWASP Top 10 Project Leader Tanya Janca returns to unpack why vibe coding has officially made the list of the most critical security risks in software development. Tanya breaks down the psychology of bad code, explains why the modern software engineer has become the primary attack surface, and shares actionable strategies for shifting security left directly into your AI prompts. Finally, she provides practical, behavioral solutions for building a golden path that makes secure coding the easy choice for your engineering team. Register here: for the June 25th workshop, Life Beyond Tokenmaxxing, to learn how to measure real AI impact and ROI across the SDLC. Follow the show:

• How LinearB helps Kraken find hidden bottlenecks across thousands of engineers | Nik Sudan72 / 100
• The discernment horizon, loop-driven development, and a wizard’s very defensible pond
• Microsoft’s wandering eyes, data labeling duties for senior devs at Meta, and prod is the new source code
• Your SDLC needs a productivity context engine
• How to harness your dragon with Fable, tech leaders turn to model routing, and coping with AI rockstars