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
230
Growing open source communities on GitHub around your WordPress plugin or theme
benbalter
1
250
It takes a digital village
benbalter
1
460
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
640
Other Decks in Technology
See All in Technology
OSSで50の競合と戦うためにやったこと
yamadashy
3
950
フレームワークを意識させないワークショップづくり
keigosuda
0
240
Wasmの気になる最新情報
askua
0
180
NLPコロキウム20251022_超効率化への挑戦: LLM 1bit量子化のロードマップ
yumaichikawa
1
190
ViteとTypeScriptのProject Referencesで 大規模モノレポのUIカタログのリリースサイクルを高速化する
shuta13
2
140
AI駆動で進める依存ライブラリ更新 ─ Vue プロジェクトの品質向上と開発スピード改善の実践録
sayn0
1
170
Railsの話をしよう
yahonda
0
170
QA業務を変える(!?)AIを併用した不具合分析の実践
ma2ri
0
110
Claude Codeを駆使した初めてのiOSアプリ開発 ~ゼロから3週間でグローバルハッカソンで入賞するまで~
oikon48
10
5.4k
会社を支える Pythonという言語戦略 ~なぜPythonを主要言語にしているのか?~
curekoshimizu
3
570
Introduction to Bill One Development Engineer
sansan33
PRO
0
300
ソフトウェアエンジニアの生成AI活用と、これから
lycorptech_jp
PRO
0
840
Featured
See All Featured
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
115
20k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
52
5.7k
Testing 201, or: Great Expectations
jmmastey
45
7.7k
[RailsConf 2023] Rails as a piece of cake
palkan
57
5.9k
Java REST API Framework Comparison - PWX 2021
mraible
34
8.9k
Site-Speed That Sticks
csswizardry
13
920
4 Signs Your Business is Dying
shpigford
185
22k
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
26
3.1k
jQuery: Nuts, Bolts and Bling
dougneiner
65
7.9k
Imperfection Machines: The Place of Print at Facebook
scottboms
269
13k
Rebuilding a faster, lazier Slack
samanthasiow
84
9.2k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
34
2.5k
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