Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

The friction between developers and security isn't due to developers' apathy. The issue is that security teams often provide 'crappy' tools that generate thousands of irrelevant alerts without context. Developers have always cared about security, but they resist processes that are inefficient and don't align with their workflows.

Related Insights

Forcing users through multi-step authentication for a simple, low-risk task like paying for parking is a classic sign of a developer-led, not product-led, mindset. It prioritizes technical convenience or arbitrary standards over the end-user experience, leading to abandonment.

Traditional security tools like identity management or API firewalls are ineffective for securing AI agents. They can see an action (e.g., deleting a database) but lack the context to know if it was an intended, productive task or a catastrophic error, rendering them useless for this new paradigm.

The most effective first step to improve developer experience (DevEx) is not building automation or buying tools. Instead, conduct a 'listening tour' with developers about their daily friction. This uncovers high-impact, low-lift opportunities that premature solutions often miss.

To overcome developer apathy towards security (which feels like boring insurance), Snyk created entertaining talks showing live hacks of popular libraries. This made the threat feel visceral and personal, motivating developers to check their own code far more effectively than a standard risk pitch.

In large enterprises, AI adoption creates a conflict. The CTO pushes for speed and innovation via AI agents, while the CISO worries about security risks from a flood of AI-generated code. Successful devtools must address this duality, providing developer leverage while ensuring security for the CISO.

Low-code platforms have a massive opportunity to solve a decades-old security challenge by embedding "secure by default" guardrails. The key is transforming security from a technical hurdle into a configurable UI problem, making it digestible and manageable for the non-technical users who now build applications.

Vercel is building infrastructure based on a threat model where developers cannot be trusted to handle security correctly. By extracting critical functions like authentication and data access from the application code, the platform can enforce security regardless of the quality or origin (human or AI) of the app's code.

Enterprises face millions of potential vulnerabilities, making prioritization impossible. The key is to ignore the noise and focus only on the small fraction that are actually exploitable by hackers. This shifts remediation efforts from theoretical weaknesses to real-world business risk.

Experienced CISOs are less concerned about AI models 'going wild' and becoming malicious hackers. The more practical and immediate problem is that AI will dramatically increase the volume of vulnerabilities discovered in codebases. Security teams will be overwhelmed not by sophisticated AI attacks, but by the sheer quantity of legitimate issues to triage and fix.

Snyk saw low adoption when asking developers to add checks to their build process. The breakthrough was a GitHub app that not only flagged new vulnerabilities but proactively opened pull requests with the fix. This reframed the tool from a potential blocker to an indispensable, helpful assistant.