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
170
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
350
Artisans and Apprentices
bantik
1
480
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
私の後悔をAWS DMSで解決した話
hiramax
4
210
基礎から学ぶ大画面対応(Learning Large-Screen Support from the Ground Up)
tomoya0x00
0
3.3k
print("Hello, World")
eddie
2
530
為你自己學 Python - 冷知識篇
eddie
1
350
Compose Multiplatform × AI で作る、次世代アプリ開発支援ツールの設計と実装
thagikura
0
170
Processing Gem ベースの、2D レトロゲームエンジンの開発
tokujiros
2
130
アセットのコンパイルについて
ojun9
0
130
アプリの "かわいい" を支えるアニメーションツールRiveについて
uetyo
0
280
知っているようで知らない"rails new"の世界 / The World of "rails new" You Think You Know but Don't
luccafort
PRO
1
190
スケールする組織の実現に向けた インナーソース育成術 - ISGT2025
teamlab
PRO
2
160
Design Foundational Data Engineering Observability
sucitw
3
200
Flutter with Dart MCP: All You Need - 박제창 2025 I/O Extended Busan
itsmedreamwalker
0
150
Featured
See All Featured
4 Signs Your Business is Dying
shpigford
184
22k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
656
61k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
35
3.1k
Building a Scalable Design System with Sketch
lauravandoore
462
33k
Reflections from 52 weeks, 52 projects
jeffersonlam
352
21k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
23
1.4k
How STYLIGHT went responsive
nonsquared
100
5.8k
Building Applications with DynamoDB
mza
96
6.6k
Being A Developer After 40
akosma
90
590k
Learning to Love Humans: Emotional Interface Design
aarron
273
40k
VelocityConf: Rendering Performance Case Studies
addyosmani
332
24k
Unsuck your backbone
ammeep
671
58k
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