The road to developers' hearts
summary
Practical playbook for reducing security friction: establish monthly office hours and async review channels so teams get timely advice; automate repeated checks and integrate them into CI/CD; buy a static analyzer for a niche DB language, fine-tune custom rules to cut false positives and make it usable; run lightweight tabletop exercises before projects; ruthlessly prioritize escalations with clear mitigation criteria. A rushed year‑end audit that produced many December fixes proves planning and early engagement save weeks of rework.
AI-written summary · about
chapters (10)
- 0:00Introduction and welcome
- 1:04Why collaboration matters
- 2:29Building trust between teams
- 6:27Engaging early and process balance
- 8:36Leveraging technology and automation
- 11:26Providing realistic recommendations
- 12:52Consistent risk assessment and escalation
- 14:38Changing security culture
- 16:26Mentoring and community impact
- 18:13Q&A session
related talks
40mDevelopers Dislike Security: Ten Frustrations and Resolutions
49mLessons from DevSecOps Trenches
27mBridging the Dev-Sec divide: Three tips for agile developers
01h 04mShifting Security Everywhere
31mSharing Security Secrets: How to Encourage Security Advocates
27mDevelopers Struggle with Application Security (and How to Make ...)
28mHow to prioritize dev experience in the development process
34mDevelopers do care about security: Building a more collaborative path