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
My Problem, My Solution
Search
Penelope Phippen
September 12, 2014
Technology
1
52
My Problem, My Solution
A talk about typing I gave at Frozen Rails 2014
Penelope Phippen
September 12, 2014
Tweet
Share
More Decks by Penelope Phippen
See All by Penelope Phippen
Introducing Rubyfmt
penelope_zone
0
550
How RSpec Works
penelope_zone
0
6.5k
Quick and easy browser testing using RSpec and Rails 5.1
penelope_zone
1
79
Teaching RSpec to play nice with Rails
penelope_zone
2
130
Little machines that eat strings
penelope_zone
1
90
What is processor (brighton ruby edition)
penelope_zone
0
98
What is processor?
penelope_zone
1
350
extremely defensive coding - rubyconf edition
penelope_zone
0
250
Agile, etc.
penelope_zone
2
210
Other Decks in Technology
See All in Technology
クラウド開発環境Cloud Workstationsの紹介
yunosukey
0
190
Cross Data Platforms Meetup LT 20250422
tarotaro0129
1
700
YOLOv10~v12
tenten0727
4
970
2025-04-24 "Manga AI Understanding & Localization" Furukawa Arata (CyberAgent, Inc)
ornew
2
230
白金鉱業Meetup_Vol.18_AIエージェント時代のUI/UX設計
brainpadpr
1
180
更新系と状態
uhyo
7
1.8k
【Oracle Cloud ウェビナー】ご希望のクラウドでOracle Databaseを実行〜マルチクラウド・ソリューション徹底解説〜
oracle4engineer
PRO
1
100
PagerDuty×ポストモーテムで築く障害対応文化/Building a culture of incident response with PagerDuty and postmortems
aeonpeople
2
350
MCPを活用した検索システムの作り方/How to implement search systems with MCP #catalks
quiver
12
6.8k
AI AgentOps LT大会(2025/04/16) Algomatic伊藤発表資料
kosukeito
0
140
SmartHR プロダクトエンジニア求人ガイド_2025 / PdE job guide 2025
smarthr
0
130
Mastraに入門してみた ~AWS CDKを添えて~
tsukuboshi
0
280
Featured
See All Featured
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
656
60k
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.2k
jQuery: Nuts, Bolts and Bling
dougneiner
63
7.7k
Facilitating Awesome Meetings
lara
54
6.3k
Become a Pro
speakerdeck
PRO
27
5.3k
Building a Scalable Design System with Sketch
lauravandoore
462
33k
Principles of Awesome APIs and How to Build Them.
keavy
126
17k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
19
1.1k
Statistics for Hackers
jakevdp
798
220k
Fontdeck: Realign not Redesign
paulrobertlloyd
83
5.5k
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
8
670
Testing 201, or: Great Expectations
jmmastey
42
7.5k
Transcript
The maybe monad as a replacement for nil
My Problem My Solution
Everyone Stand Up
None
a!/samphippen
My Problem
Type Checking is the Antithesis of Object Oriented Programming
Type
Types
What is a type?
What is a data type?
A type is a set of possible values and operations
Class
Terms are literally interchangeable in Ruby
Terms are literally interchangeable in Ruby Konstantin
Fixnum
✕
+
/
—
1.class # => Fixnum
You know what all these things do
1+1 # => 2
Array
count
each
In Ruby some types are interchangeable
Typeclass
A set of types and common operations
There is some expectation of what the operations will do
Duck typing
All number types in Ruby form a typeclass
Fixnum Float BigDecimal
Numeric Op Numeric = Numeric
Positive Numeric + Positive Numeric = Positive Numeric =
Also collections
Hash Set Array
Type Checking is the Antithesis of Object Oriented Programming
Type Checking is the Antithesis of Object Oriented Programming
Type Checking
This term has two meanings
Compile time type checking
public static final List<string> seriouslyiamsoboredwh ocares
Like in Java
Clearly we don’t do this in Ruby
So what do I mean?
ActiveRecord::Base #find_by
pony = Pony.find_by(:id => smth) pony.neigh
pony = Pony.find_by(:id => smth) if pony pony.neigh else puts
“No Pony can’t neigh” end
The problem here is two return types
nil Pony < AR::Base
We’re forced to add a type check
Also, I think this is the wrong type check
pony = Pony.find_by(:id => smth) if !pony.nil? pony.neigh else puts
“No Pony can’t neigh” end
A more explicit type check
But still wrong
pony = Pony.find_by(:id => smth) if !pony.nil? pony.neigh else puts
“No Pony can’t neigh” end
pony = Pony.find_by(:id => smth) if pony.respond_to?(:neigh) pony.neigh else puts
“No Pony can’t neigh” end
This type checking adds unnecessary complexity to our app
Type Checking is the Antithesis of Object Oriented Programming
Type Checking is the Antithesis of Object Oriented Programming
Antithesis
I am using it to mean “DOING IT WRONG”
Type Checking is the Antithesis of Object Oriented Programming
Type Checking is the Antithesis of Object Oriented Programming
Object oriented programming
Konstantin Haase says:
Data abstraction and control abstraction
Alan Kay says:
Everything is an object
Objects communicate by sending and receiving messages
def bees if :bar == a.foo else end end
def bees a.foo nil end
Tell don’t ask
Objects have their own memory (in terms of objects).
Data hiding
Every object is an instance of a class (which must
be an object).
The class holds the shared behavior for its instances (in
the form of objects in a program list)
To eval a program list, control is passed to the
first object and the remainder is treated as its message.
Type Checking is the Antithesis of Object Oriented Programming
Type Checking is the Antithesis of Object Oriented Programming
My Problem
My Problem
My Solution
Just always make your methods return things of a consistent
type class
Thanks!
No obviously there’s more
Third party APIs do this all the time
pony = Pony.find_by(:id => smth) if pony pony.neigh else puts
“No Pony can’t neigh” end
The problem here is two return types
As a client of this API I am forced to
add a type check
nil is such a common case
How do we fix it?
Null object pattern
I think this one is quite well known
class Pony def horse_power 0.5 end end
Pony.find_by( :key => value ) || NullPony.new
class NullPony def horse_power 0 end end
NullPony quacks the same as Pony
Solves the typing problem
Summing over ponies will only count Pony objects
0 might be the wrong default
Pony * NullPony = 0
Decided the default for horse_power when defining the class
Change is inevitable
Can’t predict how NullPony will be used in the future
Maybe Typeclass
Solves same problem
Allows for runtime defaults
#map(&blk) -> Maybe #value_or(a) -> a
class Just def initialize(value) @value = value end def map(&blk)
def value_or(x) Just.new(blk.call(@value)) @value end end end
class Nothing def map(&blk) self end def value_or(x) x end
end
A consistent interface for dealing with missing values
NoMethodError: undefined method `foo' for nil:NilClass
NoMethodError: undefined method `foo' for nil:NilClass
[Maybe, Nothing, Maybe]
call map on all of them
collapse with value_or
To Recap:
Null object can replace nils if you know the defaults
at class definition time
Maybe if you want defaults at run time
Your job is not to make Alan Kay happy
RSpec RSpec ! ! RSpec 3
tinyurl.com/ samfr2014
Let’s have some questions a!/samphippen
[email protected]