►
From YouTube: The heart of npm - CodeConf 2016
Description
Presented by Stephanie Snopek
npm, Inc., is a small company with a big heart and an even bigger community of users. We support the JavaScript community by running a free open source registry of modules built by developers like you. Along the way, our users need help debugging errors, understanding documentation, and resolving conflict with their peers. In this talk, we'll explore the strategies we use at npm, Inc., to support the global, diverse, passionate & growing community of Node.js developers and npm users.
About CodeConf
CodeConf improves the software community by providing a forum for thought-provoking talks and forging social connections. The fourth installment of the CodeConf series took place in Hollywood in 2016. This year's event focused on systems engineering projects, practices, and programs in the open source community.
For more information on this year's CodeConf, go to:
https://codeconf.com/
A
Hi
everybody
how
you
doing
today,
I
hope
you
doing
great
I,
wanted
to
say
a
quick
thank
you
to
the
code,
comp
organizers
for
putting
on
such
an
amazing
event
and
inviting
me
to
speak
with
all
of
you.
The
venue
is
amazing.
It's
really
really
great,
so
I
mean
I'm
here
to
talk
about
the
heart
of
NPM.
That's
my
talk,
and
so
let's
get
started
here.
A
Ah-Ha
there
you
go
okay,
so,
let's
start
with
who
am
I
why
you
here
listening
to
me?
My
name
is
Stephanie
snowpack
like
Chris
mentioned
I,
do
support
an
NPM,
so
you
know
I'm,
really
interested
in
technology
excited
to
be
in
Silicon
Valley.
You
know,
San,
Francisco,
environment
I
have
been
doing
support
for
about
seven
years
and
I'm
Canadian,
just
fun
fact:
I'm
also
really
really
a
huge
fan
of
ice
cream.
A
So
if
anybody
has
any
tips
on
where
the
best
ice
cream
in
Elias
I
would
love
to
hear
that
so
I
realized
that
not
everyone
may
not
know
what
NPM
is
so
NPM.
First
of
all
we're
a
team
of
wombat.
The
sir
is
our
mascot.
It's
a
really
great
little
creature
from
Australia
I'm,
not
entirely
sure
how
we
got
to
the
wombat
mascot,
but
it's
kind
of
a
nice
representation
of
on
the
team.
A
We
are
really
friendly,
really
approachable,
I
think
we're
pretty
adorable
and
although
we
may
be
bumbling
at
some
points,
I
really
have
the
best
intentions.
Side.
Note:
if
anybody
wants
any
of
these
wombat
stickers
I
have
this
collection
in
my
bag.
So
let
me
know,
after
the
talk
and
I'll
be
happy
to
supply
some
for
you,
but
mph
is
also
a
registry
of
code.
It
is,
it
was
started
as
this
public
open
source
project
for
people,
primarily
nodejs
developers,
JavaScript
developers
to
upload
share
their
modules.
A
So
right
now
we
have
about
300,000
modules
in
your
registry
really
really
interesting,
big
number
there.
The
CLI
is
also
a
big
part
of
NPM
and
it's
the
tool
that
enables
people
to
actually
install
and
publish
their
own
modules
to
this
open
source
registry,
and
it's
really
great
rate,
really
great
tool,
and
it's
also
a
website
NPM
is
it.
Has
we
have
a
great
website
where
our
users
can
go
and
take
a
look
at
what
modules
exist?
You
can
see
how
many
people
are
using
them.
You
can
see
how
many
people
contribute
to
them.
A
You
can
get
link
to
their
github
account
there
up
the
profiles
and
even
contribute
you
can
reach
out
to
them
and
find
a
way
found
out
how
you
can
help
contribute
to
their
modules
and
a
fun
fact
is
that
NPM
doesn't
actually
stand
for
anything
it's
commonly
referred
to
as
the
node
package
manager,
but
it
doesn't
stand
for
that.
So
we
have
a
bunch
of
extensions
that
people
contribute
to.
A
If
you
think
of
something
funny,
some
something
funny
the
NPM
might
mean
we'll,
probably
enjoy
it,
and
you
can
actually
contribute
your
own
suggestion
for
what
NP
incentives
for
nasal
pathway,
melodrama,
pretty
hilarious,
and
so
my
job
is
to
help
users
with
all
of
these
tools.
So
anybody
who
has
questions
about
the
CLI
or
has
questions
of
the
registry
have
noticed
bugs
on
the
website,
potentially
or
in
general
they're,
interacting
with
all
of
these
different
pieces
of
NPM,
and
they
need
assistance.
That's
where
I
come
in!
Oh
it's!
Okay!
It's
a
lot
of
stuff!
A
It's
totally
fine,
totally!
Fine!
It's
a
lot
to
learn,
but
it's
totally
fine.
So
what
we're
going
to
get
into
some
of
the
more
the
interesting
big
numbers
and
a
start
up,
you
know
we're
all
kind
of
trained
or
conditioned
to
really
enjoy
graphs
that
go
up
into
the
right.
Eight
telling
me
something
really
good.
Let's
take
a
look
at
some
numbers
related
to
NPM.
A
We
asked
me
about
4
million
developers
on
a
thousands
of
companies
are
using
NPM
based
on
is
hitting
the
rent
in
the
registry,
who's
checkin
at
the
website,
and
that's
a
lot
of
people.
That
is
a
lot
of
people
looking
at
download
how
many
people
are
downloading
these
modules
we're
hitting
a
billion
mod
billion
downloads
of
Meek.
Nowadays,
that's
a
lot
of
problems,
and
so
taking
a
look
at
that
graph
over
time
I
joined
you
can
see.
A
A
A
This
is
happening,
it's
totally
cool,
okay,
so
those
are
all
great
things
to
know
about
NPM,
it's
a
really
amazing
tool,
but
at
the
end
of
the
day,
these
numbers
are
representation
of
human
interaction,
with
what
we're
building
what
we're
creating.
So
my
job
is
to
remember
that
to
remember
that,
yes,
NPM
is
an
amazing
tool
for
developers
and
we
offer
a
lot
of
amazing
services
to
people
like
you,
but
at
the
end
of
the
day,
a
lot
of
people
need
help
using
them
and
I
have
to
remember
the
humanity
behind
that.
A
So
what
does
that
look
like?
My
job
is
really
connected
to
tickets
and
tweets.
So
we
deal
that
with
about
600
ish
tickets
a
month
spread
out
between
me
and
my
colleagues.
I
have
two
amazing
support.
Colleagues,
so
we
each
take
our
portion
of
that.
We
don't
get
too
many
tweets
to
the
NPM
support
handle,
but
it's
definitely
there
and
we
are
always
there
to
help
you.
If
you
have
quick
questions
or
you
notice,
something
is
going
on
NFC
tracker,
so
this
is
something
that
we're
trying
to
dive
into
a
bit
more.
A
It's
kind
of
intimidating,
though,
because
right
now
we
have
852
open
support
issues.
Those
are
the
most
type
of
support
and
those
are
the
ones
we're
trying
to
deal
with
and
that's
from
the
couple
years.
So
if
anybody
has
suggestions
or
tips
for
how
to
deal
with
an
issue
tracker
of
this
magnitude,
please
tell
me
I'd
love
to
hear
you
tips
help
me
help
you
write
and
then
there's
other
support.
A
So,
yes,
my
full-time
job
is
to
deal
with
tickets,
primarily
and
whatever
tweets
go
out
there,
but
we
have
other
people
in
the
team
in
the
companies
that
also
contribute
to
supporting
users
in
a
variety
of
ways.
So,
for
example,
the
CLI
team
has
been
doing
this
thing
where
they
invite
users
to
come
to
their
meetings
where
they
talk
about,
what's
going
on
as
a
CLI.
What's
coming
up
next,
what
are
the
issues
that
they're
focusing
on
and
you
can
voice
your
questions
or
your
concerns,
and
so
that's
really
great.
A
We
also
have
some
pretty
extensive
documentation
on
how
to
use
all
this
and
how
to
use
the
CLI
and
where
to
go
next,
if
you
have
a
goal,
documentation
is
there's
a
lot
of
it
and
it's
primarily
the
responsibility
of
one
of
my
colleagues
Ashley.
She
does
a
great
job
of
it,
but
because
there's
so
much
that
gets
updated
and
changes
over
time.
She's
actually
created
this
great
initiative
where,
if
you
are
reading
the
documentation-
and
you
know
that
something
is
wrong
or
it
needs
to
be
tweaked,
there's
something
that
he's
editing.
A
She
has
encouraged
people
to
submit
PRS
socks
for
docs.
So
if
you
submit
a
change
to
the
docs
and
it
gets
accepted,
we
will
send
you
socks,
really
cool
wombat
socks.
Okay,
so
I
encourage
you
to
check
it
out.
It's
a
really
good
way
to
get
involved
with
contributing
to
this
giant,
open
source
project,
but
I
think
at
the
end
of
the
day.
That's
what
makes
NPM
so
unique.
The
fact
that
everybody
on
the
team
is
so
committed
to
to
supporting
users.
A
I
forgot
to
mention
you
know:
engineering
calls
for
people
who
are
really
struggling
with
something
primarily
for
our
paid
customers,
I'm
getting
them
up
and
running
and
then,
of
course,
the
Status
page,
which
is
maintained
primarily
by
the
registry
team.
So,
if
any,
if
there's
any
outage
in
service
or
something
going
on
that,
people
need
to
know
about
they're
responsible
for
that
and
that's
what
makes
NPM
so
unique.
A
In
my
experience,
it
is
such
an
incredible
thing
to
know
that
the
whole
company
wants
the
support
users
in
such
an
important
way,
and
they
all
have
their
different
avenues
for
doing
that.
The
other
thing
that's
really
great
is
that
people,
the
folks
at
NPM,
the
folks
in
my
colleagues
for
about
a
year,
are
really
intentional
intentional
about
their
communication
and
that
that's
really
I
think
that's
really
special.
A
That's
that's
the
great
thing
we're
going
to
explore
a
bit
more
because
what
is
communication
I'm,
a
communication,
nerd
I,
do
that
that's
my
full-time
job,
right,
I
communicate
with
people.
But
what
that
means
is
it's
a
successful
conveying
or
sharing
of
ideas
and
feelings.
Ideas
are
create.
Feelings
are
also
part
of
our
world.
We
have
to
convey
them
both
and
it's
also
a
way
to
connect
with
people.
A
So
when
you're
thinking
about
supporting
your
open-source
users,
you're
really
trying
to
connect
the
dots
with
these
ideas
and
feelings
you're
having
about
whatever
is
going
on
and
they're
having
these
same
ideas
and
feelings.
Potentially,
you
want
to
build
a
bridge
between
you,
two
and
connect
with
them.
That's
what
communicate!
That's
the
bowl
of
communication,
it's
very
simple,
simple
definitions,
but
I
really
enjoy
kind
of
getting
back
to
the
foundation
of
that
that's
sort
of
what
that's.
What
support
is
right.
A
Like
I
said
it
is
communication
and
for
me
it's
primarily
written
like
I,
said
ticket
writing
them
out
a
lot
a
lot
of
times,
though,
there's
a
visual
and
symbolic
communication
that
goes
on,
for
example,
emoji
right
if
you're,
not
sure
that
your
words
are
really
hitting
the
mark,
you
can
use
emoji
to
represent
the
intent
behind
what
you
are
saying,
and
it's
very
easy
for
us
to
kind
of
dismiss
this
communication
thing
as
a
soft
skill.
It's
super
easy
right.
Everybody
can
communicate.
It's
really
easy
right.
No,
it's
not
that
easy.
A
A
You
know,
empathy
is
the
ability
to
put
yourself
in
your
users
shoes.
So
when
somebody
comes
to
you
with
an
issue
taking
a
moment
to
say,
oh
wow
they've
mentioned
this
issue.
Where
is
it
coming
from
like?
Why
are
they
feeling
this
way?
What
has
created
the
environment
where
they're
responding
to
me
in
such
a
way?
It
empowers
you
to
connect
with
them
a
lot
better
if
you
can
try
and
identify
with
them,
rather
than
kind
of
look
at
them
from
above
and
be
like.
A
Oh
yeah,
that's
something
going
on
no
trying
to
put
yourself
in
their
shoes,
it's
something
that
requires
a
lot
of
practice.
It's
not
again,
it's
not
an
easy
thing.
A
lot
of
us
have
had
challenges
with
emphasizing
and
that's
okay,
it's
something
that
has
to
be
practiced
and
when
I
say
flex
your
empathy,
it's
like
a
muscle,
just
like
any
other
muscle
right.
You
have
to
actually
use
it
to
make
it
stronger,
so
anyone
can
can
get
better.
A
A
Maybe
we
will
talk
about
that
so
another
strategy
when
you're
communicating
with
users
and
let's
say
you're
you're
interacting
with
somebody
who's,
really
upset
right.
You,
you
have
a
user
who's
talking
to
you
on
your
issue,
tracker,
trying
to
use
what
you
built,
they're,
really
mad
and
there's
think
about
your
mean
things
and
rude
things
is
kind
of
getting
your
ire
up.
You
know,
you're,
like
I,
actually
built
something
amazing
and
you're,
not
using
it
properly.
What's
your
problem
right,
it's
easy
to
jump
to
that
conclusion,
but
just
don't
take
it
personally.
A
You
know
it's,
yes,
you
are
all
amazing
people,
I'm
sure
you
are
making
amazing
tools,
you're,
contributing
greatly
to
the
technology.
Industry.
I
have
no
doubt
you're
doing
a
great
job
in
many
ways,
but
for
most
people
in
the
world
they
don't
know
you,
they
don't
know
what
you're
working
on
and
they
don't
know
what
you
care
about
for
most
people
you're
just
the
name
associated
with
whatever
you
built
right.
Unless
you
have
a
really
great
personal
connection,
with
most
of
your
users,
I
mean
looking
at
NPM.
A
I
can't
connect
to
4
million
people,
that's
impossible,
so
I
do
the
best
that
I
can,
with
the
interactions
that
we
do
get
and
so
I'm
not
taking
it
personally
and
being
able
to
look
past
that,
like
issues
not
about
you,
it's
something
about
what
they're
using
and
you
have
the
solution.
So
you
know,
take
a
moment,
breathe
and
then
continue
to
tackle
it.
A
A
We
we
are
often
conflict
avoidance.
We
don't
like
to
go
towards
conflict
you're
like
Oh
somebody's
fighting,
somebody's
angry
at
us,
you're
gonna,
just
walk
over
here,
run
away,
ok,
bye
and
that
doesn't
really
help
anything.
It's
really
important
to
kind
of
become
a
little
bit
more
comfortable
with
the
idea
of
Consulate
and
especially
if
you're,
in
a
position
of
mediating
an
issue.
Let's
say
two
users
are
having
this
really
really
challenging
interaction
and
you're
supposed
to
be
the
mediator,
because
you
know
you're
in
charge
for
some
reason
and
you
have
to
deal
with
it.
A
It's
okay
I
mean
you
can
let
them
talk
about
it.
That's
fine!
You
don't
have
to
get
in
there
and
tell
people
to
calm
down,
don't
look
how
people
calm
down.
Have
you
ever
calm
down,
because
somebody
has
told
you
to
calm
down
I
have
not
it's
nobody
likes
hearing
that
and
it
doesn't
really
help.
So
if
you
are
mediating
consult
in
some
way,
you
don't
really
have
to
go
into
the
nitty-gritty
of
why
people
are
feeling
a
certain
way.
You
can
just
validate
and
say:
hey.
You
know.
This
is
a
really
frustrating
situation.
A
A
Another
strategies
that
you
might
consider
is,
you
know
again,
you're
all
really
smart
people,
you
all,
have
really
great
talents.
You
are
working
on
amazing
things,
but
you
don't
know
everything
right
and
even
if
you
do
think
you
know
exactly
what's
going
on
it's
okay,
to
ask
questions.
Sometimes
that
is.
Is
it's
such
an
important
step?
A
We
overlooked
because
we
think
we
have
the
answer
already,
but
from
a
support
perspective,
even
though
it's
easy
to
jump
into
the
solution,
it's
sometimes
extremely
frustrating
I,
don't
know
if
you've
experienced
this
but
I
know
I
have
when
you
reach
out
to
somebody
and
you're
like
I.
Have
this
issue
what's
going
on
tonight?
I,
don't
get
it
help
me
and
they're,
like
oh
yeah,
I
know
exactly
what's
happening.
Here's
the
solution,
she's
a
bunch
of
information
done
right
and
it's
a
complete
roll
in
solution
for
you,
it's
not
really
what
you're
struggling
with.
A
So,
if
there's
any
ambiguity-
or
you
really
just
want
to
make
sure
you're
clear
that
you
understand
what's
happening,
ask
questions,
that's
not
to
assume
you
know.
Everything
carrying
on
support
can
be
really
challenging.
Like
this
whole
communication
thing,
it's
so
energy
intensive
and
to
be
able
to
take
a
step
back
and
say:
oh
I
have
to
identify
with
you
and
then
I
have
to
not
take
what
you
said
personally
this
conflict,
so
I
got.
A
If
you
was
that
responsibly,
okay
and
then
I,
you
know
all
of
these
things-
take
a
lot
of
energy
and
I
enjoy
it.
That's
why
I
work
in
support?
It's
really
fun
to
be
able
to
solve
problems
with
people
fight
in
open
source,
especially
if
you're
not
getting
paid
for
it.
You
got
to
recognize
when
you
need
a
break
when
you
need
to
take
a
moment
to
slow
down.
If
you
notice,
you're
hungry,
you
know,
take
a
break,
get
a
snack
get
some
water.
A
So
this
one's
a
bit
harder
because
apologies
are
very
rough
sometimes
but
I
would
really
recommend
you
get
a
bit
more
practice
in
apologizing
when
things
go
wrong
and
if
you
are
responsible
for
that
I
know
it's
really
hard,
sometimes
because,
especially
in
the
tech
industry,
there's
so
much
hinging
on
this
idea
being
right.
You
want
to
make
the
right
decision
for
your
product.
You
want
to
make
the
right
decision
for
your
team.
A
You
want
to
make
the
right
decision
that
helps
your
company
grow
or
your
your
tools,
your
open
source
project
grow,
but
sometimes
hits
the
fan
right.
That's
just
the
honest
truth,
and
one
of
one
of
the
things
that
I
learned
in
support.
You
know
you
can't
sugarcoat
everything
I'm
a
really
positive
person,
I
like
to
sugarcoat
things.
Sometimes
like,
oh
yeah,
that's
really
I'm
sure
is
unfortunate.
You
know
it's
kind
of
a
irritating
right
now,
sometimes
it's
terrible.
A
Sometimes
things
are
not
working
well
and
if
you're,
if
you're
playing
a
role
in
that,
it's
really
important
to
recognize
that
you
know
sometimes
just
have
to
say
I'm.
Sorry
I
realized
that
I
made
a
mistake.
I
understand
that
this
is
impacting
you
really
negatively
and
I'm
going
to
do
better
next
time,
but
you
can't
have
any
expectation
at
the
end
of
the
day.
A
You
can't
expect
that
your
apology
will
make
everything
better,
because
it
won't
necessarily
it's
really
nice
steps
cake,
but
it
doesn't
solve
everything,
so
don't
have
any
expectations
really
at
the
end
of
the
day.
What
we're
talking
about
here
is
communication
right.
Communication
is
supposed
to
lead
to
a
connection
of
some
sort
right.
You
are
connecting
with
your
users
you're
connecting
with
your
team
and
when
people
feel
that
really
great
sense
that
you're
listening
you're
validating
them,
you
you
want
to
help
them
out
you're
committed
to
doing
better.
A
That
connection
multiplied
over
time
leads
to
community
a
sense
of
community
that
you
can
talk
with
people.
They
will
be
there
to
help.
You
and
I
think
this
is
really
important,
especially
as
our
communities
are
growing
and
changing.
We
have
to
recognize
that
our
communication
has
to
change
and
adapt
as
well.
We
have
to
listen
to
especially
people
who
are
in
marginalized
groups,
people
who
feel
like
outsiders.
A
If
people
are
coming
to
you
and
they
say,
look
I
want
to
join,
but
I
feel
bad
about
this
thing
like
can
we
change
it
change
it
if
at
all
possible
change
it,
and
if
you
can't-
and
you
should
have
a
really
good
reason
for
not
doing
that
if
you're
not
really
the
person
primarily
responsible
for
supporting
your
users,
I
would
really
encourage
you
to
give
your
support
team
that
love
and
resent
and
recognition
for
the
amazing
job
they're
doing
somebody
has
to
do
it
right.
Somebody
has
to
connect
to
this
to
users.
A
Somebody
has
to
be
there
to
solve
the
problems.
If
it's
not
you,
somebody
else
is
doing
it
gives
them
that
kudos
give
them
that
recognition
understand
that
their
job
is
not
as
easy
as
you
think.
Maybe
maybe,
if
you
think
that
way,
it
can
be
a
real
challenge,
turn
of
emotional
labor
and
it's
it
is
enjoyable.
A
There
are
a
lot
of
rewards
to
it,
but
it
is
challenging
so
give
your
support
team
what
they
need
to
do
successfully
right,
give
them
the
tools
they
need
to
address
these
issues
and
yeah
just
support
your
support
team
at
the
end
of
the
day,
if
you
get
anything
from
this,
I
hope
it's
that
NPM
love
view
we're
a
bunch
of
really
cute
approachable
wombats.
If
you
have
any
questions
about
NPM,
please
let
me
know:
I
will
be
at
the
back
of
the
room.
A
You
can
ask
for
the
stickers
and
ask
questions
about
NPM
other
thing,
if
you,
if
you
are
having,
if
you're
noticing
your
community
is
growing,
your
community
of
users
growing
really
be
mindful
of
the
strategies
that
you're
using
to
connect
with
them
and
whenever
you
can
adapt
your
your
communication
strategies
and
at
the
end
of
the
day,
if
that's
not
you
it's
your
support
team,
so
give
them.
The
lovely
deserves
they're
working
hard
for
you.
Thank
you.
So
much
for
being
here.
Thank
you
for
listening.
I
hope.
You
have
a
wonderful
time
in
LA.