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
Better Living Through Open Source
Search
Coraline Ada Ehmke
June 13, 2013
Programming
2
160
Better Living Through Open Source
How can we improve as developers while living our values?
Coraline Ada Ehmke
June 13, 2013
Tweet
Share
More Decks by Coraline Ada Ehmke
See All by Coraline Ada Ehmke
Scaling the Artisan
bantik
0
150
Your First Legacy Codebase
bantik
1
420
Alchemy and the Art of Software Development
bantik
0
340
Artisans and Apprentices
bantik
1
470
Lightweight BI with Ruby, Rails, and MongoDB
bantik
6
2.7k
Smash the Monolith: Refactoring Rails Apps with Services and APIs
bantik
8
1.2k
Lightweight Business Intelligence in Ruby
bantik
3
1.2k
Beautiful APIs with Faceted
bantik
3
360
Other Decks in Programming
See All in Programming
0626 Findy Product Manager LT Night_高田スライド_speaker deck用
mana_takada
0
170
なぜ「共通化」を考え、失敗を繰り返すのか
rinchoku
1
650
Blazing Fast UI Development with Compose Hot Reload (droidcon New York 2025)
zsmb
1
290
『自分のデータだけ見せたい!』を叶える──Laravel × Casbin で複雑権限をスッキリ解きほぐす 25 分
akitotsukahara
2
640
Azure AI Foundryではじめてのマルチエージェントワークフロー
seosoft
0
170
A2A プロトコルを試してみる
azukiazusa1
2
1.4k
Modern Angular with Signals and Signal Store:New Rules for Your Architecture @enterJS Advanced Angular Day 2025
manfredsteyer
PRO
0
220
5つのアンチパターンから学ぶLT設計
narihara
1
170
PHPで始める振る舞い駆動開発(Behaviour-Driven Development)
ohmori_yusuke
2
390
データの民主化を支える、透明性のあるデータ利活用への挑戦 2025-06-25 Database Engineering Meetup#7
y_ken
0
360
NPOでのDevinの活用
codeforeveryone
0
840
猫と暮らす Google Nest Cam生活🐈 / WebRTC with Google Nest Cam
yutailang0119
0
120
Featured
See All Featured
How to train your dragon (web standard)
notwaldorf
95
6.1k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
233
17k
The Web Performance Landscape in 2024 [PerfNow 2024]
tammyeverts
8
690
Testing 201, or: Great Expectations
jmmastey
43
7.6k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
7
740
The Power of CSS Pseudo Elements
geoffreycrofte
77
5.9k
Rails Girls Zürich Keynote
gr2m
95
14k
[RailsConf 2023] Rails as a piece of cake
palkan
55
5.7k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
331
22k
Building Better People: How to give real-time feedback that sticks.
wjessup
367
19k
Site-Speed That Sticks
csswizardry
10
690
Git: the NoSQL Database
bkeepers
PRO
430
65k
Transcript
Better Living Through Open Source Corey Ehmke June 2013
Who am I?
A developer with a long memory. (And a longer history.)
An active Open Source contributor.
A lead developer at Apartments.com.
A lifelong learner.
One day I asked myself...
What matters most to me as a developer? “ ”
#1 Getting better at what I do.
Building cool and useful stuff. #2
Finding learning & teaching moments. #3
Practicing good citizenship. #4
Then I asked myself...
“That’s great, but how do you actually practice these values?”
Hmm. Good question, self. Let’s see.
#1
#1 Getting better at what I do.
Studies have shown* that getting better at what you do
involves three kinds of “stuff”.
Studies have shown* that getting better at what you do
involves three kinds of “stuff”. * I totally made this up actually.
The Three Kinds of Stuff
The Three Kinds of Stuff Stuff I've Done
Stuff I Do Every Day The Three Kinds of Stuff
Stuff I've Done
Stuff I Do Every Day The Three Kinds of Stuff
Stuff I've Done Stuff I Want to Do
Stuff you’ve done is the problem-solving vocabulary you have to
work with.
Stuff you do every day reinforces that vocabulary.
Stuff you’re interested in motivates you to expand your vocabulary.
So getting better at what you do requires both practice
and making time for things that interest you.
Interlude #1: Advice from an English Major
I used to read a lot of crap.
I used to read a lot of crap.
I used to read a lot of crap.
I used to read a lot of crap.
In school I practiced reading more crap.
In school I practiced reading more crap.
In school I practiced reading more crap.
In school I practiced reading more crap.
Then I discovered books that hurt my brain. (In a
good way.)
Then I discovered books that hurt my brain. (In a
good way.)
Then I discovered books that hurt my brain. (In a
good way.)
Then I discovered books that hurt my brain. (In a
good way.)
Reading these books expanded my mental vocabulary.
Reading code can have the same effect...
...but only if it’s really good code.
Open Source gives you access to the best code ever
written.
None
Welcome to the library.
Welcome to the library.
#2
#2 Building cool and useful stuff.
If you’re lucky, your work involves creating and delivering useful
stuff.
Most of it will be good. Some of it will
be great. (And some of it will come back to haunt you.)
Business software has a finite number of users & stakeholders.
Fewer stakeholders means that fewer voices shape the solution.
Edge cases and client-specific code will eventually outweigh core functionality.
In short, closed-source code loses focus over time.
In open source software, users == stakeholders.
Open source code gains focus and utility over time. (Until
it stops being useful, at which point something quickly comes along to replace it.)
Open sourcing your cool and useful stuff makes it cooler
and even more useful.
#3
#3 Finding learning & teaching moments.
Seer: My First Gem
Simple, declarative DSL for graphing in RoR.
Elegant design, clean code, plenty of tests, & even a
sample project.
At the time, my best work to date.
None
None
My beautiful code was... not perfect.
My test suite sucked.
But the design was good and communicated intent.
The open source community took what I designed and ran
with it.
Humbling and encouraging.
None
`
#4
#4 Practicing good citizenship.
I faced a challenge.
I found a solution.
Other people may have the same challenge.
I should share the solution.
Open source software is the new commons.
If it weren’t for open source, most of us would
not have the jobs we do.
None
Don’t be that guy.
Contributing Effectively
Be a fixer. DO
Be a scribe. DO
DO Take bite-sized pieces.
DO Get the maintainers familiar with your name.
DON’T Change too much at once.
DON’T Overcommit or over commit.
DON’T Be a jerk.
DON’T Be anonymous.
Getting Started
None
None
None
Questions?
Corey Ehmke bantik.github.com @Bantik