►
From YouTube: Keynote: Creating a Holistic Developer Experience - Jasmine James, Engineering Manager, Twitter
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Keynote: Creating a Holistic Developer Experience - Jasmine James, Engineering Manager, Twitter
A
Well,
my
name
is
once
again
jasmine
james,
I'm
an
engineering
manager
at
twitter.
I
lead
the
developer
experience
pillar
within
our
engineering
effectiveness
organization.
What
that
means
is
that
I
get
to
engage
with
internal
developers
to
understand
their
challenges
and
pain,
points
specific
to
documentation,
internal
tool,
support
and
the
local
development
environment.
A
Over
my
career,
I've
worked
at
multiple
companies
where
I've
implemented
new,
tooling
and
capabilities
to
solve
very
specific
problems.
Everything
from
version
control,
artifact
repository
ci
processes,
using
tools
like
jenkins,
the
whole
point
of
doing
that
was
to
speed
up
the
business
or
delivery
of
business
value
as
we
implemented
specific
capabilities,
some
of
the
problems
remained
the
same.
The
interaction
with
the
tools
had
not
changed.
A
A
So
what
I
realized
is
that
until
you
consider
the
entire
workflow
experience,
anything
we
did
would
have
limited
impact
so
change
the
approach.
Instead
of
focusing
on
those
small
issues
focused
on
what
really
mattered,
the
entire
development
workflow
and
its
impact
to
people
so
today
I'll
be
sharing
some
of
the
learnings
that
I've
gathered
as
an
end
user
supporting
developers
through
tooling
capabilities
I'll
highlight
some
key
methods
that
you
can
use
to
create
a
more
holistic
and
people-centered
developer
experience.
A
A
So,
as
we
saw
it's
not
going,
all
that
well,
janice
is
having
issues
finding
the
right
direction
in
her
new
environment
at
our
old
company,
janice
was
a
lead
that
helped
define
that
developer
workflow
by
collaborating
with
the
many
infrastructure
and
platform
teams
that
own
those
tools
and
services.
So
she
definitely
has
an
idea
of
how
things
could
be
better
like
janice
over
the
past
year.
The
one
constant
that
we've
all
experienced
is
change.
A
This
may
have
manifested
in
many
ways
maybe
you're
working
at
a
new
location,
perhaps
you're
working
in
a
different
role
or
even
a
different
company,
or
you
could
be
like
me
and
be
doing
all
three
of
those
things
there's
also
those
of
us
who
are
working
in
the
same
tools
in
the
same
environments,
but
either
way.
I
think
we
all
can
agree
that
the
pain
points
within
the
developer
workflow
have
become
quite
amplified,
given
the
level
of
changes
that
we've
experienced.
A
A
Before
I
highlight
the
pillars
I
want
to
introduce
you
to
the
developer
happiness
meter
1.0,
as
we
work
diligently
with
janice's
organization
to
improve
her
experience,
will
be
able
to
see
how
it
impacts
her
in
real
time
cool
right.
So,
let's
dive
right
in
here
are
those
four
pillars:
discoverability
usability
capabilities
and
the
ever
important
stability
I
love
acronyms.
So
I
was
very
pleased
that
it
made
one
when
I
was
as
I
was
making
this
presentation.
A
These.
These
topics
are
probably
not
unfamiliar
with
you.
Constant
just
constance
just
talked
about
how
we
need
to
look
at
the
tools
that
developers
use
as
a
product
as
products
in
general
are
developed.
The
user's
experience
or
ux
is
considered
greatly
because
it
could
be
the
differentiating
factor
between
them
using
your
product
or
competitors
and
a
ux
isn't
necessarily
a
gui.
It
could
be
a
command
line,
the
configuration
of
a
tool
or
even
documentation,
since
this
concept
is
so
important
to
external
facing
products
for
customers
to
drive
revenue.
A
Why
not
take
the
same
approach
to
developer
experience?
So,
as
I
walk
through
these
I'll,
be
highlighting
some
methodologies,
you
can
use
to
get
a
better
understanding
of
the
current
state
within
your
environment
metrics.
You
can
track
as
you
improve
it
and
core
deliverables
that
I've
seen
with
my
own
eyes
improve
this
area.
I'll
also
call
out
some
cncf
projects
that
can
contribute
to
improvements,
but
it's
important
to
note
that
tools
cannot
be
the
only
thing
to
consider
here.
A
A
The
next
thing
we
can
do
is
track.
Metrics
metrics,
like
onboarding
time
customer
satisfaction
or
even
how
quickly
folks
are
deploying
things
are
great
ways
to
measure
improvements
on
discoverability
some
core
improvements
that
I've
seen
work
are
single
sourcing,
which
means
that
you're
having
one
point
of
reference
for
guidance,
templates
and
hubs
are
great
ways
to
do
this.
This
reduces
the
toil
within
the
developer,
experience
of
discovering
new
and
relevant
information.
A
A
A
A
It
looks
like
janice
is
working
on
a
yaml
file.
She
was
looking
in
her
environment
for
a
clear
example
of
how
she
could
deploy
her
machine
learning
model
into
the
kubernetes
cluster.
She
couldn't
find
one,
so
she
did
what
any
developer
would
do.
She
got
one
from
the
internet
as
she
moved
it
into
her
environment.
She
unfortunately
has
a
typo
she's,
trying
to
figure
out
why
it
won't
why
it
won't
deploy.
A
A
The
first
thing
that
we
can
do
to
get
a
better
understanding
of
usability
is
run
usability
testing,
so
usability
testing
means
defining
tasks
and
giving
them
to
a
participant
to
complete.
There
are
two
types
of
tasks:
open
ended
and
closed,
ended.
Open-Ended
tasks
are
flexible
and
designed
with
minimal
explanation.
A
These
are
good
at
identifying
bottlenecks
within
your
process
or
elements
that
confuse
users.
So
a
good
open-ended
task
for
janus
would
be
to
hey
scale.
Your
deployment
to
three
replicas
and
janus
would
go
about
doing
that
during
the
test.
Close-Ended
tasks
are
very
specific
and
goal
oriented
and
they
are
based
on
the
idea
that
there
is
only
one
correct
answer.
A
These
are
great
for
testing
specific
elements
such
as
use
these
steps
in
cube
cuddle
to
create
two
replicas
very
specific
right
for
usability.
There
are
two
main
metrics
that
I'm
identifying
the
success
rate,
which
is:
what
is
the
percentage
that
the
user
is
having
or
what
is
the
percentage
of
success
that
the
user
is
having
when
trying
to
use
that
when
trying
to
use
that
tool
for
a
specific
purpose?
Ideally,
this
would
be
at
100,
but
that's
not
the
case
for
janus
right
now.
The
next
one
is
time-based
efficiency.
A
This
is
the
average
time
it
takes
to
complete
the
task
as
far
as
improvements
core
improvements
to
implement
for
usability
golden
paths
are
a
great
way
to
reduce
the
barrier
of
entry.
Investing
in
automation
is
an
obvious
one.
This
greatly
improves
the
success
rate
and
error
prevention.
Introducing
things
like
linters
are
a
great
great
way
to
prevent
users
from
failing
to
accomplish
what
they
set
out
to
do.
A
Helm
is
an
awesome
tool
to
leverage
that
allows
for
reuse
of
a
single
helm
chart
which
which,
which
improves
time-based
efficiency
and
automation,
which
greatly
improves
success
rate.
A
All
right
so
janice
is
out
of
the
red,
which
is
a
good
thing.
We
still
have
a
ways
to
go,
though,
so,
let's
take
a
look
at
capabilities
in
this
next
scenario.
Janice
is
trying
to
find
capabilities,
specific
to
mean
machine
learning
within
her
environment,
but
everything
that
she's
seeing
is
targeted
for
a
back-end
developer,
not
a
good
feeling.
How
can
we
improve
this?
A
The
first
thing
we
can
do
is
journey
mapping
journey
mapping
is
a
process
that
is
used
frequently
for
external
customers
and
in
the
book
developer
relations
how
to
build
and
grow
a
successful
developer
program
by
caroline
lucco
and
james
partner.
Highly
recommend
a
developer
journey
map
is
defined
as
a
visual
visualization
that
identifies
the
path
developers
follows
and
experiences.
A
The
goal
of
the
map
is
move
to
move
the
developer
from
left
to
right
as
quickly
as
possible,
but,
as
you
go
about
that,
you
can
identify
gaps
within
your
offerings
to
measure
capabilities.
Customer
satisfaction
is
the
best
signal.
As
far
as
core
improvements,
the
obvious
one
would
be
to
just
provide
persona
map
capabilities.
A
It's
also
important
to
note
that
some
capabilities
can
be
used
across
personas,
which
also
helps
janus
accomplish
what
she
has
to
do.
An
example
of
this
is
linker
d,
linker
d,
decouples
services
from
having
to
know
about
the
network
and
provides
abstraction
of
network
code
from
the
business
logic,
which
means
that
janice
won't
have
to
worry
about
the
things
that
don't
really
matter
specific
to
her
business
logic.
A
A
In
this
scenario,
janice
is
attempting
to
deploy
and
it
looks
like
the
pods
are
not
spinning
up
in
her
kubernetes
cluster.
Unfortunately,
there
was
a
upgrade
last
night
that
did
not
go
so
well,
so
she's
trying
to
figure
out
what's
happening
every
time
the
build
is
failing
her
confidence
in
the
tool
decreases.
So
let's
look
at
ways
to
further
define
what
reliability
looks
like
in
janus
environment.
A
The
first
thing
we
can
do
is
take
a
look
at
incident
management,
data,
post-mortem
surveys
and
even
conduct
focus
groups.
Focus
groups
are
a
great
great
way
to
get
qualitative
responses
that
can
be
used
to
assess
developer
confidence
in
the
workflow.
This
real-time
engagement
can
also
serve
as
a
great
starting
point
to
probe
deeper
into
specifics
on.
What's
what
events
lower
the
developers,
confidence
in
the
tool
metrics
you
can
use
to
track
stability
are,
as
I'm
sure
you
all
have
gathered,
tool
and
capability
of
time.
A
Another
interesting
metric
is
mean
time
between
outages
to
improve
the
stability
within
the
environment.
Intentional
postmortems,
I
think,
are
very,
very
key.
How
many
of
us
have
had
incidents
that
have
resulted
in
things
that
we
know
could
fix
the
problem,
but
they
never
get
prioritized
and
actually
fixed,
so
prioritizing
those
things
are
very
important,
centralized
support
so
that
there's
a
channel
to
understand
what's
up
and
what's
down,
also
improves
developer
confidence
and
tools.
A
A
When
the
infrastructure
team
in
janus's
organization
uses
a
tool
like
litmus
to
validate
kubernetes
upgrades
and
benchmark
resilience.
The
developer
experience
improves
for
janus
by
way
of
greater
mean
time
between
outages
and
more
uptime,
which
means
she
can
deploy
when
she
needs
to
alright.
So
we've
done
it.
Janet
is
very
happy
with
her
developer
workflow.
A
The
organization
that
janus
is
a
part
of
approached
each
of
these
challenges,
with
an
empathetic
ear,
to
gain
understanding,
established,
metrics,
to
measure
improvements
and
implemented
capabilities
that
have
directly
improved
janice's
experience.
External
customers
developers
have
one
big
thing
in
common
they're
all
people
so,
as
you
think
holistically
about
improving
your
experience
for
developers
within
your
organization.
A
Think
about
who
you're
solving
for
before
the
how
before
I
end,
I
wanted
to
call
out
the
book
that
I
reference
if
you're
going
to
solve
this
problem,
definitely
read
this
book
that
came
out
in
this
past
september
and
also
the
one
thing
I
love
about
this
community
is
the
ability
for
us
to
connect
and
share
best
practices,
so
don't
hesitate
to
reach
out
via
these
two
methods
below.
Thank
you.