Optimize for Developer Happiness

Slide 1

Slide 1 text

! Optimize for developer happiness Why how you work is as important as what you work on @benbalter

Slide 2

Slide 2 text

CONWAY'S LAW "organizations which design systems... are constrained to produce designs which are copies of the communication structures of these organizations"

Slide 3

Slide 3 text

! Developer-centric development

Slide 4

Slide 4 text

! STARTUP the fairytale

Slide 5

Slide 5 text

Low value High value Startup Established ﬁrm Ideas Process

Slide 6

Slide 6 text

Low value High value Startup Established ﬁrm Geeks Suits

Slide 7

Slide 7 text

! What does your organization optimize for?

Slide 8

Slide 8 text

! Happy shareholders Successful software Eﬃcient developers Strategic management

Slide 9

Slide 9 text

! Happy shareholders Good software Happy developers Happy Customers

Slide 10

Slide 10 text

! You can make software without MANAGEMENT

Slide 11

Slide 11 text

! You can make software without COMPLIANCE AND OVERSIGHT

Slide 12

Slide 12 text

! You can't make software without DEVELOPERS

Slide 13

Slide 13 text

! DEVELOPER HAPPINESS Optimize for and the rest will follow

Slide 14

Slide 14 text

! Developer happiness (Inside|Outside) the ﬁrewall

Slide 15

Slide 15 text

! Inside the ﬁrewall

Slide 16

Slide 16 text

! Traditional software development

Slide 17

Slide 17 text

! When outcomes can't be measured, institute process

Slide 18

Slide 18 text

! Daily, synchronous meetings to manually shuttle information around the organization

Slide 19

Slide 19 text

! Decisions made in person,   in hour-long blocks with   all stakeholders present

Slide 20

Slide 20 text

! Blocking, human-based processes

Slide 21

Slide 21 text

! Email as the least-common denominator

Slide 22

Slide 22 text

! Organizational knowledge lives (and dies) with employees

Slide 23

Slide 23 text

! bus_factor++

Slide 24

Slide 24 text

! Open-source development

Slide 25

Slide 25 text

! Transparency solves for process

Slide 26

Slide 26 text

! The constraints of open source

Slide 27

Slide 27 text

! Electronic

Slide 28

Slide 28 text

! Available

Slide 29

Slide 29 text

! Asynchronous

Slide 30

Slide 30 text

! Lock-free

Slide 31

Slide 31 text

! Prefer systems that naturally   CAPTURE AND EXPOSE PROCESS

Slide 32

Slide 32 text

! Open source inside the ﬁrewall

Slide 33

Slide 33 text

! Open source is a   PHILOSOPHY AND A WORKFLOW   not as an alternative technology

Slide 34

Slide 34 text

! How to   WORK LIKE AN OPEN SOURCE PROJECT

Slide 35

Slide 35 text

! 1. Share to the widest extent possible

Slide 36

Slide 36 text

! Openness breaks down silos, reduces duplication, and minimizes on-boarding time

Slide 37

Slide 37 text

! 2. Minimize developer friction

Slide 38

Slide 38 text

! Friction (n)   the time it takes to go from   "I want to contribute" to   "I have contributed"

Slide 39

Slide 39 text

! Common scripts to rule them all http://githubengineering.com/scripts-to-rule-them-all/

Slide 40

Slide 40 text

! PREFER CULTURAL CONSTRAINTS to technical and administrative constraints

Slide 41

Slide 41 text

! Non-blocking is better than blocking

Slide 42

Slide 42 text

! Never force a human to do what a robot can

Slide 43

Slide 43 text

! ChatOps, DevOps, Hubot, and CI

Slide 44

Slide 44 text

! If you liked it you should have PUT AN API ON IT

Slide 45

Slide 45 text

! Outside the ﬁrewall

Slide 46

Slide 46 text

! APIs make developers happy

Slide 47

Slide 47 text

! Openness makes developers happy

Slide 48

Slide 48 text

! Two caveats

Slide 49

Slide 49 text

! 1. Open up almost everything

Slide 50

Slide 50 text

! 2. Openness is about more than just throwing 0's and 1's over the ﬁrewall

Slide 51

Slide 51 text

! Treat your data with the same respect that developers treat code

Slide 52

Slide 52 text

! Open source, inner source, APIs, & open data all  foster communities around shared challenges

Slide 53

Slide 53 text

! Be the hub, not the single point of failure (or innovation)

Slide 54

Slide 54 text

! Adopt an expanded definition of stakeholders

Slide 55

Slide 55 text

! Ensure all stakeholders have the opportunity to contribute   on equal footing

Slide 56

Slide 56 text

! Decentralize governance

Slide 57

Slide 57 text

! Minimize information imbalance

Slide 58

Slide 58 text

! 1. Work in the open

Slide 59

Slide 59 text

! 2. Propose and discuss improvements in the open

Slide 60

Slide 60 text

! 3. One shared, public issue tracker

Slide 61

Slide 61 text

! 4. Minimize synchronous meetings (and memorialize them when necessary)

Slide 62

Slide 62 text

! 5. Extensive, automated tests

Slide 63

Slide 63 text

! How do you optimize for developer happiness?

Slide 64

Slide 64 text

! Inside the ﬁrewall systems that capture and expose process

Slide 65

Slide 65 text

! Outside the ﬁrewall treat external stakeholders as internal stakeholders

Slide 66

Slide 66 text

! No really, how do you optimize for developer happiness?

Slide 67

Slide 67 text

! TECHNOLOGY is the easy part

Slide 68

Slide 68 text

! Bureaucracy is an organism

Slide 69

Slide 69 text

! Inoculate with small doses of culture and innovation

Slide 70

Slide 70 text

! Involve all stakeholders early on

Slide 71

Slide 71 text

! Start small and  go through the motions

Slide 72

Slide 72 text

! Create a "feedback" repository both internally and externally

Slide 73

Slide 73 text

! Open data Open governance Open tooling

Slide 74

Slide 74 text

! DEVELOPER HAPPINESS Optimize for and the rest will follow

Slide 75

Slide 75 text

! Optimize for developer happiness Why how you work is as important as what you work on @benbalter