Admitting that hard problems are hard

A presentation at DevOpsDays Ghent 2019 in October 2019 in Ghent, Belgium by Sasha Rosenbaum

Slide 1

Slide 1

Admitting that hard problems are hard SASHA ROSENBAUM

Slide 2

Slide 2

You have been tasked with building a website

Slide 3

Slide 3

Imagine your CTO, Bob

Slide 4

Slide 4

Bob has an idea

Slide 5

Slide 5

Slide 6

Slide 6

  • Hey, Bob, I don’t understand… - Why do we need all this?!

Slide 7

Slide 7

Are you saying that YOU don’t understand this?

Slide 8

Slide 8

Slide 9

Slide 9

Slide 10

Slide 10

Resume driven development

Slide 11

Slide 11

Slide 12

Slide 12

“If you can’t explain it to a six-year-old, you don’t understand it yourself.” ― Albert Einstein

Slide 13

Slide 13

Slide 14

Slide 14

Slide 15

Slide 15

We should stop pretending that ❖Distributed systems are easy ❖People can be available 24/7 ❖Unicorn companies don’t have technical debt ❖That new product will solve all of your problems

Slide 16

Slide 16

The intro slide Sasha Rosenbaum Sr. Program Manager @Microsoft @DivineOps

Slide 17

Slide 17

Computer Science Top 20 CS department in the world • • • • System Administrator for IAF R&D Software Engineer Azure Consultant Cloud Solution Architect https://www.linkedin.com/in/sasha-rosenbaum/

Slide 18

Slide 18

You must be marketing!

Slide 19

Slide 19

We use heuristics to navigate the world

Slide 20

Slide 20

Slide 21

Slide 21

Stereotypes are self-perpetuating

Slide 22

Slide 22

Studies in 2012 and 2015 Same resume with a male (vs female) name was 6-14% more likely to get an interview. The resumes with white-sounding names spurred 50% more callbacks than the ones with black-sounding names.

Slide 23

Slide 23

Slide 24

Slide 24

Why am I telling you this?

Slide 25

Slide 25

Slide 26

Slide 26

The cost is much higher for ❖Women ❖People of color ❖Junior Engineers

Slide 27

Slide 27

Why speak up?

Slide 28

Slide 28

Complexity isn’t free

Slide 29

Slide 29

Costs of complexity https://abstrusegoose.com/432 ❖Time to learn ❖Time to build ❖Cost of Maintenance ❖Chances of failure

Slide 30

Slide 30

Money

Slide 31

Slide 31

Productivity

Slide 32

Slide 32

Building Effective Teams (Google Study) Background? Personality types? Skills?

Slide 33

Slide 33

Building Effective Teams (Google Study) Background Personality types Skills => Psychological Safety

Slide 34

Slide 34

Psychological safety A belief that a team is safe for risk taking in the face of being seen as ignorant, incompetent, negative, or disruptive.

Slide 35

Slide 35

Psychological Safety Feeling confident that no one on the team will embarrass or punish anyone else for admitting a mistake, asking a question, or offering a new idea.

Slide 36

Slide 36

How many of you have that?

Slide 37

Slide 37

How many of you remember not having that?

Slide 38

Slide 38

Psychological safety doesn’t just happen

Slide 39

Slide 39

As a leader, remember

Slide 40

Slide 40

Make it safe to express opinions

Slide 41

Slide 41

Make it safe to admit mistakes

Slide 42

Slide 42

You don’t know everything

Slide 43

Slide 43

You are here to IMPROVE not to PROVE yourself

Slide 44

Slide 44

Slide 45

Slide 45

None of this is easy

Slide 46

Slide 46

But it is worth it!

Slide 47

Slide 47

Thank You! @DivineOps

Slide 48

Slide 48

Resources https://rework.withgoogle.com/print/guides/5721312655835136/ https://www.news.com.au/finance/work/careers/the-same-resume-with-differentnames-nets-different-results/news-story/a2a182fb4570e948c27ce63139ee66b1 https://www.politifact.com/punditfact/statements/2015/mar/15/jalen-ross/blackname-resume-50-percent-less-likely-get-respo/ https://www.technion.ac.il/en/2016/08/technion-ranked-top-in-israel-69thworldwide/ https://www.amazon.com/Mindset-New-Psychology-Success-dpB07N48NM33/dp/B07N48NM33/ http://projects.wsj.com/buzzwords2014