►
Description
Pamela Vickers, an Engineering Manager at Mailchimp, discusses how to guide newcomers through the stages of learning. Most of the four learning stages—unconscious incompetence, conscious incompetence, conscious competence and unconscious competence—are bridged by acquiring experience. But the gap between unconscious incompetence to conscious incompetence is where the most discomfort and discouragement occurs.
Helping new developers bridge that void ensures a vibrant, accessible community, and having visible members/mentors in each stage encourages newcomers' learning. This talk illustrates (literally!) how to help new colleagues build this bridge and prevent losing them in the what-do-I-even-Google abyss.
About GitHub Universe:
GitHub Universe is a two-day conference dedicated to the creativity and curiosity of the largest software community in the world. Sessions cover topics from team culture to open source software across industries and technologies.
For more information on GitHub Universe, check the website:
https://githubuniverse.com
A
I'm
going
to
go
ahead
and
get
started
to
keep
this
this
train
on
time,
I'm
pamela
vickers
and
I'm
really
excited
to
be
here.
We're
gonna
jump
right
in.
Do
you
all
remember
this
talk
or
this
blog
post,
a
lot
of
people
were
sharing
it.
A
lot
of
people
had
really
strong
opinions
about
it,
as
they
often
do
on
the
internet
and
Jeff
Atwood
of
coding.
Horror
was
making
some
points
about
how
all
of
these
learn
to
code.
A
Efforts
might
be
kind
of
fundamentally
flawed
in
a
few
areas,
and
his
major
points
were
that
it
assumes
that
more
code
in
the
world
is
inherently
desirable
thing.
It
just
seems
that
coding
is
the
goal.
It
puts
the
method
before
the
problem.
It
assumes
that
adding
naive
novice
not
even
sure
they
like
this
whole
programming
thing
coders
to
the
workforce,
is
a
net
positive
for
the
world,
and
it
also
implies
that
there's
a
thin,
easily
permeable
membrane
between
learning
to
program
and
getting
paid
to
program
professionally.
A
So
some
of
his
assertions
had
some
merit,
but
a
lot
of
his
post
reads
that,
as
if
there
are
these
checkpoints
and
these
mandatory
hour
of
codes,
you
must
you
must
perform
every
year.
And
what
really
stood
out
to
me
is
that
these
two
points
have
nothing
to
do
with
learning,
to
code
problems
and
problems
that
have
much
more
to
do
with
how
existing
developers
welcome
developing
developers
into
the
developer
community
and
into
the
workforce.
A
A
lot
of
people
who
disagree
disagreed
very
strongly
as
edge
Shaw
is
one
of
them,
but
a
lot
of
the
people
who
were
disagreeing
had
this
context
and
this
contact
with
new
developers,
and
so
they
were
pretty
kind
of
appalled
at
some
of
the
points
that
Jeff
Atwood
is
making
and
said.
Shah
wrote
this
entire
rebuttal
called:
please
no
become
anything,
especially
not
a
programmer,
and
the
people
who
agreed
seem
to
mostly
live
in
the
comment
section
and
they
all
seem
to
talk
about
new
developers
and
new
coders
in
a
very
abstract
sense.
A
It
didn't
sound,
like
very
many
of
them,
had
even
met
anybody
that
was
on
that
learning
to
code
path.
So
the
new
developers
aren't
just
faceless
drones
that
are
coming
and
like
typing
things,
into
terrible
websites
and
taking
jobs.
They
are
all
people
that
are
learning
this
for
very
legitimate
reasons
and
very
different
reasons.
They
have
different
backgrounds,
different
experiences,
and
we
really
only
benefit
by
welcoming
them
and
make
and
helping
them
succeed.
A
This
is
level
one
Tenderfoot
can't
even
see
the
mountain
from
where
she
is.
She
knows
her,
probably
is
a
mountain,
but
she
doesn't
even
know
that
she's
going
to
have
to
cross
this
ridiculous
Canyon
to
get
there,
and
this
is
a
place
in
the
learning
to
code
journey
where
a
lot
of
times,
people
just
start
with
how
do
I
learn
to
code,
and
if
you
look
really
closely,
you
can
see
that
on
everyone
there's
like
millions
of
results,
so
this
is
where
we
introduce
a
new
character
named
bingle.
A
Clearly
and
Tenderfoot
can
ask
being
goal
of
anything,
but
bingle
has
no
idea
which
tenderfoots
trying
to
accomplish
so.
At
the
start,
some
of
the
answers
help
help
or
hurt.
So
as
she
goes
through
her
journey,
she
will
definitely
learn
how
to
use
bingle
better,
but
at
first
Bingle
can
almost
be
a
burden.
Much
like
scarecrow
from
wizard
of
oz.
When
Tenderfoot
asked
bingle
how
do
I
learn
to
code,
she
sold
many
different,
conflicting
things.
Oh
that
way
is
a
very
nice
way.
A
A
Unfortunately,
Tenderfoot
at
this
point
has
to
decide
on
our
first
few
steps
all
on
her
own
Raven,
Covington
and
Atlanta
rails.
Girls.
Member
once
told
me,
as
I,
began
learning
I
found,
there's
so
much
great
content
out
on
the
internet,
which
is
both
awesome
and
overwhelming.
It
was
difficult
for
me
to
chart
my
own
path
and
figure
out
where
to
go
next,
so
Tenderfoot
like
Raven
and
like
Dorothy,
must
pick
a
direction
somewhat
arbitrarily
and
pursue
it.
So
in
the
dark.
She
picks
a
direction
and
just
goes
for
it
stopped
by
uninformed
step.
A
A
A
They
might
not
even
remember
that
they're
on
a
mountain
at
all
in
the
first
place
and
all
they
know-
is
just
kind
of
their
life
in
the
clouds
and
they're
pretty
happy
that
way,
but
occasionally
one
will
wake
up,
will
stretch
will
fly
down
and
they'll
see
who
might
be
further
down
the
mountain
and
they'll
try
and
help
them
back
up,
since
they
remember
how
they
got
there.
They
are
in
some
learning
models
in
a
stage
described
as
reflective
competence
or
conscious
competence
of
unconscious
competence.
A
So
it's
likely
that
you've
worked
with
someone
kind
of
like
this,
where
they
are
snoozing.
They
don't
really
remember
much.
You
can
go
to
them
for
the
the
questions
that
are
more
highly
technical
in
nature.
Maybe
what
tool
do
I
use?
You
can
go
them
for
a
code
review,
but
when
we
are
really
lucky,
you
get
to
work
with
one
of
these
people,
the
level
five
people
who
they
can
answer
those
hard
challenging
questions.
A
They
can
answer
the
fundamental
questions
as
well
and
they're
patient
with
you
and
let
you
catch
up
to
where
they
are
and
make
sure
that
their
explanations
actually
helped
you
so
we'll
find
others
in
the
mountain
community
in
the
level
to
the
conscious
and
competence
stage
and
level
3
the
conscious
competent
stage.
They
are
all
kind
of
climbing
together.
A
A
But
we
are
also
going
back
and
bringing
people
up
with
us
so
back
to
Tenderfoot
she's,
not
even
seeing
the
mountain
yet
she's,
just
going
through
the
forest,
hoping
for
the
best
she's,
not
scared,
it's
not
scary,
but
it's
just
a
big
vast
forest
she's
been
asking
for
bingle
for
help
he's
been
doing
his
best,
providing
basic
directions:
she's
filling
her
knapsack
with
lots
and
lots
of
tools.
She's
got
some
JavaScript
in
there,
some
Python
some
HTML,
some
CSS
Ruby,
she's,
filling
it
and
the
knapsacks
getting
heavier
and
everything
is
getting
mixed
up.
A
She'll
reach
in
to
pull
one
tool
and
grabbed
the
wrong
one.
He
doesn't
even
notice
because
she
doesn't
even
know
why
those
things
are
in
her
knapsack
to
begin
with
her
out
and
perfect
and
direct,
but
she
still
makes
it
to
the
edge
of
the
forest
she
steps
out
of
the
dark
forest
and
sees
a
glimmer
of
light.
A
She
hikes
up
to
the
canyon
ledge
and
sees
a
couple
Mountaineers
on
the
other
side,
so
she's
pretty
excited.
She
thinks
he's
done.
It
she's
made
it
at
this
point,
so
she
kind
of
waved
that
them,
but
they
don't
really
notice
her
right
away.
So
she
writes
a
note
on
a
paper
plane
and
sends
it
across.
She
says:
hey
new
friends:
how
do
we
get
across
this
canyon
Thanks?
A
So
you've
probably
seen
the
equivalent
of
this
somewhere.
There's
that
question
on
Stack
Overflow
or
someone
who
finds
your
your
local
black
community,
maybe
even
IRC,
if
they're
a
little
bit
more
adventurous
and
they're
asking
for
help
and
direction,
but
they're
asking
something
huge
and
vague,
but
that
might
be
their
first
contact
with
the
developer
community
at
all
and
I.
A
Think
that's
kind
of
frightening
I
took
a
look
at
the
learn:
programming
reddit,
because
I
heard
some
really
good
things
and
I
heard
a
lot
of
people
were
getting
a
lot
of
good
advice
from
there
and
I
found
it's
a
pretty
supportive
community.
But
there
are
people
there
who
think
they're
being
helpful
and
kind
of
could
take
a
look
at
their
messaging
because,
even
with
a
good
response,
they
can
have
a
lot
of
discouragement
just
packaged
right
in
and
so
let's
say,
Tenderfoot
had
written
this
post.
A
It
says
I
want
to
really
dig
into
programming,
but
I'm
feeling
a
bit
overwhelmed.
They
said
I
read
post
here
and
I'm
absolutely
lost
in
the
amount
of
technical
jargon
and
such
more
than
jargon,
I'm
worried
about
the
mathematical
aspects
of
programming.
I've
struggled
for
most
of
my
educational
career
with
anything
beyond
vams
da
Silva.
Can
anyone
give
me
some
insight
into
what
level
of
math
I
should
be
proficient
in
if
I
want
to
go
anywhere
with
programming?
A
The
top
voted
reply
was
really
long,
a
pretty
well
intention,
but
it
began
with
these
this
series
of
questions.
The
first
thing
you
want
to
do
is
take
a
look
at
yourself.
Do
you
like
math?
Do
you
like
logic
problems?
Are
you
good
at
breaking
complex
problems
in
two
parts?
If
you
answered
yes
to
one
or
more
of
those
keep
reading,
if
that
stuff
sounds
like
a
drag,
please
save
yourself
some
time
and
look
into
something
else.
A
Alternatively
thermae
or
this
post
about
programming
does
not
be
at
all,
and
if
you
aren't
familiar,
she
is
one
of
the
ones
who
wrote
the
rails
bridge
curriculum.
So
she
discovered
this
early
in
the
process
and
she
says
that
adult
students
who
came
to
the
workshop
came
from
the
very
wide
range
of
backgrounds
and
she
noticed
that
people
with
a
math
background
did
fine,
of
course,
but
people
with
a
heavy
language
background
often
did
better.
She
said
when
she
worked
with
high
schoolers.
She
noticed
that
the
bilingual
kids
took
to
it
more
quickly
as
well.
A
So,
despite
all
of
the
computer
science
background
she
had
and
the
conversation
she
might
have
had
with
people,
she
determined
something
pretty
profound.
That
programming
is
just
not
math,
so
it's
kind
of
a
big
difference
between
this
idea
and
someone
who
has
me
a
little
bit
more
hands-on
that
observation,
so
it
all
suggests,
is
consider
every
paper
airplane.
You
encounter
to
be
more
like
a
delicate
paper
plane
and
we
want
to
be
kind.
We
want
to
be
encouraging.
A
We
want
to
be
honest,
instead
expectations,
but
just
remember
that
that
response
that
they
receive
from
you
might
be
their
first
and
then
ultimately
their
last
communication
with
someone
in
the
developer
community,
so
Tenderfoot
sweden
on
her
reply,
she's
still
reading,
typing
away.
She's
learning
all
of
the
things
without
really
learning
anything
and
she
gets
the
message
to
reply.
It
says:
haven't
you
heard
of
a
bridge,
so
she
feels
kind
of
sad
and
silly.
A
At
the
same
time,
she's
worried
that
maybe
she's
kind
of
stumbled
into
area
folks,
who
aren't
really
that
interested
in
helping
I
found
this
post
as
well.
It
says
why
are
experienced
programmers
so
hostile
toward
beginners.
They
said
it's
usually
assumed
that
I
haven't
done
my
own
research,
which
is
never
the
case
for
every
helpful
reply.
It
seems
they'll
get
four
or
five
useless
replies,
attempting
to
call
me
out
for
my
own
laziness,
which
that
just
really
hurt
me
a
lot
because
I
know
I've
seen
that
as
well.
A
Fortunately,
this
message
isn't
that
aggressive.
Maybe
it's
just
a
little
smug,
so
she's
still
sticks
around
and
gets
another
message.
It
says:
are
you
asking
how
to
build
a
bridge?
So
that's
a
little
bit
better,
maybe
she's
ready
to
keep
going.
But
what
could
she
have
done
better
when
she
was
writing
her
own
message?
Asking
stock
overflow
has
a
guide
to
asking
the
perfect
question
and
its
pretty
long,
but
my
summary
is
essentially
start
with
the
Golden
Rule.
Imagine
you're
trying
to
answer
the
question
provide
context,
but
maybe
not
too
much.
A
Don't
don't
include
your
entire
code
base,
maybe
just
the
relevant
bits
frame.
The
problem
describe
the
tools
you're
using
and
describe
what
you've
tried
already
and
yeah
provide
the
right
sample
code
and
the
right
data
and
write
something
articulately,
don't
just
throw
something
together
when
you're
frustrated
throw
it
up
there,
because
the
last
someone
has
to
interpret
themselves
the
more
helpful
they
can
be.
But
what
the
guy
doesn't
say
that
you
should
really
consider
the
same
things
when
you're
writing
an
answer.
A
So
golden
rule
provide
context
really
make
sure
that
you
explain
your
thought
process
and
how
you
got
to
the
suggestion
you're
proposing,
so
that
it's
not
just
a
magical
answer
that
they
just
take
and
run
with,
but
don't
really
learn
from
so
this
time.
She
thinks
about
her
message
and
tries
to
provide
a
little
bit
more
context.
She
says:
I've
just
found
this
canyon
and
I'd
like
to
cross
it
I.
Don't
know
how
wide
or
how
deep
it
is,
but
I
see
that
some
of
you
have
made
it
across.
A
Can
you
tell
me
what
you
did
in
order
to
get
there
I'd
like
to
build
a
bridge
that
I'm
not
sure
what
materials
to
use
this
time
she
gets
a
longer
reply
back,
I
says,
hi
Tenderfoot
crossing
the
canyon
is
super
easy.
All
you
need
to
do
is
grab
your
foo
and
then
bar
the
bad,
but
make
sure
you
don't
boughs
the
bar
or
l.
It's
the
fool.
This
is
I'll,
see
you
soon.
A
Have
you
heard
the
phrase
drinking
from
the
firehose?
Yes,
maybe
you
know
what
that
feels
like
much
like
our
Tenderfoot
redditor
from
before?
It's
really
easy
as
a
new
learner
to
get
lost
in
the
vocabulary,
among
all
the
other
things
someone's
trying
to
learn.
So
this
is
a
pretty
common
image
and
whenever
people
talk
about
learning,
but
it
just
shows
what
people
are
really
learning
when
they're
learning
ruby
on
rails-
and
it's
so
big
like
we
have
to
look
at
in
pieces,
so
there's
web
stuff,
there's
operating
system
stuff,
there's
database
stuff
deployment
command
line.
A
We
have
text.
Editors
definitely
get
hung
up
on
that
as
early
as
possible.
What
else
do
we
have
here?
We
have
actually
Ruby
managing
Ruby
managing
the
dependencies.
Then
we
have
the
rails
framework,
which
is
probably
someone's
first
exposure,
not
probably,
but
likely
someone's
first
exposure
to
ideas
like
MVC
and
restful
api
s.
Then
we
have
get
which
is
pretty
important
and
then
github
and
knowing
that
they're
actually
not
the
same
thing,
that's
kind
of
important
that
takes
a
minute
for
people.
A
A
So,
there's
a
responsibility
on
both
sides
of
the
canyon.
When
mentors
provide
context
and
definitions
when
using
programming,
specific
terms
and
phrases,
it
removes
assumptions
and
it
can
provide
illumination
to
the
person
who
is
receiving
information
and
when
mentees
catalogue
and
really
learn
new
terms
and
ideas
they're
exposed
to
they
can
receive
better
help.
It
can
be
more
specific
and
more
precise,
so
Thunderfoot
spend
some
time
parsing
her
note.
She
uses
bingle
as
best
she
can
to
translate
some
of
the
message,
and
some
of
it
starts
to
make
sense
to
her.
A
But
she
still
stuck
on
a
few
things.
All
you
need
to
do
is
grab
your
food
and
then
bar
the
bass.
She
looks
in
her
knapsack,
but
she
doesn't
have
a
foo
available
to
borrow
the
bass,
getting
tools
and
environment
setup
even
at
it
as
an
experienced
developer
feels
at
best,
tedious
and
at
worst
impossible
when
you
are
installing
tools
to
install
other
tools
and
dependencies
starts
to
like
installation
inception.
A
Sorry
about
that,
we'll
just
move
on.
So
when
things
go
right,
it
can
be
confusing,
but
when
things
go
wrong,
it
is
both
confusing
and
frustrating
and
if
you're,
in
a
position
to
help
someone
get
set
up
when
that
frustration
sets
in
it's
kind
of
you
have
to
be
mindful
that
you
don't
let
them
experience
the
brunt
of
that
frustration,
because
then
we
can
ostracize
them
and
they're
already
in
a
pretty
vulnerable
position
and
I'm
guilty
of
some
of
these.
A
So
I
know
that
they
happen
I've
seen
all
of
these
happen,
probably
almost
every
installation,
fest
I,
have
ever
gone
24
any
workshop,
but
we
try
to
get
ahead
of
it
now
and
say:
hey
don't
make
those
jokes
they're
not
actually
funny.
So
here's
a
difficult
question
that
you've
probably
heard
how
do
I
get
our
vm
installed
am
I
1995
thinkpad.
Well,
this
is
horrible
answer,
get
a
new
macbook
pro
here's
another
difficult
question:
I'm,
having
issues
installing
anything
on
my
windows
or
linux
machine,
any
ideas.
A
Why
well
here's
a
horrible
answer,
because
everything's
just
harder
on
Windows
and
Linux
or
replace
whatever
OS.
You
really
feel
strongly
about.
So
just
don't
just
don't
do
this
at
all,
even
tongue
in
cheek,
which
I
think
programmer
humor
tends
to
be
kind
of
on
the
negative
side
and
someone
not
just
steeped
in
that
sort
of
humor
it's
kind
of
off-putting
and
instead
what
we
should
do
is
use
these
difficult
installations
to
show
that
that's
just
part
of
it
experience
people
right
into
these
things
all
the
time.
A
It's
easy
to
be
like
rah
rah
for
having
so
much
fun,
it's
going
to
change
your
life,
but
then
there
are
these
moments
where
you're
like
yeah.
It
did
change
my
life.
That
is
true,
so
use
these
opportunities
to
show
them
how
you
think
and
how
you
approach
these
problems
in
your
day-to-day,
because
it's
going
to
be
part
of
their
life
too.
If
they
keep
pursuing
it,
so
back
to
Tenderfoot
still
doesn't
have
a
foo.
She
looks
for
one,
but
no
luck.
She
has
bingle
where
do
I
get
through
Bingle's,
not
super
helpful,
just
offers.
A
Where
do
I
get
some
food,
and
given
her
experience
with
asking
questions
from
before,
she
waits
a
really
long
time
before
asking
again,
but
finally
realizing
she's
not
making
any
progress.
She
sends
another
message.
She
asks
sorry,
what
is
a
foo
I
can't
seem
to
find
one
sorry
for
asking
so
many
questions.
A
Well,
this
reply,
she
gets
quickly
did
I
say
a
foo
I
meant
to
say
in
norf
have
a
great
day.
So
here
she
is,
she
spent
precious
daylight
looking
for
a
foo,
but
what
she
really
needed
was
an
orphan
when
we
have
tutorials
with
out-of-date
information
and
new
version
numbers
or
when
we
assume
someone's
using
a
UNIX
shell
or
really
making
any
assumption
at
all,
we
can
send
a
tenderfoot
in
the
wrong
direction.
For
an
indefinite
amount
of
time-
and
they
might
be
too
hesitant
to
come
back
when
it's
not
working
for
them.
A
So
in
the
same
vein
of
write
code
for
the
future
developer.
Think
of
that,
when
you're
putting
helpful
information
out
into
the
world
make
sure
that
it
won't
send
someone
in
the
wrong
direction
and
check
in
whenever
possible
after
you've.
Given
someone
some
direction,
because
just
a
quick
did
that
work
for
you
might
save
them
hours
or
days
in
the
process
of
what
they're
trying
to
learn
or
build.
So
now
that
she
knows
that
she's.
Looking
for
a
Norv
she's
able
to
find
one.
A
Yay
exciting,
so
she
a
review
and
updates
her
instructions
to
grab
your
Norv
and
bar
the
bass,
so
with
some
help
from
bingle
and
a
few
informative
searches
later,
what
does
a
bar?
What
is
the
pass?
How
do
I
bar
she
carefully
meticulously
bars
the
bass
she
looks
up
and
sees
a
single
step
has
appeared
on
her
side
of
the
canyon
is
so
exciting
and
then
she
waits.
A
Yeah
and
nothing
else
happened,
she's
one
step
closer,
but
she
has
a
long
way
to
go
so
she's
back
to
having
to
ask
a
question.
So
she
writes
a
note,
says:
I've
successfully
barred
the
baths.
I
have
the
step
of
my
bridge
now.
Thank
you.
What
do
I
do
now
to
finish
my
bridge,
a
reply
arrives,
and
it
advises
great
news
now
just
keep
at
it.
You
have
to
bar
a
lot
of
basses
to
finish
building
your
bridge
across
this
canyon,
so
she
bars
abuzz
again.
She
gets
another
sup.
A
So
back
in
reddit
land,
a
tenderfoot
redditor
asks.
Is
it
okay?
If
I'm
successfully
going
through
code
Academy
lessons
while
not
fully
understanding
some
of
them,
they
describe
their
situation,
they
say
I'm
about
halfway
through
the
Python
course,
and
it's
not
quite
clicking
yet
I
haven't
been
having
any
problems
with
the
lessons,
but
sometimes
I'll
type
the
code
in
and
it
will
be
correct,
but
I'll
not
understand
why
it
worked.
Should
I
just
keep
going
and
not
worry
about
fully
understanding
it.
A
So
I
have
more
of
a
grip
on
the
language,
so
it
was
tenderfeet
weekend.
Building
this
bridge
across
the
canyon
they're
gaining
consciousness
of
their
incompetents
they're
learning
to
identify
where
and
what
they
don't
know.
That
redditor
recognizes
there's
pieces
of
understanding
their
missing,
but
they
can't
quite
identify
what
those
pieces
are.
A
This
halfway
point
between
unconscious
and
competence
and
conscious
incompetents
is
where
a
lot
of
those
Oh
or
the
moments
start
to
happen.
Raven
Covington
told
me
about
one
of
those
first
moments
she
encountered
where
she
said:
I
didn't
realize
how
easily
you
can
type
something
wrong
and
break
your
program.
A
Zedge
Hall
describes
those
that
necessary
repetition,
she's
performing
and
the
intro
of
this
book
series
learn
code.
The
hard
way
he
says
keep
at
it
force
yourself.
If
you
run
into
something
you
don't
understand,
skip
it
come
back
to
it
later,
just
keep
going
because
with
programming
there's
this
very
odd
thing
that
happens
at
first.
You
will
not
understand
anything.
Then
one
day,
bang
your
brain
will
snap
and
you
will
suddenly
get
it.
A
So
some
of
this
repetition
can
get
a
little
lonely,
but
there
are
things
she's
just
going
to
have
to
learn
on
her
own
she's
gonna
have
to
have
her
own
moments
of
oh
and
she's,
counting
on
that
bang
now
I
get
it.
That
said,
Shaw
promises
so
with
each
of
these
moments
that
she
encounters
she's
into
Norway
across
the
canyon,
she's
learning
what
she
has
to
learn.
A
So
her
heads
down
she's,
focusing
on
all
the
basses.
She
asked
a
bar
she's
getting
steadily
across
the
bridge.
She
now
has
vocabulary
tools,
resources
and
the
ability
to
ask
better
questions
all
in
her
knapsack.
She
has
people
on
the
other
side
to
answer
her
questions
and
she
sees
a
goal.
The
mountain
is
in
sight,
so
she'll
have
to
continue
barring
the
bars,
but
by
the
time
she
reaches
the
other
side
of
the
canyon.
She
has
more
informed
questions.
A
She
wonders
what
happens
if
I
pass
the
bar,
how
bad
is
Abbas,
izle
I
know
I
needed
a
north,
but
what?
If
I'd
used
to
whom
she
might
not
even
understand
the
answers
to
these
questions?
But
that's
for
the
next
stage
of
learning.
That's
what
will
help
propel
her
further
up
the
mountain,
so
she's
not
just
take
her
first
step
into
the
safer
brighter
side
of
the
canyon
she's
got
community
she's
got
people
to
learn
with,
so
everyone
was
just
very
happy.
A
What
does
this
look
like
in
the
real
world?
Well,
you've
probably
seen
that
image
I
know,
you've
probably
definitely
seen
this
image.
This
is
what
it
looks
like
in
the
real
world
and
it
doesn't
look
super
great.
But,
what's
worse
is
how
it
feels
when
you
fall
into
one
or
even
several,
of
one
of
these
underrepresented
categories.
A
When
someone
falls
into
those
categories,
they
don't
necessarily
see
someone
as
a
beacon
of
success,
so
they
don't
have
someone
to
immediately
go
to
to
ask
a
question
very
comfortably,
so
they
might
not
even
ask
Stephanie
McGee
apai
Herrara.
Think
I
said
that
correctly.
Will
she
wrote
about
the
importance
of
seeing
people
early
in
the
learning
process?
She's
a
prospective
and
current
students
need
to
be
able
to
see
people
like
them
in
interview
rooms
and
in
classroom
podiums.
A
She
says
that
every
level
of
those
organizations
from
boardrooms
HR
and
the
value
of
this
kind
of
presence
is
immeasurable.
Knowing
that
that
kind
of
presence
is
all
too
rare.
Many
established
previous
pioneers
are
working
to
improve
this
Dominic
M
liddell
founded
coding,
while
black,
because
he
kept
hearing
people
say
well
if
we
could
find
them,
we'd
hire
them
and
he
wanted
to
say
no.
We
are
here
and
we
want
you
to
find
us.
A
So
once
you
arrive,
you
see
no
one,
the
joy
that
someone
might
feel
when
they
do
see.
Someone
is
huge,
there's
this
blog
post
by
Ashley
Nelson
Hornstein,
but
I
really
love
where
she
talks
about
discovering
a
new
hero.
Annie
Jean
easily.
Does
anyone
who
she
is
nope
alright?
So
she
was
an
African
American
computer
programmer
who
worked
for
what
would
become
NASA,
wasn't
even
NASA
yet
in
the
1950s
through
the
80s,
and
actually
she
learned
about
energy
and
easily
on
Twitter
and
just
couldn't
get
enough.
A
She
just
was
consuming
information
and
talking
to
everyone
about
her
that
she
says
having
visible
examples
of
people
that
look
like
you,
an
aspirational
professional
field
is
powerful
by
merely
existing.
These
examples
prove
that
there's
an
achievable
pathway
to
that
field,
actually
talk
to
her
friends
about
Easley's
life
and
even
got
to
meet
dr.
Yvonne
Cagle,
who
NASA
astronaut
and
when
Ashley
told
dr.
Cagle
about
easily
and
showed
her
photo.
She
said
dr.
A
A
A
So
I
actually
feel
like
this
conference
has
done
a
really
good
job.
I,
don't
know
if
anyone
I've
seen
a
few
tweets
about
people
really
praising
the
diversity.
But
what's
important
to
me
is
I've
seen
diverse
attendance,
but
I've
also
seen
diverse
speakers
and
that
stuff,
really
matters
affinity,
groups
and
events
like
black
girls
code
alter
comp
and
railsbridge.
They
help
members
of
underrepresented
groups
find
familiar
faces
and
act
as
beacons
to
help
guide
and
encourage
people
and
pioneering
tender
feet
across
the
canyon.
A
And
are
we
from
our
Mountain
of
competence,
sending
the
right
messages
and
responses
to
these
new
would
be
members
of
our
community,
whether
they're
a
pioneer
or
not?
Each
method,
we
craft,
whether
in
person
or
online,
should
recognize
the
relative
difficulty
of
the
journey
they've
begun
and
with
each
well
crafted
message:
interaction,
we're
helping
tenderfeet
bridge
that
treacherous
Canyon,
while
helping
them
overcome
that
first
major
obstacle
and
their
learning
path.
A
So,
with
each
bridge
built
our
mountain
community
grows
and
with
each
bridge
built,
we
gain
traveling
companions
with
different
experiences
and
different
skill
sets,
because
upcoming
obstacles
we
might
face
might
be
completely
new
to
you
or
me,
but
might
be
something
familiar
to
one
of
these
new
developers.
So
with
that
shared
and
indifferent
experience,
we
can
solve
new
and
exciting
problems
together.
We
just
have
to
get
them
across
first.
So
thank
you
very
much.
A
I
want
to
say
thanks
to
tambo,
she
was
my
coworker
at
one
point
and
she
worked
with
me
on
the
illustrations
and
she
is
a
pioneering
bridge
builder
herself,
so
she's
awesome
check
her
all
on
Twitter
and
see
what
she's
up
to
she's
always
doing
something
new,
and
if
you
want
to
stay
in
touch,
here's
my
information.
I
work
at
milton
I'm
engineering
manager
in
Atlanta
and
I'm,
a
co-organizer
of
a
monthly
meetup
called
girls,
girls
Atlanta.
We
also
do
a
workshop
just
here
and
there
and
we've
had
a
few
pretty
awesome
success
stories.