17 Nov 2026 You cant blame AI for the code you ship | Freshworks Murali Swaminathan
Freshworks uses an AI Product Development Lifecycle to manage code quality and prioritize measurable customer impact over mere tool adoption.
Published 23 Jun 2026
Duration: 00:46:06
Modern software security grapples with autonomous agent-driven deployment risks, AI-generated code vulnerabilities like "vibe coding," expanded OWASP Top 10 2025 threats, supply chain weaknesses, and the urgent need for collaborative, proactive security practices, cultural shifts, and developer education over fragmented tools and outdated methodologies.
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 Interru...
The podcast explores emerging security challenges driven by rapid advancements in autonomous agents, AI-assisted development, and the evolving software supply chain. Key concerns include the heightened risks associated with "vibe coding"relying on AI-generated code without thorough reviewwhich can introduce vulnerabilities, such as leaked secrets, even with secure prompts. The discussion highlights the OWASP Top 10 2025, now expanded to 13 items to address modern threats like supply chain risks, CI/CD security, and "vibe coding." It critiques outdated security practices, emphasizing the need for integrated approaches like "purple security," which fosters collaboration between development and security teams, rather than treating security as a product or a checklist. The podcast also addresses gaps in incident response data and the limitations of current security tools, which are often circumvented by developers due to inefficiency and cost.
A major theme is the shift toward embedding security earlier in the development lifecycle ("shifting left"), including code generation, to prevent vulnerabilities from arising post-deployment. The software supply chain was identified as a critical vulnerability, with risks extending beyond organizational control through compromised packages, developer-targeted attacks, and third-party dependencies. Examples include supply chain breaches exploiting post-install scripts and developers access becoming a vector for attacks. The discussion stresses the importance of secure defaults, structured reviews for AI tools, and rethinking security education to prioritize defensive coding practices over rote memorization of vulnerabilities. It also underscores the underreported scale of security breaches, with publicized incidents representing only a fraction of total incidents, and calls for systemic changes in documentation, accountability, and organizational culture to address security as a shared responsibility rather than a siloed task.
Additionally, the podcast touches on the psychological and economic factors influencing developer behavior, such as resistance to restrictive security policies and perverse incentives tied to feature delivery over safety. It advocates for pragmatic, flexible frameworks that align with workflow efficiency and emphasizes the need for secure, low-friction environments to normalize best practices. The hidden cost of delayed security measures, the interconnected nature of vulnerabilities, and the growing role of behavioral economics in shaping secure defaults were also highlighted. Overall, the discussion underscores the urgency of modernizing security practices to keep pace with evolving threats while fostering collaboration, education, and systemic improvements across development and organizational cultures.
What if you integrated secure AI prompts into your dev workflow to prevent vibe coding vulnerabilities?
What if you built a supply chain security layer into your dependency management process?
What if you redefined your security defaults to prioritize "lock the front door" principles?
17 Nov 2026 You cant blame AI for the code you ship | Freshworks Murali Swaminathan
Freshworks uses an AI Product Development Lifecycle to manage code quality and prioritize measurable customer impact over mere tool adoption.
3 Nov 2026 Bet on research, not on vibes | Together AIs Dan Fu
Domain expertise amplifies AI's impact on GPU kernel development, while organizations must adapt management practices to attribute costs and distribute individual engineering gains.
13 Oct 2026 Building the software factory from the spec up | LinearB's Ariel Illouz & Ofer Affias
"Linear B adopted AI-assisted, spec-driven development, starting small and scaling through structured practices, AI guilds, and iterative refinement, while addressing challenges in code context and engineer role shifts amid rapid industry changes."
29 Sept 2026 Why AI made code review the new bottleneck, and the metric that spotted it | Newsela's Dee Wilcox
"AI's impact on engineering teams is examined, revealing faster development cycles but longer reviews, requiring workflow adjustments, KPI tracking, and iterative testing, while balancing innovation, governance, and quality assurance."
15 Sept 2026 Treat your data pipelines like code, because your agents already do | MotherDuck's Jordan Tigani
"Modern data infrastructure evolves with AI-driven automation, smaller efficient systems, and tools like MotherDuck, balancing innovation, cost, and human collaboration."