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
Creating a Gem
Search
Jeff Felchner
March 22, 2013
Technology
1
130
Creating a Gem
Jeff Felchner
March 22, 2013
Tweet
Share
More Decks by Jeff Felchner
See All by Jeff Felchner
Rails Engines as an SOA Middle Ground
jfelchner
1
470
Advanced and Intermediate Git
jfelchner
1
85
Rails Templates
jfelchner
1
65
Other Decks in Technology
See All in Technology
All About Sansan – for New Global Engineers
sansan33
PRO
1
1.3k
わが10年の叡智をぶつけたカオスなクラウドインフラが、なくなるということ。
sogaoh
PRO
1
270
Java 25に至る道
skrb
3
150
[PR] はじめてのデジタルアイデンティティという本を書きました
ritou
0
770
Introduction to Sansan for Engineers / エンジニア向け会社紹介
sansan33
PRO
5
59k
Node vs Deno vs Bun 〜推しランタイムを見つけよう〜
kamekyame
1
260
Everything As Code
yosuke_ai
0
490
re:Invent2025 セッションレポ ~Spec-driven development with Kiro~
nrinetcom
PRO
2
170
産業的変化も組織的変化も乗り越えられるチームへの成長 〜チームの変化から見出す明るい未来〜
kakehashi
PRO
1
320
スクラムマスターが スクラムチームに入って取り組む5つのこと - スクラムガイドには書いてないけど入った当初から取り組んでおきたい大切なこと -
scrummasudar
1
1.5k
Bedrock AgentCore Evaluationsで学ぶLLM as a judge入門
shichijoyuhi
2
320
BidiAgent と Nova 2 Sonic から考える音声 AI について
yama3133
2
150
Featured
See All Featured
AI: The stuff that nobody shows you
jnunemaker
PRO
1
160
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
508
140k
Optimizing for Happiness
mojombo
379
70k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
162
16k
Leveraging LLMs for student feedback in introductory data science courses - posit::conf(2025)
minecr
0
100
Git: the NoSQL Database
bkeepers
PRO
432
66k
Raft: Consensus for Rubyists
vanstee
141
7.3k
Navigating Team Friction
lara
191
16k
Ten Tips & Tricks for a 🌱 transition
stuffmc
0
47
Claude Code のすすめ
schroneko
67
210k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
333
22k
How Software Deployment tools have changed in the past 20 years
geshan
0
31k
Transcript
Creating Your First Gem
What?
Does One Thing Well
Why?
Programming is hard.
Programming well is really hard.
The Problem
Naming
The First Rule
Name It Something Clever
The Second Rule
Don’t Take One Of My Names
None
615.555.1234
None
The Third Rule
Don’t Be Inappropriate
Don't name it something sexual.
Don't name it something misogynistic
Don't name it after crude words for your anatomy
F&%#
None
Why Listen To Me?
rspectacular null_and_void bangers_and_hash envision dolla_dolla_bill stipend use_the_forcible referehencible molten_core dynamo
johnny_five i_am_valid oscillator chronological greenwich get_together enwrap pinpoint chicken_soup apple_cart ruby-progressbar
Our Example
None
“Translating pig latin is fun”.to_pig_latin # => “anslating-tray ig-pay atin-lay
is-ay un-fay”
None
Creating Your Gem
Jewler
Hoe
Bundler
</disclaimer>
gem install bundler bundle gem pope_francis
create pope_francis/Gemfile create pope_francis/Rakefile create pope_francis/LICENSE.txt create pope_francis/README.md create pope_francis/.gitignore
create pope_francis/pope_francis.gemspec create pope_francis/lib/pope_francis.rb create pope_francis/lib/pope_francis/version.rb
create pope_francis/Gemfile create pope_francis/Rakefile create pope_francis/LICENSE.txt create pope_francis/README.md create pope_francis/.gitignore
create pope_francis/pope_francis.gemspec create pope_francis/lib/pope_francis.rb create pope_francis/lib/pope_francis/version.rb
Gem::Specification.new do |gem| gem.name = "pope_francis" gem.version = PopeFrancis::VERSION gem.authors
= ["Jeff Felchner"] gem.email = ["
[email protected]
"] gem.description = %q{TODO: Write a gem description} gem.summary = %q{TODO: Write a gem summary} gem.homepage = "" end
Gem::Specification.new do |gem| gem.name = "pope_francis" gem.version = PopeFrancis::VERSION gem.authors
= ["Jeff Felchner"] gem.email = ["
[email protected]
"] gem.description = %q{ig-pay atin-lay anslator-tray} gem.summary = %q{The one-stop shop for your Pig Latin needs} gem.homepage = "http://github.com/jfelchner/pope_francis" end
Releasing Your Gem
Sign Up on rubygems.org
None
Add Your Gem to Github (optional)
None
rake release
pope_francis 0.0.1 built to pkg/ pope_francis-0.0.1.gem Tagged v0.0.1 Pushed git
commits and tags Pushed pope_francis 0.0.1 to rubygems.org
None
Versioning
Use Semantic Versioning (http://semver.org)
x.y.z Major . Minor . Patch (eg 1.8.4)
Your Gem’s Version
pope_francis/lib/pope_francis/version.rb
module PopeFrancis VERSION = "0.0.1" end
arning-way! Pushing The Same Version Twice Will Fail
> gem push pkg/pope_francis-0.0.1.gem Pushing gem to https://rubygems.org... Repushing of
gem versions is not allowed. Please use `gem yank` to remove bad gem releases.
Yanking Releases
> gem install gemcutter > gem yank pope_francis -v 0.0.1
Yanking gem from RubyGems.org... Pushing gem to https://rubygems.org... Successfully yanked gem: pope_francis (0.0.1)
None
> gem install pope_francis ERROR: Could not find a valid
gem 'pope_francis' (>= 0) in any repository ERROR: Possible alternatives: francis, tolerances
README Driven Development
Waaaaaaiiiiiiiiiiiiitttttttttt a second.....
Your Public API = Your Version
Your Public API is the most important thing when developing
a gem.
None
Write the Code
Fast Forward
pope_francis/lib/pope_francis.rb
require ‘pope_francis’
require ‘pope_francis’ while english_phrase = gets do puts english_phrase.to_pig_latin end
Hacking On It
Fork the Gem
https://github.com/jfelchner/pope_francis
Rename the Gem in Your Fork
pope_francis-nash-rails
pope_francis-nash-rails-jfelchner
Using It In Another Project
gem install pope_francis-nash-rails-jfelchner
require ‘pope_francis’
require ‘pope_francis-nash-rails-jfelchner’
Exercises
Additional Options
“Translating pig latin is fun” .to_pig_latin(:hyphenate => false) # =>
“anslatingtray igpay atinlay isway unfay”
Preserve Capitalization
“Translating Pig Latin is fun”.to_pig_latin # => “Anslating-tray Ig-pay Atin-lay
is-way un-fay”
Rails App
None
Thanks! Jeff Felchner @jfelchner