On Being A Senior Engineer – Am I Already There?

Slide 1

Slide 1 text

Konstantin Diener | [email protected] Am I Already There? On Being A Senior Engineer

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

Konstantin Diener CTO and Co-Founder of cosee

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

When is one actually a Senior Engineer?

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

You don’t wake up one day and you are “senior” just because your title reflects that upon a promotion. Senior engineers don’t know everything. They’re not perfect in their technical knowledge, and they’re OK with that. John Allspaw

Slide 12

Slide 12 text

I prefer to call them Mature Engineers.

Slide 13

Slide 13 text

Full Skill Developer Was ein Entwickler außer Coden noch können sollte Konstantin Diener [email protected] | @onkelkodi https://talks.cosee.biz/talk/d4777604-98cb-4c3c-9783-056790507da8

Slide 14

Slide 14 text

Mature Engineers …

Slide 15

Slide 15 text

… don’t need fancy job titles.

Slide 16

Slide 16 text

A huge body of research— hundreds of studies—shows that when people are put in positions of power, … Robert Sutton

Slide 17

Slide 17 text

… they start talking more, taking what they want for themselves, ignoring what other people say or want, ignoring how less powerful people react to their behavior, acting more rudely, and generally treating any situation or person as a means for satisfying their own needs … Robert Sutton

Slide 18

Slide 18 text

Robert Sutton The No Asshole Rule

Slide 19

Slide 19 text

Mature Engineers …

Slide 20

Slide 20 text

… are no A***holes

Slide 21

Slide 21 text

… the sustained display of hostile verbal and nonverbal behavior, excluding physical contact. Robert Sutton

Slide 22

Slide 22 text

But, this Engineer is that important!

Slide 23

Slide 23 text

There is such thing as an A***hole TCO!

Slide 24

Slide 24 text

Assholes have devastating cumulative e ff ects partly because nasty interactions have a far bigger impact on our moods than positive interactions — five times the punch, according to recent research. Robert Sutton

Slide 25

Slide 25 text

Enforcing the no asshole rule isn’t just management’s job. Robert Sutton

Slide 26

Slide 26 text

Mature Engineers do not avoid conflicts.

Slide 27

Slide 27 text

Mature Engineers …

Slide 28

Slide 28 text

… foster constructive critisism and discussion.

Slide 29

Slide 29 text

Intel preaches that the only thing worse than too much confrontation is no confrontation at all. Intel

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

We as an industry need to (of course) refrain from critiques of human character and condition, but not shy away from critiques of work product. Theo Schlossnagle

Slide 32

Slide 32 text

We need to get tougher skin and be able to receive critique through a lens that attempts to eliminate personal focus. There will be assholes, they should be shunned. Theo Schlossnagle

Slide 33

Slide 33 text

But the attitude that someone’s code is their baby should come to an end. Code doesn’t have feelings, doesn’t develop complexes and certainly doesn’t exhibit the most important trait (the ability to reproduce) of that which carries for your genetic strains. Theo Schlossnagle

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

„Perfection is achieved, not when there is nothing more to add, but when there is nothing le ft to take away.“ Antoine de Saint-Exupéry

Slide 36

Slide 36 text

• What might be missing? • What could cause this not to work? • Can you please generate as many antitheses to my idea as possible? • Even if it is technically sound, can the others in the organization understand, operate, extend and troubleshoot it? • How could Evil User Stories look like? Critique

Slide 37

Slide 37 text

But, that has a lot to do with people and not with machines.

Slide 38

Slide 38 text

Konstantin, I studied computer science because I don't want to have anything to do with people! a former colleague

Slide 39

Slide 39 text

Mature Engineers …

Slide 40

Slide 40 text

... have their product and their customers in mind.

Slide 41

Slide 41 text

That means contact with lots of people who know nothing about technology.

Slide 42

Slide 42 text

https://xkcd.com/2501

Slide 43

Slide 43 text

Does that mean Customers? 😱

Slide 44

Slide 44 text

That’s the job of our Product Owner … 😎

Slide 45

Slide 45 text

If you’re only using your engineers to code, you’re only getting half their value. Marty Cagan

Slide 46

Slide 46 text

Target Customer Underserved Needs Feature Set UX Value Proposition Product Market Fit nach Dan Olsens „Product-Market Fit Pyramid“

Slide 47

Slide 47 text

https://www.youtube.com/watch?v=s7YUQMa2Q0g

Slide 48

Slide 48 text

Konstantin Diener | [email protected] | @coseeaner … die Entwicklungs-Teams kennen sollten Product-Discovery-Techniken https://www.youtube.com/watch?v=TBMF56GQUOM

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

Product Owner Designer Developer

Slide 51

Slide 51 text

[…] a team can still get by with another engineer in the trio, as long as that engineer takes responsibility for fully vetting feasibility and getting buy-in from the rest of the engineering team as they work through assumption testing for the ideas that they are considering. Teresa Torres https://www.producttalk.org/2024/10/engineer-lead-product-trio/

Slide 52

Slide 52 text

Mature Engineers …

Slide 53

Slide 53 text

... reduce complexity.

Slide 54

Slide 54 text

• How does the smallest possible solution look like? • Do we need a Spike? • How can we use as little abstraction as possible? • Make it work, make it fast, make it scale! Dev @ Trio

Slide 55

Slide 55 text

Great so ft ware today is o ft en preferable to perfect so ft ware tomorrow. Andrew Hunt & David Thomas, The Pragmatic Programmer

Slide 56

Slide 56 text

Along similar lines, psychologist Karl Weick contends that aiming for “small wins” is o ft en a more comforting and ultimately e ff ective strategy than aiming for “big wins“. Robert Sutton

Slide 57

Slide 57 text

No content

Slide 58

Slide 58 text

Mature Engineers …

Slide 59

Slide 59 text

... make their assumptions explicit.

Slide 60

Slide 60 text

And help us to read code …

Slide 61

Slide 61 text

Programs must be written for people to read, and only incidentally for machines to execute. Abelson and Sussman

Slide 62

Slide 62 text

… to understand architecture …

Slide 63

Slide 63 text

… and to understand decisions.

Slide 64

Slide 64 text

https://www.youtube.com/watch?v=YotLyjDBng4

Slide 65

Slide 65 text

Wie kann es trotzdem funktionieren? Technologieentscheidungen im Team sind schwer! https://talks.cosee.biz/talk/8044646c-1a8e-4024-902a-aa0adb88c074

Slide 66

Slide 66 text

Mature Engineers …

Slide 67

Slide 67 text

… do not shy away from estimates.

Slide 68

Slide 68 text

Konstantin Diener | [email protected] | @coseeaner … das Enfant terrible der So!ware-Entwicklung Schätzungen https://www.youtube.com/watch?v=C-kp5oYnPoo

Slide 69

Slide 69 text

Mature Engineers …

Slide 70

Slide 70 text

… teach and learn.

Slide 71

Slide 71 text

The Best Test of a Person’s Character Is How He or She Treats Those with Less Power (especially when no one is watching). Robert Sutton

Slide 72

Slide 72 text

Tanya Reilly The Sta ff Engineer’s Path

Slide 73

Slide 73 text

Catalyst Group Individual The Sta ff Engineer’s Path

Slide 74

Slide 74 text

Group Individual Catalyst Advice Teaching Guardrails Opportunity The Sta ff Engineer’s Path

Slide 75

Slide 75 text

Group Individual Catalyst Mentoring, sharing, knowledge, feedback Tech talks, documentation, articles Mentorship program, tech talk events Code review, design review, coaching, pairing, shadowing Classes, codelabs Onboarding curriculum, teaching people to teach Code review, change review, design review Processes, linters, style guides Frameworks, culture change Delegating, sponsorship, cheerleading, ongoing support Sharing the spotlight, empowering your team Creating a culture of opportunity, watching with pride as your superstar junior colleagues change the world Advice Teaching Guardrails Opportunity The Sta ff Engineer’s Path