Link
Embed
Share
Beginning
This slide
Copy link URL
Copy link URL
Copy iframe embed code
Copy iframe embed code
Copy javascript embed code
Copy javascript embed code
Share
Tweet
Share
Tweet
Slide 1
Slide 1 text
Extremely Defensive Coding
Slide 2
Slide 2 text
a!/samphippen
Slide 3
Slide 3 text
I want to start with a story
Slide 4
Slide 4 text
“When is it OK to override the methods on object?”
Slide 5
Slide 5 text
I umm’d and ahh’d for a bit
Slide 6
Slide 6 text
I gave a half explanation and then asked them if they understood
Slide 7
Slide 7 text
I eventually came to an answer to do with consistency
Slide 8
Slide 8 text
Do it when it makes your object more consistent with Ruby, not less
Slide 9
Slide 9 text
e.g. an == on a data object
Slide 10
Slide 10 text
What makes a gem good?
Slide 11
Slide 11 text
Internals?
Slide 12
Slide 12 text
Internals?
Slide 13
Slide 13 text
Interface?
Slide 14
Slide 14 text
Interface? ✅
Slide 15
Slide 15 text
More convenient than if I did it myself
Slide 16
Slide 16 text
And it stays convenient
Slide 17
Slide 17 text
And it can be used by everyone on a team
Slide 18
Slide 18 text
And it works with a wide range of Ruby codebases
Slide 19
Slide 19 text
I don’t want much do I?
Slide 20
Slide 20 text
RSpec
Slide 21
Slide 21 text
RSpec Definitely always convenient
Slide 22
Slide 22 text
RSpec Definitely always convenient
Slide 23
Slide 23 text
User story
Slide 24
Slide 24 text
As an RSpec user
Slide 25
Slide 25 text
When I stub an object
Slide 26
Slide 26 text
I want the original method to be on that object after the example
Slide 27
Slide 27 text
So that my objects aren’t broken by my test suite
Slide 28
Slide 28 text
As an RSpec user
Slide 29
Slide 29 text
When I stub an object
Slide 30
Slide 30 text
I want the original method to be on that object after the example
Slide 31
Slide 31 text
So that my objects aren’t broken by my test suite
Slide 32
Slide 32 text
How does that work?
Slide 33
Slide 33 text
allow(cat).to receive(:meow)
Slide 34
Slide 34 text
Takes the meow method off cat
Slide 35
Slide 35 text
Saves it
Slide 36
Slide 36 text
Executes test
Slide 37
Slide 37 text
Puts the method back on the original object
Slide 38
Slide 38 text
How do you save a method?
Slide 39
Slide 39 text
No content
Slide 40
Slide 40 text
Method object
Slide 41
Slide 41 text
Put it somewhere else
Slide 42
Slide 42 text
Put it back at end of test
Slide 43
Slide 43 text
The end
Slide 44
Slide 44 text
The end
Slide 45
Slide 45 text
Defensive coding
Slide 46
Slide 46 text
RSpec::Support .method_handle_for
Slide 47
Slide 47 text
Simply invoking the method method is not good enough
Slide 48
Slide 48 text
Some scenes may have been altered/accelerated for your viewing pleasure
Slide 49
Slide 49 text
Let’s have some questions !!/samphippen
[email protected]
Slide 50
Slide 50 text
Users Lie
Slide 51
Slide 51 text
def method ‘get’ end
Slide 52
Slide 52 text
Users can redefine anything at any time in Ruby
Slide 53
Slide 53 text
Let’s have some questions !!/samphippen
[email protected]
Slide 54
Slide 54 text
Let’s have some questions !!/samphippen
[email protected]
Slide 55
Slide 55 text
Instance method object Method without a target object
Slide 56
Slide 56 text
Comes from a class/module not an instance
Slide 57
Slide 57 text
Grab the Kernel implementation of #method
Slide 58
Slide 58 text
Let’s have some questions !!/samphippen
[email protected]
Slide 59
Slide 59 text
Let’s have some questions !!/samphippen
[email protected]
Slide 60
Slide 60 text
Users can and will redefine core methods at any time
Slide 61
Slide 61 text
Instead we use Kernel’s implementation
Slide 62
Slide 62 text
Nobody screws with Kernel
Slide 63
Slide 63 text
Ruby interpreters lie
Slide 64
Slide 64 text
Some objects do not have Kernel in their inheritance chain
Slide 65
Slide 65 text
No content
Slide 66
Slide 66 text
Let’s have some questions !!/samphippen
[email protected]
Slide 67
Slide 67 text
Let’s have some questions !!/samphippen
[email protected]
Slide 68
Slide 68 text
Let’s have some questions !!/samphippen
[email protected]
Slide 69
Slide 69 text
Rebinding module methods
Slide 70
Slide 70 text
c
Slide 71
Slide 71 text
c
Slide 72
Slide 72 text
RSpec does not support Rubinius
Slide 73
Slide 73 text
No content
Slide 74
Slide 74 text
We tried, we really really tried
Slide 75
Slide 75 text
So anyway, dealing with module methods
Slide 76
Slide 76 text
Let’s have some questions !!/samphippen
[email protected]
Slide 77
Slide 77 text
Let’s have some questions !!/samphippen
[email protected]
Slide 78
Slide 78 text
Let’s have some questions !!/samphippen
[email protected]
Slide 79
Slide 79 text
Let’s have some questions !!/samphippen
[email protected]
Slide 80
Slide 80 text
Let’s have some questions !!/samphippen
[email protected]
Slide 81
Slide 81 text
Let’s have some questions !!/samphippen
[email protected]
Slide 82
Slide 82 text
Let’s have some questions !!/samphippen
[email protected]
Slide 83
Slide 83 text
Let’s have some questions !!/samphippen
[email protected]
Slide 84
Slide 84 text
Let’s have some questions !!/samphippen
[email protected]
Slide 85
Slide 85 text
Let’s have some questions !!/samphippen
[email protected]
Slide 86
Slide 86 text
Ruby interpreters behave differently.
Slide 87
Slide 87 text
Let’s have some questions !!/samphippen
[email protected]
Slide 88
Slide 88 text
Sometimes users don’t lie
Slide 89
Slide 89 text
No content
Slide 90
Slide 90 text
No content
Slide 91
Slide 91 text
No content
Slide 92
Slide 92 text
No content
Slide 93
Slide 93 text
`method': undefined method `foo' for class `Foo' (NameError)
Slide 94
Slide 94 text
This is a catch 22
Slide 95
Slide 95 text
Solution: trust but verify
Slide 96
Slide 96 text
No content
Slide 97
Slide 97 text
No content
Slide 98
Slide 98 text
No content
Slide 99
Slide 99 text
Let’s put it all together
Slide 100
Slide 100 text
No content
Slide 101
Slide 101 text
Wrapping up
Slide 102
Slide 102 text
This is why I love RSpec
Slide 103
Slide 103 text
Please file bugs
Slide 104
Slide 104 text
Your gem should be defensive
Slide 105
Slide 105 text
Users lie Redefinitions come from anywhere, expect them
Slide 106
Slide 106 text
Ruby interpreters lie Your code will run on non-MRI, old MRI, etc
Slide 107
Slide 107 text
Sometimes users don’t lie Users are weird, trust but verify
Slide 108
Slide 108 text
What makes a gem good?
Slide 109
Slide 109 text
Internals?
Slide 110
Slide 110 text
That explanation made no sense
Slide 111
Slide 111 text
Internals?
Slide 112
Slide 112 text
Interface?
Slide 113
Slide 113 text
allow(cat).to receive(:meow)
Slide 114
Slide 114 text
You get the complexity of RSpec working with any object for free
Slide 115
Slide 115 text
You probably didn’t even know it was there until I just told you
Slide 116
Slide 116 text
Interface? ✅
Slide 117
Slide 117 text
Gems
Slide 118
Slide 118 text
Gems are like super objects
Slide 119
Slide 119 text
Done badly they cause an even more extreme mess
Slide 120
Slide 120 text
Done correctly they hide huge complexity behind well defined barriers
Slide 121
Slide 121 text
Defending against users helps your gem be convenient
Slide 122
Slide 122 text
Write defensively, and your users will never know what’s inside the box
Slide 123
Slide 123 text
Remember the story?
Slide 124
Slide 124 text
This talk is born out of Ruby’s power
Slide 125
Slide 125 text
We need our code to defend today, against the mistakes of our tomorrow
Slide 126
Slide 126 text
No content
Slide 127
Slide 127 text
Let’s have some questions a!/samphippen
[email protected]