►
From YouTube: Keynote: Software Delivery and Developer Experience in the Age of Platform E... KellyAnn Fitzpatrick
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
Keynote: Software Delivery and Developer Experience in the Age of Platform Engineering - KellyAnn Fitzpatrick, Senior Industry Analyst, RedMonk
As developer velocity and productivity become increasingly important priorities to the business side of software production, we have seen more organizations attempt to address the developer experience gap: the disjointed experience that results from overwhelming choice and fragmentation of the tools and processes used to build and release software. One ascendant solution: the emergence of teams dedicated to engineering internal platforms that integrate these tools and processes so that application developers can focus their creative efforts on writing code. This talk covers some of the trends we are seeing in platform engineering and considers the often complex delivery setups involved when we are talking about systems engineered to help developers build and release software--systems that have to consider developers as both consumers and producers.
A
So
delighted
to
be
here
at
cdcon,
this
is
the
first
time
I
have
done
a
keynote,
not
my
first
keynote,
the
first
time
it
has
been
in
person
and
virtual
at
the
same
time,
so
welcome
to
all
of
you
who
made
it
to
austin
in
this
103
102,
degree,
weather
and
hello.
Also
to
those
of
you
who
are
joining
us
virtually
at
home.
A
I
will
try
to
remember
that
that
you
are
there
as
well
for
the
kind
of
audience
participation
part
of
my
talk,
and
some
of
you
are
looking
at
me
like
audience
participation
what
so
today,
I'm
talking
about
software
delivery
and
developer
experience
in
the
age
of
platform
engineering.
All
of
those
words
should
be
somewhat
familiar
to
you
and
a
little
bit
about
myself.
I
am
a
senior
analyst
at
redmonk,
which
is
a
developer-focused
industry.
A
A
A
You
can
find
me
on
twitter
at
dr
kellyanne
fitz,
and
if
you
get
to
my
profile
and
see
a
picture
of
a
dragon,
that
is
in
fact
me
because
you're
talking
about
personal
reinvention
and
yet
an
earlier
other
life,
I
was
a
medievalist
and
if
there
are
any
other
medievalists
at
cdcon
today,
come
find
me.
I
will
buy
you
two
drinks,
there's
not
that
many
of
us
out
here
out
there.
A
A
So
for
those
of
you
who
are
here,
I'm
going
to
ask
you
to
do
a
show
of
hands
for
those
of
you
who
are
joining
virtually.
I
have
put
on
my
twitter
profile,
like
pinned
to
the
my
pinned
tweet,
a
thread
with
a
series
of
twitter
polls
for
these
same
questions
so
feel
free
to
answer
them
in
that
way
or
not.
But
for
those
of
you
who
are
here
today
how
many
of
you
are
familiar
with
software
delivery,
you
started
with
an
easy
one
like
hands
up
all
right,
everyone
for
those
of
you
at
home.
A
A
How
about
developer
experience
or
devx
a
lot
of
hands
as
well,
but
I'm
going
to
say
perhaps
a
few
less
hands
than
for
software
delivery
and
then
finally
platform
engineering
again
a
lot
of
hands,
but
probably
probably
the
least
least
popular
answer
for
all
the
questions
that
I
asked
so
these
this
also
are
the
three
things
I
will
be
talking
about
today.
So
here
is
also
my
agenda,
which
I
made
interactive
somehow
again
teacher.
A
A
A
A
So
moving
on
to
developer
experience
and
kind
of
why
it
matters
the
experience
of
developing
software
and
all
the
different
things
that
kind
of
go
into
it.
This
is
something
that
we're
hearing
more
and
more
about.
You
know
out
there
in
the
industry,
especially
from
the
business
side
of
things,
which
has
kind
of
taken
up
developer
experience
as
something
that
is
important
as
a
priority
for
a
number
of
reasons.
A
A
Everyone
breaks
the
build,
but
as
the
kind
of
co-wood
pandemic
has
shown,
the
need
to
be
able
to
adapt
and
to
get
things
out
faster,
has
great
advantages
and
with
the
kind
of
introduction
of
the
idea
that
moving
fast
also
can
produce
better
software,
which
the
dora
report,
the
devops
research
and
assessment
kind
of
group,
has
kind
of
put
forward.
There's
been
this
like
larger
embrace
of
velocity,
and
it
has
almost
become
a
business
imperative
where
software
is
involved.
A
Along
with
velocity,
comes
this
idea
of
developer
productivity,
how
to
make
your
developers
as
efficient
as
possible,
and
even
though
those
first
two
might
sound
more
like
this-
is
a
business
driven
type
of
thing
as
a
developer,
you
might
feel
like
you're,
somehow
being
like
squeeze
for
as
much
work
as
you
can
possibly
get
out.
Developer
happiness
is
also
a
very
important
kind
of
concept
out
there,
as
grace
francisco
has
already
kind
of
talked
about.
A
A
The
fact
that
you
can,
with
a
credit
card
or
not
because
free
trials
are
now
much
more
abundant
than
they
were
access,
almost
any
type
of
technology
that
you
want,
without
asking
permission
from
from
it
or
ops
or
whoever,
whoever
in
an
organization
used
to
be
that
kind
of
gatekeeper
who
got
to
use.
What
also
there
is
an
abundance
of
choice
in
frameworks
and
tooling
and
fati
showed
this
earlier.
A
So
perhaps
you
need
not
just
ci
and
cd
tooling,
but
a
whole
bunch
of
other
different
pieces
in
order
to
kind
of
build
and
test
and
deploy
software
right.
This
is
the
cncf
landscape,
and
if
you
look
at
this
and
don't
feel
somewhat
overwhelmed
by
the
the
amount
of
options
that
you
have
for
all
the
different
kind
of
components
and
pieces,
you
have
a
much
stronger
stomach
than
I
do.
A
What
we
are
seeing
is
that
when
developers
are
going
to
to
build
something,
they
not
only
have
to
navigate
this
over
abundance
of
choice,
but
then
have
to
figure
out
how
to
make
all
of
these
pieces
work
together
and
then
have
to
figure
out
how
to
maintain
all
of
those
pieces
working
together
in
an
industry
where
the
second
something
is
out
there.
The
clock
has
started
on
when
it
is
going
to
be
obsolete
or
outdated.
A
This
is
a
phenomena
that
again,
my
colleague,
steve,
has
kind
of
coined
as
the
developer
experience
gap.
So
the
time
that
developers,
who
probably
would
rather
just
be
writing
code,
have
to
take
away
from
that
in
order
to
maintain
the
the
often
onerous
chain
of
tooling
that
they
need
in
order
to
do
it
often
with
the
technical
equivalent
of
duct
tape
and
bailing
wire-
and
I
don't
know
about
you,
but
in
my
past
I
have
done
things
with
scripts
that
I
am
not
proud
of,
and
I
assume
that
it
caused
absolutely
no
technical
debt
whatsoever.
A
A
Open
standards
is
probably
you
know,
another
kind
of
movement
coming
from,
maybe
a
different
different
part
of
the
community.
The
idea
that,
if
we're
all
building
things
according
to
some
type
of
standard,
maybe
maybe
it
will
be
easier
to
figure
out
what
we're
working
with
interoperability,
which,
yes,
if
things
were
actually
designed
to
work
together,
it
would
be
great,
but
interoperability
often
feels
like
the
holy
grail
of
kind
of
like
software
tool
changes.
A
We
have
political
platforms,
we
have
other
types
of
physical
platforms
like
train
platforms
or
oil
platforms
and
then
there's
the
way
that
we
use
the
word
platform
in
tech
and
those
are
the
shoes
I
would
want
to
be
wearing
if
it
was
not
102
degrees.
By
the
way,
so
we've
heard
platforms
used
to
talk
about
what
in
the
past,
we
would
have
talked
about
as
products
right.
We
hear
about
data
platforms,
aiml
platforms,
observability
platforms,
devops
platforms
and
even
conference
platforms
like
the
one.
A
A
If
we
got
into
that,
but
while
we
don't
usually
use
the
word
has
anymore,
we
are
seeing
a
new
generation
of
app
development
platforms
out
there
that
are
prioritizing
like
developer
experience,
the
netlifes,
the
gatsbys,
the
versailles,
the
renders
and
then
also
we're,
seeing
the
rise
of
internal
development
platforms
that
are
built
in
order
to
help
optimize
the
developer.
Experience
for
developers
in
an
organization.
A
A
So
why
are
internal
platforms
increasingly
becoming
a
thing
in
some
ways?
Internal
platforms
allow
organizations
to
leverage
the
expertise
of
people
who
are
specifically
focusing
on
how
to
put
tools
together
how
to
create
something
to
build
on
instead
of
having
to
do
that
as
like
a
side
step
and
then
go
and
build
the
applications
themselves.
A
A
A
Now
this
is
her
diagram.
I'll
give
you
a
link
to
a
set
of
sides
that
she's
kind
of
made
public.
I
wish
there
was
a
recording
of
her
talk
that
there
isn't,
and
if
I,
if
I
were
to
kind
of
take
this
and
update
it,
which
I
I
did
not
do,
because
I
keep
thinking
about
the
different
ways
that
I
would
update
it
for,
like
a
more
general
use
case,
as
opposed
to
what
the
new
york
times
is
doing.
A
In
some
ways.
This
does
not
solve
that
for
the
people
who
have
to
build
the
platforms
right
that
we're
just
kind
of
like
throwing
down
or
really
pushing
the
developer
experience
gap
over
to
platform
engineers.
And
while
I'm
not
going
to
say
that
platform
engineering
experience
gap
is
a
term
that
we
need
to
have
it's
probably
something
that
exists.
A
Also,
the
idea
of
platform,
engineering
and
platform
kind
of
teams
as
being
the
creators
and
enablers
of
software
delivery.
I
think
we
need
to
start
thinking
about
it
that
way
and
finally,
platforms.
These
internal
platforms
very
much
need
to
be
seen
and
treated
as
products,
even
if
the
end
users
are
only
internal
because
one
of
the
ways
that
we
improve
the
developer
experience
and
you
may
only
ever
use
one
of
these
platforms
as
a
developer-
is
to
empower
platform
teams
and
platform
engineers.
A
Thank
you
very
much
for
your
time.
Today.
I
have
a
list
of
all
of
the
resources
that
I
have
used
and
hopefully
these
sites
will
be
published,
so
you
can
just
like
click
on
the
links
instead
of
having
to
type
out
all
of
the
different
urls,
and
I
will
be
here
until
thursday,
I
would
love
to
hear
what
you
are
using
to
build
your
software.