“Programs must be written
for people to read,
and only incidentally for
machines to execute”
—SICP
Slide 10
Slide 10 text
Communication
Slide 11
Slide 11 text
Touching
Slide 12
Slide 12 text
Build muscle
memory
Slide 13
Slide 13 text
Show,
don’t do
Slide 14
Slide 14 text
Ask only
when necessary
Slide 15
Slide 15 text
Listen
Slide 16
Slide 16 text
Build
Understanding
Slide 17
Slide 17 text
Recognize
your
assumptions
Slide 18
Slide 18 text
Ask
Questions
Slide 19
Slide 19 text
Leading
questions
Slide 20
Slide 20 text
Demonstrate
debugging
techniques
Slide 21
Slide 21 text
Learning
First
Slide 22
Slide 22 text
Digressions
second
Slide 23
Slide 23 text
K.I.S.S.
Slide 24
Slide 24 text
Avoid
distraction
Slide 25
Slide 25 text
“I don’t
know”
Slide 26
Slide 26 text
There are two
kinds of knowledge:
the kind that's “obvious”,
and the kind
we haven't acquired yet.
https://twitter.com/ReinH/status/488225181723525120
Slide 27
Slide 27 text
“This weekend I was
reminded how complex
(and in some cases, convoluted)
typical test setup is for Rails
applications.”
Justin Searls http://blog.testdouble.com/posts/2015-02-16-arcane-knowledge.html
Slide 28
Slide 28 text
“One engineering mindset that
has gotten in my way is the
thought that I will never
‘catch up on’
what other people already know.”
Emily Claire Reese http://blog.eclairereese.com/post/110897066911/playing-catch-up
Slide 29
Slide 29 text
Understanding
then
Criticism
Slide 30
Slide 30 text
Understand
why
Slide 31
Slide 31 text
Most
important first
Slide 32
Slide 32 text
Let it Slide
Slide 33
Slide 33 text
Good
>
Perfect
Slide 34
Slide 34 text
Build
confidence
Slide 35
Slide 35 text
Safe Spaces
Slide 36
Slide 36 text
Remove
traps
Slide 37
Slide 37 text
Manage
Frustration
Slide 38
Slide 38 text
Pay attention
to feelings
Slide 39
Slide 39 text
Take breaks
Slide 40
Slide 40 text
Leave them
alone
Slide 41
Slide 41 text
Thinking
Tools
Slide 42
Slide 42 text
Draw
pictures
Slide 43
Slide 43 text
Physical
analogues
Slide 44
Slide 44 text
Search skills
Slide 45
Slide 45 text
Cultivate
Good Behavior
Slide 46
Slide 46 text
Testing
Slide 47
Slide 47 text
Documentation
Slide 48
Slide 48 text
Commit
practices
Slide 49
Slide 49 text
Code
review
Slide 50
Slide 50 text
Time
Estimation
Slide 51
Slide 51 text
Task
scoping
Slide 52
Slide 52 text
Newbs
Slide 53
Slide 53 text
Equals
collaborating
Slide 54
Slide 54 text
Culture of
Sharing
Slide 55
Slide 55 text
Share credit
Slide 56
Slide 56 text
Defer to
experts
Slide 57
Slide 57 text
Apologize
Slide 58
Slide 58 text
Touching
Slide 59
Slide 59 text
Talking over
Slide 60
Slide 60 text
Misunderstand
Slide 61
Slide 61 text
Acknowledge
mistakes
Slide 62
Slide 62 text
Use these
skills
Slide 63
Slide 63 text
Onboarding
Slide 64
Slide 64 text
Learning a
new system
Slide 65
Slide 65 text
Working
with juniors
Slide 66
Slide 66 text
Code school
TA
Slide 67
Slide 67 text
Increase
Happiness
Slide 68
Slide 68 text
“Talking with [Eric]
was like that car
ride in The Matrix,
Slide 69
Slide 69 text
where they're telling
you all this really cool
stuff about the world
Slide 70
Slide 70 text
and you wouldn't
have got to know
it by yourself.
Slide 71
Slide 71 text
But then you get
pushed
out of the car
Slide 72
Slide 72 text
and you're in some
part of town
you've never been to
Slide 73
Slide 73 text
and you have
no idea
how to walk home.
Slide 74
Slide 74 text
I will say, since then Eric has taken
a lot more care in packing a lunch
for me, and pinning my mittens to
my coat so I don't lose them.”
Elizabeth Uselton
Slide 75
Slide 75 text
Contributors
•Liz Rush
•Cat Useleton
•Elizabeth Uselton
•Hsing-Hui Hsu
•Fastly
•Ada Developers Academy Students