Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
The Art of Building Developer Tools
Search
Samuel E. Giddins
March 06, 2015
Technology
77
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
The Art of Building Developer Tools
Samuel E. Giddins
March 06, 2015
More Decks by Samuel E. Giddins
See All by Samuel E. Giddins
Funding Ruby Infrastructure as a Non-Profit
segiddins
0
61
Evolution of Rails within RubyGems.org
segiddins
0
53
The Challenges of Building a Sigstore Client from Scratch
segiddins
0
160
Keeping the Gems Sparkling
segiddins
0
110
A Survey of RubyGems CVEs
segiddins
0
110
Handling 225k requests per second to RubyGems.org
segiddins
0
120
State of the RubyGems 2023
segiddins
0
160
Building Broken Gems
segiddins
0
120
Switching Disciplines as a Tech Lead
segiddins
0
70
Other Decks in Technology
See All in Technology
GuardDuty 検知対応を DevOps Agent で効率化しようとしている話 / GuardDuty Investigations with DevOps Agent
masahirokawahara
1
350
enechainの内製セルフサービスプラットフォーム
hiyosi
0
150
作り直せるコードは迅速に 作り直せないDBは慎重に - AI時代のプロダクトエンジニアが「判断の不可逆性」で開発速度を変える話
kinosuke01
0
300
SQL文一行も書けない人事がCortexもろもろを使って人事業務を楽にしてみる
ponponmikankan
1
220
Code4Lib JAPANカンファレンス2026 開会挨拶 / Code4Lib JAPAN Conference 2026: Opening Remarks
ykiyota
0
330
Sigmaで作る業務アプリ
kazushiro_honma
0
110
TinyGo 開発サイクルを高速化する:Go で作るエミュレータ入門
zozotech
PRO
1
600
20260912_スクラムにジェネラリストは必要か
ryugen04
0
320
From Vanilla Kubernetes to a Batteries-Included Platform: Developer Experience at 1,300+ Clusters
yosshi_
0
680
AIで仕事のやり方を変える
matsu7874
3
1k
10分で知る最近のOmarchy
komagata
0
250
Deploying a Full-Stack Bun-Native Framework on Cloudflare Workers
7nohe
0
130
Featured
See All Featured
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.8k
Documentation Writing (for coders)
carmenintech
77
5.5k
Un-Boring Meetings
codingconduct
0
410
[SF Ruby Conf 2025] Rails X
palkan
2
1.4k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
31
10k
Building Flexible Design Systems
yeseniaperezcruz
330
41k
Chasing Engaging Ingredients in Design
codingconduct
0
300
Efficient Content Optimization with Google Search Console & Apps Script
katarinadahlin
PRO
1
840
The SEO Collaboration Effect
kristinabergwall1
1
550
Learning to Love Humans: Emotional Interface Design
aarron
275
41k
Lessons Learnt from Crawling 1000+ Websites
charlesmeaden
PRO
1
1.6k
Rebuilding a faster, lazier Slack
samanthasiow
85
9.6k
Transcript
The Art of Building Developer Tools
Samuel Giddins Realm
None
LLVM I couldn’t do my job without it.
None
What do these projects, and countless others, have in common?
None
Developer Tools
How we get from point A to point B. Every
day.
My Projects
None
None
None
None
Each is a different kind of tool
How can I make these things?
1. Find something that’s missing from your workflow 2. Build
it 3. Build it in such a way others can use it 4. Receive feedback 5. Ignore 70% of it 6. Have a thick skin 7. Keep on improving
Is this something I want to do?
Maybe Don’t rush into it. It’s a lot of work,
and you won’t succeed unless it’s a project that makes you happy.
Is there a real problem space here? Can someone in
my position provide a solution?
Think risk vs. reward. Think about access. Think about time.
Does my experience leave me ready to solve this problem?
—Is it general? —Is it in-depth? —Is it unavoidable?
! Great
! Great Go Forth and Build
None
Solve a small, difficult problem first. Do it better than
anyone ever has before.
Document it up the wazoo. Both header docs and ‘guides’.
Yes, you need both.
Initial traction comes easier the more focused your solution is.
Once you have an audience, start spreading out. Find the
ancillary problems, and solve them one at a time.
As your project grows, it will lose people. Not everyone
loves a monolith. So try and make sure the things you bolt on both belong and don’t take over.
On the negative side
There Will Be Issues
There Will Be Insults
There Will Be Holy Wars
everything is terrible, nothing works, people are horrible, and there
will be cool people doing awesome things on a regular basis — André Arko
Ignore All of That (If you want to)
Above All, Have Empathy
You’re asking a fellow developer to spend their most precious
resource on something you built. It’s an honor. It’s a heavy responsibility.
Conclusion
Conclusion Let’s go and build some cool stuff.
Available now on Speaker Deck. https://speakerdeck.com/segiddins/the-art-of- building-developer-tools
None
Samuel Giddins Realm @segiddins