Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Optimize for Developer Happiness
Search
Ben Balter
April 26, 2016
Technology
0
280
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
1
1.3k
Fostering a culture of collaboration
benbalter
0
220
Growing open source communities on GitHub around your WordPress plugin or theme
benbalter
1
240
It takes a digital village
benbalter
1
450
Open source workflows in highly regulated environments
benbalter
0
92
The technology is the easy part
benbalter
2
290
How to foster an open source culture inside Government
benbalter
3
2.4k
Open source inspired workflows for open (and closed) geospatial data
benbalter
0
150
10 ways people are (mis)using GitHub Pages for fun and profit
benbalter
6
630
Other Decks in Technology
See All in Technology
Kubernetes における cgroup v2 でのOut-Of-Memory 問題の解決
pfn
PRO
0
420
DuckDB-Wasmを使って ブラウザ上でRDBMSを動かす
hacusk
1
130
Flutterでキャッチしないエラーはどこに行く
taiju59
0
200
「AI2027」を紐解く ― AGI・ASI・シンギュラリティ
masayamoriofficial
0
160
役割は変わっても、変わらないもの 〜スクラムマスターからEMへの転身で学んだ信頼構築の本質〜 / How to build trust
shinop
0
150
Figma + Storybook + PlaywrightのMCPを使ったフロントエンド開発
yug1224
10
3.5k
ヘブンバーンズレッドのレンダリングパイプライン刷新
gree_tech
PRO
0
400
『FailNet~やらかし共有SNS~』エレベーターピッチ
yokomachi
1
190
生成AI時代のデータ基盤
shibuiwilliam
1
1.2k
Microsoft Fabric のネットワーク保護のアップデートについて
ryomaru0825
1
120
見てわかるテスト駆動開発
recruitengineers
PRO
6
2.3k
Goss: Faiss向けの新しい本番環境対応 Goバインディング #coefl_go_jp
bengo4com
1
1.4k
Featured
See All Featured
Build The Right Thing And Hit Your Dates
maggiecrowley
37
2.8k
Git: the NoSQL Database
bkeepers
PRO
431
66k
Why Our Code Smells
bkeepers
PRO
339
57k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
30
9.6k
Intergalactic Javascript Robots from Outer Space
tanoku
272
27k
Code Review Best Practice
trishagee
70
19k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
333
22k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
51
5.6k
A Tale of Four Properties
chriscoyier
160
23k
Building Adaptive Systems
keathley
43
2.7k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
284
13k
Bootstrapping a Software Product
garrettdimon
PRO
307
110k
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