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
コードに語らせよう――自己ドキュメント化が内包する楽しさについて / Let the Code Speak
nrslib
6
1.4k
Using AI Tools Around Software Development
inouehi
0
1.2k
Go Modules: From Basics to Beyond / Go Modulesの基本とその先へ
kuro_kurorrr
0
110
人には人それぞれのサービス層がある
shimabox
3
670
C++20 射影変換
faithandbrave
0
430
Javaに鉄道指向プログラミング (Railway Oriented Pro gramming) のエッセンスを取り入れる/Bringing the Essence of Railway-Oriented Programming to Java
cocet33000
2
540
Effect の双対、Coeffect
yukikurage
5
1.4k
Beyond Portability: Live Migration for Evolving WebAssembly Workloads
chikuwait
0
350
アンドパッドの Go 勉強会「 gopher 会」とその内容の紹介
andpad
0
160
機械学習って何? 5分で解説頑張ってみる
kuroneko2828
0
210
ReadMoreTextView
fornewid
1
370
The Evolution of Enterprise Java with Jakarta EE 11 and Beyond
ivargrimstad
1
650
Featured
See All Featured
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
507
140k
Principles of Awesome APIs and How to Build Them.
keavy
126
17k
How To Stay Up To Date on Web Technology
chriscoyier
790
250k
The Power of CSS Pseudo Elements
geoffreycrofte
77
5.8k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
45
7.3k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
48
5.4k
What’s in a name? Adding method to the madness
productmarketing
PRO
22
3.5k
The Pragmatic Product Professional
lauravandoore
35
6.7k
Automating Front-end Workflow
addyosmani
1370
200k
Build your cross-platform service in a week with App Engine
jlugia
231
18k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
107
19k
How to Think Like a Performance Engineer
csswizardry
24
1.7k
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