DiscoverBrakeSec Education PodcastNickolas Means talks about Security, Devops velocity, blameless orgs, and conferences infosec should attend
Nickolas Means talks about Security, Devops velocity, blameless orgs, and conferences infosec should attend

Nickolas Means talks about Security, Devops velocity, blameless orgs, and conferences infosec should attend

Update: 2023-03-04
Share

Description

 

Guest info

Name and Title:

Nickolas Means, VP of Engineering at SYM

Email/Social Media Contact:

@nmeans on Twitter, @nmeans@ruby.social on Mastodon

Time Zone (if other than Pacific):

Central (Austin, TX)

 

Show Topic Summary / Intro

We welcome Nickolas Means to the stream. Nick is the VP of Engineering at Sym, the adaptive access tool built for developers. He's been an engineering leader for more than a decade, focused on helping teams build velocity through trust and autonomy. He's also a regular speaker at conferences around the world, teaching more

effective software development practices through stories of real-world engineering triumphs and failures.

He’s also the co-host of “Managing Up” a podcast with  Management tips, stories, and interviews to help navigate the challenges of managing creative and technical teams.

 

<td colspan="2" style="vertical-align: top; padding: 5pt 5pt 5pt 5pt; overflow: hidden; border: solid #
Comments 
In Channel
loading
00:00
00:00
x

0.5x

0.8x

1.0x

1.25x

1.5x

2.0x

3.0x

Sleep Timer

Off

End of Episode

5 Minutes

10 Minutes

15 Minutes

30 Minutes

45 Minutes

60 Minutes

120 Minutes

Nickolas Means talks about Security, Devops velocity, blameless orgs, and conferences infosec should attend

Nickolas Means talks about Security, Devops velocity, blameless orgs, and conferences infosec should attend

Nickolas Means and Bryan Brake

Questions and potential sub-topics (5 minimum):

  1. 'blameless environment' during an incident. We can discuss working an incident and if a 'blameless' environment the exception or the rule (stories from the trenches are always welcome)

  1. Building a compliance program without tanking your engineering velocity... I'd like to speak about that in terms of overall security (product security, scanning, license checks, and more)

  1. Is there a playbook to building more efficient dev and security teams? Can cross training dev in basic security, or security in sprint planning processes make a better experience for all?