Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Speaker Deck
PRO
Sign in
Sign up for free
Optimize for Developer Happiness
Ben Balter
April 26, 2016
Technology
0
220
Optimize for Developer Happiness
Why how you work is as important as what you work on
Ben Balter
April 26, 2016
Tweet
Share
More Decks by Ben Balter
See All by Ben Balter
A community of communities: Empowering maintainers to grow communities around their code
benbalter
0
800
Fostering a culture of collaboration
benbalter
0
130
Growing open source communities on GitHub around your WordPress plugin or theme
benbalter
1
160
It takes a digital village
benbalter
1
250
Open source workflows in highly regulated environments
benbalter
0
60
The technology is the easy part
benbalter
2
220
How to foster an open source culture inside Government
benbalter
3
1.8k
Open source inspired workflows for open (and closed) geospatial data
benbalter
0
100
10 ways people are (mis)using GitHub Pages for fun and profit
benbalter
6
570
Other Decks in Technology
See All in Technology
Spotify物理コントローラーがほしい
miso
0
160
Oracle Database Technology Night #55 Oracle Autonomous Database 再入門
oracle4engineer
PRO
1
120
A Conditional Point Diffusion-Refinement Paradigm for 3D Point Cloud Completion
takmin
0
210
⚡Lightdashを試してみた
k_data_analyst
0
210
AWSの基礎を学ぼうで学んだ9種類のDBを勝手にふりかえる
98lerr
2
720
1年間のポストモーテム運用とそこから生まれたツール sre-advisor / SRE NEXT 2022
fujiwara3
6
3.2k
[SRE NEXT 2022]組織に対してSREを適用するとはどういうことか
srenext
0
160
runn is a package/tool for running operations following a scenario. / golang.tokyo #32
k1low
1
200
開発者のための GitHub Organization の安全な運用と 継続的なモニタリング
flatt_security
3
3.7k
CTOのためのQAのつくりかた #scrumniigata / SigSQA How to create QA for CTOs and VPoEs
caori_t
0
230
実験!カオスエンジニアリング / How to Chaos Engineering
oracle4engineer
PRO
0
140
Steps toward self-service operations in eureka
fukubaka0825
0
620
Featured
See All Featured
The Language of Interfaces
destraynor
148
20k
The MySQL Ecosystem @ GitHub 2015
samlambert
238
11k
Learning to Love Humans: Emotional Interface Design
aarron
261
37k
Optimizing for Happiness
mojombo
365
63k
Making Projects Easy
brettharned
98
4.3k
XXLCSS - How to scale CSS and keep your sanity
sugarenia
236
1M
We Have a Design System, Now What?
morganepeng
35
2.9k
In The Pink: A Labor of Love
frogandcode
130
21k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
19
1.4k
Fontdeck: Realign not Redesign
paulrobertlloyd
73
4.1k
Facilitating Awesome Meetings
lara
29
3.9k
GraphQLの誤解/rethinking-graphql
sonatard
24
6.2k
Transcript
! Optimize for developer happiness Why how you work is
as important as what you work on @benbalter
CONWAY'S LAW "organizations which design systems... are constrained to produce
designs which are copies of the communication structures of these organizations"
! Developer-centric development
! STARTUP the fairytale
Low value High value Startup Established firm Ideas Process
Low value High value Startup Established firm Geeks Suits
! What does your organization optimize for?
! Happy shareholders Successful software Efficient developers Strategic management
! Happy shareholders Good software Happy developers Happy Customers
! You can make software without MANAGEMENT
! You can make software without COMPLIANCE AND OVERSIGHT
! You can't make software without DEVELOPERS
! DEVELOPER HAPPINESS Optimize for and the rest will follow
! Developer happiness (Inside|Outside) the firewall
! Inside the firewall
! Traditional software development
! When outcomes can't be measured, institute process
! Daily, synchronous meetings to manually shuttle information around the
organization
! Decisions made in person, in hour-long blocks with
all stakeholders present
! Blocking, human-based processes
! Email as the least-common denominator
! Organizational knowledge lives (and dies) with employees
! bus_factor++
! Open-source development
! Transparency solves for process
! The constraints of open source
! Electronic
! Available
! Asynchronous
! Lock-free
! Prefer systems that naturally CAPTURE AND EXPOSE PROCESS
! Open source inside the firewall
! Open source is a PHILOSOPHY AND A WORKFLOW
not as an alternative technology
! How to WORK LIKE AN OPEN SOURCE PROJECT
! 1. Share to the widest extent possible
! Openness breaks down silos, reduces duplication, and minimizes on-boarding
time
! 2. Minimize developer friction
! Friction (n) the time it takes to go
from "I want to contribute" to "I have contributed"
! Common scripts to rule them all http://githubengineering.com/scripts-to-rule-them-all/
! PREFER CULTURAL CONSTRAINTS to technical and administrative constraints
! Non-blocking is better than blocking
! Never force a human to do what a robot
can
! ChatOps, DevOps, Hubot, and CI
! If you liked it you should have PUT AN
API ON IT
! Outside the firewall
! APIs make developers happy
! Openness makes developers happy
! Two caveats
! 1. Open up almost everything
! 2. Openness is about more than just throwing 0's
and 1's over the firewall
! Treat your data with the same respect that developers
treat code
! Open source, inner source, APIs, & open data all
foster communities around shared challenges
! Be the hub, not the single point of failure
(or innovation)
! Adopt an expanded definition of stakeholders
! Ensure all stakeholders have the opportunity to contribute
on equal footing
! Decentralize governance
! Minimize information imbalance
! 1. Work in the open
! 2. Propose and discuss improvements in the open
! 3. One shared, public issue tracker
! 4. Minimize synchronous meetings (and memorialize them when necessary)
! 5. Extensive, automated tests
! How do you optimize for developer happiness?
! Inside the firewall systems that capture and expose process
! Outside the firewall treat external stakeholders as internal stakeholders
! No really, how do you optimize for developer happiness?
! TECHNOLOGY is the easy part
! Bureaucracy is an organism
! Inoculate with small doses of culture and innovation
! Involve all stakeholders early on
! Start small and go through the motions
! Create a "feedback" repository both internally and externally
! Open data Open governance Open tooling
! DEVELOPER HAPPINESS Optimize for and the rest will follow
! Optimize for developer happiness Why how you work is
as important as what you work on @benbalter