Tech and Brew – Giving Developers A Voice
Here’s a question for the DevSecOps folks: How do you ensure secure development when security is often seen as the thing slowing projects down?
YOU HAVE TO GIVE THE DEVELOPER A VOICE.
☝️ Collect your data of your developers. Preferred languages, projects, pains, etc.
✌️ Correlate the feedback they’ve given with strategic initiatives and give developers the WHY for their work rather than making them code monkeys.
If you want better security in development that lasts, it starts with making the developer feel heard. Lasting change starts with empathy, not mandates.
How have you seen empathy being used as a way to create lasting change?