►
From YouTube: InFocus Keynote
Description
Join us for our first InFocus event: A special live keynote featuring our CEO, Thomas Domke, where he’ll share an inside look into the future of GitHub. Next, you’ll hear from our SVP of Product, Matthew McCullough, and Principal Solutions Engineer, Kevin Alwell, on the latest from our product organization, and Eirini Kalliamvakou, Staff Researcher at GitHub shares how the SPACE framework can help your organization.
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
Hello,
everyone
thank
you
for
joining
us.
The
world
depends
on
software.
We
can
no
longer
live
without
software.
Everything
we
do
at
work
in
our
lives
is
powered
by
thousands
of
lines
of
code.
When
I
wake
up
in
the
morning
my
alarm,
working
on
a
smartphone
and
my
watch
will
tell
me
how
I
slept.
I
read
the
news
on
my
phone.
I
check
my
email
I
catch
up
with
family
and
team
members.
I
might
take
a
photo
of
my
latte
in
a
fancy
coffee
shop.
A
I
track
my
runs
and,
of
course
I
can
schedule
a
doctor's
appointment
and
that's
only
a
subset
of
one
day
in
our
lives.
Millions
of
developers
build
and
maintain
the
software
that
runs
our
world
and
open
source
plays
a
big
role
in
this.
In
fact,
over
90
percent
of
software
has
some
dependency
on
open
source.
It
has
a
dependency
on
developers
and
maintainers
from
around
the
world,
innovating
together
and
contributing
code.
There
is
no
single
company
that
can
out
compete
open
source
for
collaboration.
A
So
as
a
software
company,
how
do
you
keep
innovating?
How
do
you
empower
your
developers
to
deliver
for
business
and
work
alongside
the
open
source
community?
Well,
for
starters,
you
can
have
your
developers
collaborate
with
each
other
in
the
same
way
that
open
source
projects,
collaborate
across
boundaries
across
silos
and
across
country
borders.
A
That's
the
power
of
the
interconnected
community
and
at
github
we're
on
a
mission
to
accelerate
human
progress
through
developer
collaboration,
and
that
starts
by
thinking
developers.
First,
with
every
decision
we
make
every
product
we
design
with
every
process
we
implement.
We
want
to
empower
developers
to
their
best
work
on
github
and
we
have
seen
customers
joining
us
on
this
journey
by
empowering
their
own
developers
to
help
build
the
future
of
software
alongside
the
open
source
community.
A
Several
years
ago,
we
started
working
with
a
team
at
3m
and
you
might
know
them
from
the
post-it
notes,
but
they
have
created
over
60
000
products
from
across
the
world.
They
were
struggling
with
how
to
share
knowledge,
how
to
break
through
silos
that
left
their
code
scattered
in
a
ton
of
places.
They
wanted
to
innovate
like
the
open
source
community
and
work
together
globally,
so
they
decided
to
choose
github
to
help
power.
A
The
next
stage
of
innovation
and
what
started
with
a
few
developers
sharing
ai
models
grew
into
over
1600
developers,
using
github
to
optimize
their
development
processes
and
speed
up
their
time
to
market
the
team
at
3m
never
mandated
github.
Their
developers
chose
to
move
their
software
collaboration
to
github
in
the
cloud
and
are
quickly
modernizing
their
entire
tool
chain.
A
They
started
using
github
actions,
which
is
our
ci
cd
platform
to
power
deployments
to
their
multi-cloud
infrastructure
and
they're,
also
adopting
other
github
features
like
the
pandabot
and
they're,
using
our
security
pipeline
to
help
secure
the
end-to-end
software
supply
chain.
This
is
the
true
power
of
thinking
developer,
first
by
empowering
developers
to
their
best
work
on
github.
We
enable
companies
like
3m
or
your
company,
to
harness
the
power
of
github
alongside
the
open
source
community
and
we're
just
getting
started,
whether
your
startup
building
your
first
big
app
or
a
multinational
corporation
spending
the
globe.
A
We
want
to
help
you
build
the
world's
best
software
today
and
in
the
future.
Speaking
of
the
future,
when
we
look
ahead,
we
see
that
the
future
of
software
development
has
four
major
trends,
and
the
first
is
that
software
development
is
moving
to
the
cloud
developers
have
spent
the
last
10
years
or
so
on.
Moving
other
professionals
to
the
cloud
sales,
people
with
salesforce
designers,
with
figma
accountants
with
netsuite,
and
yet
software
development
is
still
mostly
local.
Last
year
we
launched
a
new
product
called
codespaces
which
moves
the
whole
software
environment
to
a
virtual
machine.
A
A
software
developer
still
uses
a
laptop,
of
course
to
connect
to
that
cloud,
but
the
whole
environment,
all
the
dependencies
everything
needed
to
edit
and
run
your
project
is
now
hosted
in
the
cloud
at
github
we
have
moved
over
800
developers
to
codespaces
and
reduced
the
onboarding
time
from
45
minutes
to
less
than
a
single
minute.
Our
developers,
our
team
members,
even
is
ceo,
can
now
easily
set
up
an
environment
and
get
started
on
a
project.
The
second
area
is
to
empower
developers
with
artificial
intelligence.
A
Ai
enables
developers
to
have
an
assistant
on
their
site
and
the
first
such
product
is
github
co-pilot
with
copilot
developers
can
stay
in
their
editor.
Copilot
understands
the
context
of
what
the
developer
is,
writing
and
proposes
what
you
may
type
next
from
multi-line
code
blocks
to
whole
methods.
A
Co-Pilot
actually
makes
developers
more
productive
by
keeping
them
in
their
editor
in
their
flow
of
productivity
and
generating
value
for
their
company's
customers.
Co-Pilot
would
not
exist
without
the
open
source
it
was
trained
on.
So
my
third
focus
area
is
open
source.
Almost
all
software
today
depends
on
open
source.
We
believe
open
source
has
one
not
only
as
a
philosophy
of
publishing
source
code,
but
more
so
as
a
way
for
many
developers
to
collaborate
with
each
other
open
source
contributions,
make
technology
better
for
everyone,
and
it
has
become
synonymous
with
enterprise
software.
A
The
unaffiliated
nature
of
open
source
means
that
the
community
that
maintains
it
plays
a
whole
advancing
overall
innovation
for
all
of
us.
These
developers
are
part
of
our
teams
and
it
is
our
responsibility
to
support
sustainable,
open
source
and
open
source
impacts.
Your
security
posture,
you
might
have
hundreds
of
projects
in
your
own
company,
but
you're
likely
using
thousands
of
open
source
components.
A
Every
single
project,
internal
or
external
needs
to
be
constantly
scanned
for
code
and
runtime
vulnerabilities,
scan
for
secrets
and
code
and
scan
for
injected
malware
at
github.
We
are
on
a
mission
to
help
customers
secure
their
code
with
tools
like
code,
curl
and
dependerbot,
but
we're
also
helping
open
source
maintainers
to
secure
their
projects.
A
No
single
company
can
secure
their
software
supply
chain
on
their
own.
We
all
need
to
work
together
on
this.
Thank
you
so
much
for
joining
us
at
infocus.
We're
excited
to
partner
with
you
to
accelerate
your
software
delivery,
optimize
your
efficiency
and
secure
your
software,
as
well
as
your
software
supply
chain.
B
Thanks
thomas
hi,
I'm
matthew
the
svp
of
product
at
github,
and
I'm
here
with
you
today
to
chat
about
how
you
can
build
amazing
software
experiences
with
github.
You
may
have
heard
this
years
ago,
but
it
remains
true
even
today,
regardless
of
our
industries,
we're
in
the
midst
of
transforming
all
businesses
to
software
businesses
and
as
a
software
business,
we
find
that
very
relatable
when
you
consider
the
complexity
of
the
tool
stack,
the
talent
shortage
and
the
speed
at
which
we
have
to
operate
reaching
our
goals
feels
challenging
at
times.
C
Hello
and
welcome
my
name
is
kevin
alwell,
I'm
a
principal
enterprise
solutions
engineer
at
github.
Today,
I'm
going
to
be
walking
you
through
how
all
these
features
and
how
this
strategy
manifests
in
terms
of
enterprise
capabilities
across
the
platform.
So
for
what
that
means
for
us
is
we're
going
to
migrate
an
application
from
a
third
party
scm
tool
into
github
we're
going
to
translate
a
pipeline
into
an
actions.
C
Workflow
use
some
of
the
latest
and
greatest
capabilities
across
the
platform
and
then
ultimately
deploy
it
out
into
azure,
so
buckle
up,
it'll
be
an
action-packed
10
minutes.
It's
a
privilege
to
be
here,
walking
you
through
this,
and
so
I
appreciate
your
time
and
obviously
your
attention,
and
so
one
thing
that
I
abstracted
here
from
the
demo
was
I
used
to
github
enterprise
importer
to
to
actually
create
a
migration
script
and
so
that
migration
script
will
be
applied
to
all
the
repos.
C
My
organization
in
this
case
get
a
better
price
server
into
my
github
enterprise
cloud,
org.
Okay,
so
my
repo
is
already
there.
I
also
automatically
translated
using
valet
my
jenkins
pipeline
into
a
github
actions.
Workflow.
You
can
see
that
this
pull
request
was
dynamically
created
for
me
that
I'll
reference
in
a
in
a
little
while
the
last
thing
I'll
call
out
is
valet,
does
translation
from
jenkins
and
circle
ci.
C
This
supports
many
third-party
ci
providers
and
it
also
can
audit
your
existing
pipelines
to
understand
you
know
your
footprint
and
how
that
would
translate
into
actions.
Workflows
super
useful,
okay,
now
that
we're
here,
maybe
some
of
the
first
things
I'll
show
you
is-
is
actually
code
spaces.
Your
cloud
hosted
ide.
So
if
you
want
to
accelerate
the
time
to
productivity
for
your
developers,
a
cloud
hosted
id
is,
is
often
a
good
option
to
do
that.
That's
what
we've
done
at
github
is
actually
adopted.
C
It
stands
up
a
container
image
and
then,
when
you
actually
go
to
launch
your
code
space,
it
pulls
it
off
the
rack
and
makes
it
available
to
your
devs,
and
so
you
can
see
that's
actually.
What
I
have
here
is
this
pre-built
code
space
environment
stood
up
and
accessible
through
my
browser,
so
if
it
is
something
like
npm
start,
I
should
see
my
application
running
on
port
3000
highly
sophisticated
application
there.
It
is
as
a
as
a
calculator
okay.
C
What
I
did
want
to
call
out
here
is
actually
how
we
standardize
this
cloud
id
environment
in
your
pre-built
environment,
what
it
actually
interprets
for
building
that
image-
and
this
is
this
dev
container
file
you
can
see
in
this
case
I've
included
copilot.
That's
what
we'll
be
testing
together,
and
this
is
how
I
actually
pre-installed
my
dependencies
was
to
run
this
post
create
command
okay,
so
maybe
the
first
thing
we'll
do
is
validate
the
copilots.
Here
again,
if
you
haven't
heard
of
copilot,
it's
your
pair
ai
programmer,
so
I
I
basically
described
a
copilot.
C
Array,
we
might
get
a
function
suggested
here
that
adds
all
numbers
in
an
array.
Similarly,
I
might
be
able
to
call
a
third-party
api
and
it
would
understand
those
endpoints,
so
I
don't
have
to
go
to
stack
overflow.
I
don't
have
to
go
to
those
doc
that
documentation,
I
might
say,
get
all
members
of
my
github
organized
organization.
C
Okay,
and
so
then
I
might
get
you
can
see
here,
this
is
actually
supposed
to
be
your
org
id.
It's
aware
of
this
members,
co-pilot's
awareness
member's
endpoint.
All
I
have
to
do
is
kind
of
massage
it
a
little
bit
as
a
developer.
Otherwise
I
can
use
this
code
in
order
to
get
all
the
members
of
my
github
organization.
There's
a
stat
that
says
35
of
the
code
that's
committed
where
a
developer
has
copilot
enabled
is
actually
generated
by
copilot.
So
it's
a
third
increase
in
productivity,
which
is
massive.
That's
why
I
love
it.
C
Okay,
now,
let's
dive
in
here
into
the
new
projects,
v2,
I
want
to
showcase
some
of
the
progress
we're
making
in
planning
and
tracking
and
again,
I
know
we're
moving
fast
here
this
just
giving
you
a
taste
of
some
of
the
latest
capabilities.
One
of
the
first
things
you'll
notice
here
is
that
this
is
actually
a
project
that
spans
multiple
repositories.
All
my
work
items
are
tracked
in
a
very
familiar
way
kind
of
like
an
excel
spreadsheet.
C
Okay,
I
can
also
view
those
work
items
in
a
typical
kanban
board
style,
a
track
or
delivery
toward
an
alpha.
I
might
also
look
for
something
like,
for
example,
you
know
this
kind
of
parent-child
relationship
as
I'm
tracking
progress
towards
some
greater
deliverable
right,
some
epic,
as
those
work
items
get
delivered
and
that's
what
you'll
notice
here.
C
The
last
thing
that
I'll
show
you
maybe
second
to
last
thing
is
how
you
can
actually
group
your
tasks
by
the
label,
so
you
can
actually
group
your
task
by,
for
example,
the
urgency
or
the
priority
of
these
features,
and
so
to
do
that,
I
might
press
command
k
on
my
project
board.
I
might
say
something
like
group
by
and
in
this
case
my
group
by
my
iteration
and
I
as
a
pm
as
a
product
owner.
I
can
actually
come
in
and
see
hey.
C
Here's
what's
in
progress
today
for
this
current
sprint
cycle,
okay,
and
so,
let's,
together,
take
off
just
work
on
them,
consume
reusable
deployment
workflow
to
azure,
and
so
it's
the
work
item
is
exactly
that
and
what
I'll
do
is
actually
see.
Has
anyone
else
in
my
org
already
implemented
this
reusable
workflow,
or
does
it
exist
in
the
org?
And
so
to
do
that
I
do
use
our
new
code
search
functionality.
That's
actually
stack
ranks
your
results
based
on
the
relevance
to
you
today.
C
That's
actually
not
done
in
the
regular
search,
it's
all
random,
so
you'll,
you
know.
I
think
this
experience
is
nicely
curated.
Now.
The
experience
here
is
is
pretty
cool.
I
can
see
basically
at
the
top
level
any
reference
to
deploy
node.
I
can
also
there's
this
consumer
workflow.
Here
is
the
parent,
though
this
reusable
workflow,
that
I
want
to
consume
it's
an
org
workflow
that
deploys
a
node
app
into
azure,
and
so
maybe
it
says
to
consume.
I
want
to
capture
that.
C
Maybe
one
thing
I'll
mention
to
you
about
this:
reusable
workflow
is
it's
actually
running
on
a
custom,
hosted
runner
that
has
enhanced
compute
storage
and
also
a
reduced
range
of
ip
addresses,
which
is
awesome
from
an
infosec
perspective.
Okay,
so
I've
already
captured
what
this
workflow
does.
So
I
go
back
to
my
code
space.
Maybe
I
go
to
my
centralized,
deploy,
I
go
add,
deploy
here
so
into
my
own
pipeline,
my
own
deployment
pipeline.
I
capture
this
reusable
workflow.
C
C
C
I
know
it's
already
been
action-packed,
everything's
come
and
gone,
and
the
flash
is
this
new
push
protection
feature
we've
shipped
for
advanced
security
customers,
and
so
this
is
a
github
token
that
I'm
adding
to
this
reusable
workflow
and
what
I
want
to
do
is
actually
proactively
block
this
credential
from
making
its
way
back
into
my
source
code.
Today
we
already
have
a
detection
for
kind
of
reactive
controls.
Have
I
already
pushed
a
credential
in
my
source
code,
and
this
will
prevent
that
from
happening
in
the
first
place?
C
Let's
get
push,
what
we'll
notice
is
that
this
has
actually
been
blocked,
so
the
push
protection
the
secret
detected.
This
push
has
failed.
Here's
the
reference
for
the
commit,
the
file,
the
line,
and
I
can
actually
go
and
circumvent
that
as
a
developer.
If,
for
some
reason
I
know
that
this
is
used
in
tests,
it's
a
false,
positive
or
I'll
fix
it
later,
and
then
I
have
temporary
the
temporary
ability
to
push
that
credential
back
to
the
repo,
so
now
we're
kind
of
just
adding
these
guardrails
without
being
too
invasive
to
the
developer
experience.
C
C
C
So
again,
let's
talk
about
what
we've
already
seen
in
the
git
of
enterprise
importer
to
move
your
source
code
from
third
party
sem
into
github,
we've
seen
translation
for
your
pipelines
from
azure
devops
into
git
of
actions
workflows.
We
use
a
code
space
with
a
pre-build
which
accelerates
our
dev
developers,
ability
again
to
get
up
and
running
on
a
new
project.
We've
seen
projects
v2
our
new
planning
and
tracking
tools.
C
Some
of
the
cool
capabilities
under
the
hood
there
for
our
power
users,
reusable
workflows,
searchability
custom,
hosted
runners
and
advanced
security,
push
protection,
so
there's
so
much
out
there
for
you
to
get
your
hands
on.
I
encourage
you
to
do
that.
Ask
us
questions
and
we'd
love
to
work
with
you.
So
thank
you
so
much
and
let's
get
back
to
the
program.
B
Thanks
kevin
as
a
software
developer
myself,
when
I
see
an
end-to-end
demo
like
that,
I
get
so
excited
and
that
excitement
comes
from
a
grounded.
Why
each
of
the
technology
showcased
has
tremendous
potential
to
enhance
developer
productivity
and
accelerate
your
business
if
you're,
not
using
github
enterprise,
yet
check
out
our
free
trial
and,
if
you're,
already
a
get
of
enterprise
customer.
Thank
you
we'd
love
to
chat
about
how
we
can
help
you
get
the
most
value
from
our
platform
and
use
the
whole
suite
of
features
that
kevin
just
showed
us
using
github's.
D
Hello,
everyone
welcome
to
in
focus
and
thank
you
for
joining
me.
We're
going
to
talk
about
productivity
today,
a
keyword
that
we
hear
everywhere
and
I'm
going
to
walk
you
through.
What
research
shows
can
help
you
and
your
team
and
your
organization
not
only
become
more
productive
but
continue
to
be
productive,
long
term
in
a
healthy
way,
I'm
irinica
lemvakum.
I
am
a
researcher
here
at
github.
I
work
out
of
github
next,
where
we
innovate
and
we
create
what
is
going
to
be
the
future
of
software
development.
D
I'm
also
a
member
of
the
developer
velocity
lab,
and
this
is
a
research
initiative
between
github
and
microsoft,
where
we
are
focusing
on.
How
can
we
improve
the
now
for
software
development?
We
are
a
team
of
researchers
and
data
scientists.
We
discover
tools
and
processes
through
research
that
really
work
for
developers
and
help
them
be
more
productive,
more
efficient,
healthier
and
happier.
D
Why
do
we
talk
about
and
think
about
developer
productivity?
So
much?
There
are
a
couple
of
reasons.
The
first
one
is
that
developer
productivity
is
really
really
important
to
get
right.
It
underlines
the
success
of
any
organization,
and
it
does
it
in
a
number
of
different
ways.
So
perhaps
you're
recognizing
yourself
here,
maybe
you're
thinking
about
how
to
accelerate
your
software
development.
How
can
you
be
going
to
market
faster?
How
can
you
be
building
software
in
tighter
cycles?
D
Maybe
you're
thinking
about
how
you
can
be
building
software,
that
is
more
secure
or
more
reliable,
maybe
you're
thinking
about
improving
your
own
organizational
efficiency?
How
can
you,
for
example,
be
making
better
planning
decisions
faster
or
maybe
you're
thinking
about
improving
your
developers,
well-being
and
their
retention
down
the
line?
D
All
of
these
things
are
things
that
are
directly
influenced
by
developer
productivity,
and
we
find
case
study
after
case
study
after
case
study
that
those
organizations
that
pay
attention
to
developer
productivity
and
support
it.
Well,
they
end
up
performing
better
too,
unfortunately
important
as
it
is
to
get
developer
productivity
right.
We
do
often
get
it
wrong
and
that's
only
because
productivity
is
complicated
and
the
concept
has
been
around
for
a
long
time,
so
it
has
accumulated
some
myths
and
misconceptions
that
sometimes
can
just
throw
off
our
thinking.
D
For
example,
we
hear
from
a
lot
of
teams
and
organizations
who
care
about
developer
productivity,
but
they
only
ever
measure
developer
activity.
They
track
activity
over
time.
They
look
at
dashboards
of
lines
of
code
numbers
of
commits
numbers
of
pull
requests,
but
what
we
find
is
that
those
activity
counts
alone
are
not
enough
to
predict
successful
outcomes.
We
could
be
looking
at
dashboards
all
day
long
and
whether
our
numbers
of
commits
are
going
up
or
down.
D
Other
times
we
hear
that
productivity
measures
are
only
ever
relevant
to
you
if
you're,
a
manager
and
again
we
find
in
the
research
and
I'm
going
to
share
some
of
that
later.
The
productivity
measures
are
incredibly
beneficial
for
individual
developers
and
their
personal
productivity
too.
They
can
show
them
how
to
improve
and
when
to
improve
and
what,
if
we
do
it
right
and
they
can
increase
their
satisfaction,
they
can
improve
their
well-being
and
they
can
increase
their
confidence
too.
D
When
something
is
really
important
to
get
right,
we
don't
want
to
be
getting
it
wrong.
So
here
is
one
thing
that
I
would
like
you
to
be
thinking
about.
As
I
talk
through
the
research
and
the
insights
today,
and
that
is
that
when
we
say
we
want
improved
productivity,
nobody
wants
that
improvement
to
only
last
a
week
or
a
sprint
or
a
quarter.
What
we
really
want
is
productivity
improvements
that
we
can
sustain
over
time
and
if
we
only
ever
look
at
activity,
that's
not
enough
to
get
us
there.
Think
about
this.
D
Maybe
you've
seen
this
in
your
organization
too.
Sometimes
teams
push
themselves
hard
towards
a
ship
deadline
and
they
get
us
activity.
Spikes.
They
do
manage
to
get
a
lot
more
done
than
usual
in
that
time
frame,
but
is
that
sustainable?
Is
that
their
new
rhythm
of
work
that
they
can
maintain
past
the
deadline?
Probably
not
when
teams
operate
that
way,
they
conquer,
quick
productivity,
wins
and
those
can
feel
great,
sometimes
they're
essential,
but
they
can
also
backfire.
D
So
the
smart
use
of
resources
and
the
smart
investment
is
to
think
past
only
the
next
quarter
and
how
to
set
yourself
up
to
have
productivity
improvements
and
benefits
that
are
going
to
see
you
through
the
next
three
to
five
years,
and
you
don't
have
to
do
it
in
the
dark.
You
don't
have
to
do
it
alone.
I
can
guide
you
through
it
with
the
latest
research.
So
today
I'm
going
to
talk
to
you
about
three
things:
one
we're
going
to
talk
about
a
new
productivity
framework,
a
way
to
measure
productivity
called
space.
D
Two,
I'm
going
to
talk
to
you
about
how
we
use
space
here
at
github
to
help
developers
improve
their
own
personal
productivity
in
the
good
day
project
and,
finally,
we're
going
to
look
at
three
trends
from
the
2021
state
of
the
octopus
report.
That
can
show
you
how
you
can
help
your
organization
become
more
productive
and
sustain
the
productivity
improvements
over
time.
D
D
What's
special
about
space
is
that
it
is
holistic
and
it
takes
out
into
consideration
a
lot
more
dimensions
and
a
lot
more
metrics
around
productivity
and
the
trade-offs
between
them,
and
in
that
sense
it
can
bypass
all
of
the
productivity
myths
and
misconceptions
I
mentioned
earlier.
Space
is
also
very
intentional
about
incorporating
well-being
aspects.
D
We
want
to
make
sure
that
any
productivity
measures
and
metrics
we're
putting
in
place
work
for
the
developers
themselves
too,
and
it's
that
combination
of
perspectives
being
holistic
and
incorporating
well-being
aspects
that
really
makes
productivity
sustainable
space
is
an
acronym
s
is
for
satisfaction
and
well-being.
P
is
for
performance,
a
is
for
activity,
c
is
for
communication,
and
collaboration
and
e
is
for
efficiency
and
flow,
and
already
you
can
see
that
there's
a
lot
more
going
on
here
than
just
activity.
D
The
first
one
looks
at
satisfaction
and
well-being.
Both
of
those
are
critical
parts.
They
directly
influence
developer
productivity,
so
we
make
we
want
to
make
sure
that
we
are
tracking
both
of
those,
and
here
you
could
be
thinking
about
metrics,
like
employee
satisfaction,
level
of
engagement
level
of
burnout.
D
We
find
more
and
more
that
companies
track
these
indicators
over
time
and
they
usually
do
it
through
surveys,
which
is
a
great
practice,
because
information
about
satisfaction
and
well-being
doesn't
really
live
in
any
telemetry.
So
this
is
really
a
dimension
that
looks
at
how
happy
and
fulfilled
developers
are
with
the
type
of
work
that
they
do.
The
work,
the
tools
that
they
use
and
the
culture
and
environment
that
they're
in
the
next
dimension
performance
is
about
outcomes.
D
How
well
did
we
do,
and
here
we
want
to
be
thinking
about
way
more
than
just
how
much
we
did
the
impact
of
our
code,
the
quality
of
our
code,
the
level
of
customer
satisfaction
that
we
generate.
These
are
all
things
that
are
important
for
performance
performance
is
also
not
a
binary.
It's
not
did
we
do
well
or
not,
and
the
reason
is
that
some
of
these
aspects
and
these
metrics
of
performance
have
trade
us
between
them.
D
So
maybe
we
write
a
lot
of
code,
but
it's
not
good
quality
or
maybe
we
are
shipping
features
on
time,
but
they
don't
really
get
adopted
or
maybe
sometimes
a
lot
of
different
metrics
seem
to
be
moving
in
the
right
direction.
We
write
a
lot
of
code
it
ships
on
time.
It
is
high
quality
features,
get
adopted,
they
generate
revenue,
but
our
developers
are
burnt
out,
so
how
good
our
performance
is
is
always
relevant
to
how
what
our
goals
are.
What
is
it
that
is
important
to
you
and
that's
how
we
pick
metrics
as
well.
D
We
have
way
more
metrics
than
we'll
ever
be
able
to
use.
The
key
aspect
is
to
pick
the
relevant
ones.
Goals
come
first,
metrics
come
next,
and
the
metrics
that
you
use
in
your
organization
when
it
comes
to
performance
may
be
very
different
from
another
organization.
Just
because
you
have
different
goals.
D
One
of
my
personal
favorites
to
highlight
is
mentorship,
which
kind
of
happens
out
of
sight
mentorship.
You
will
hear
later
from
the
2021
state
of
the
octopus
report,
it's
incredibly
beneficial
for
teams
and
organizations,
and
it's
also
an
activity
that
developers
do
more
and
more
of
as
they
go
through
their
careers
and
they
become
more
senior,
and
yet
it
happens
pretty
much
invisibly.
It's
not
tracked
anywhere,
and
it
doesn't
happen
within
any
engineering
system
that
we
track
off.
D
So
when
we
think
about
activity,
we
want
to
be
thinking
broadly
to
make
sure
we're
capturing
all
the
different
things
that
developers
do.
Communication
and
collaboration
focuses
on
teams.
What
is
it
that
teams
need
to
get
their
work
done
and
that
might
include
things
that
we
don't
typically
think
about.
So,
for
example,
how
long
does
it
take
to
find
a
colleague
that
has
expertise
that
can
help
you
solve
a
problem
you're
stuck
on
or
how
easy
is
it
to
find
the
right
information,
the
right
documentation
about
an
area
of
the
code
base?
D
You're
working
on
these
are
tricky
aspects
to
quantify.
So
again
we
want
to
make
sure
that
we're
going
back
to
developers
as
the
source
of
truth,
usually
with
something
like
a
survey
and
finally,
efficiency
and
flow.
This
one
is
becoming
more
and
more
critical
to
developer
productivity
and,
in
fact,
if
you
hear
developers
say
that
they've
had
a
particularly
productive
day
or
productive
week.
This
is
what
they're
talking
about
you
may
have
heard
of
the
concept
of
flow.
D
I'm
oversimplifying,
but
flow
is
a
state
that
when
we
enter
it
and
stay
in
it
long
enough,
it's
a
state
of
intense
concentration
and
it
makes
us
more
efficient.
Now,
unfortunately,
it's
also
a
fragile
state.
It's
hard
to
get
into
it's
easy
to
get
out
of,
especially
if
we
experience
a
lot
of
fragmentation
in
our
days,
so
we
could
be
looking
at
efficiency
and
flow
from
the
individual
perspective.
What's
the
level
of
interruption
that
somebody
is
experiencing
throughout
their
day?
D
D
That
was
an
overview
of
what
goes
into
the
space
framework
and
when
we
say
that
it
is
holistic.
What
is
it
that
we
mean?
There's
a
lot
more
to
dig
into
definitely
check
out
the
developer
velocity
lab
website,
because
there's
a
longer
recorded
talk
there.
That
goes
more
into
the
specifics
and,
of
course,
the
paper.
If
you
want
to
get
all
the
information,
but
for
the
practical
application
in
your
organization,
here's
the
pro
tip.
D
We
recommend
that
you
pick
three
out
of
the
five
dimensions
of
the
space
framework
and
for
each
one
of
those
three
dimensions.
You
pick
a
couple
of
metrics
to
cover
each
one
that
should
give
you
enough
to
get
you
out
of
the
habit
of
only
tracking
activity
over
time
and
to
give
you
a
baseline
of
being
holistic
and
then
over
time
you
can
gradually
progress
to
a
state
where
you
are
covering
all
of
the
five
dimensions,
with
multiple
metrics
for
each
one.
D
Now
that
was
a
little
bit
about
how
you
can
use
space
to
benefit
your
organization,
how
you
can
change
your
thinking
and
you
can
start
picking
metrics
that
work
for
you.
Can
you
also
use
it
to
improve
your
own
personal
productivity,
though
spoiler
you?
Can
we
tested
that
here
at
github
through
the
good
day
project?
And
you
may
have
heard
or
read
something
about
the
good
day
project
we
published
it
last
year
in
the
github
blog.
D
What
we
were
trying
to
do
with
a
good
day
project
was
to
empower
developers,
give
developers
the
means
to
improve
their
own
days
and
improve
their
own
productivity
in
a
way
that
fits
them
because
believe
it
or
not
developers
most
of
the
time
are
not
getting
what
they
need
out
of
productivity
tools
and
productivity
trackers,
and
you
may
have
seen
this
for
yourself.
Productivity,
trackers,
typically
get.
D
D
They
find
that
it
doesn't
really
do
justice
to
how
multi-faceted
their
work
is,
because
it
keeps
being
reduced
to
only
a
couple
of
things.
They
have
seen,
unfortunately,
in
the
past,
these
very
activity,
oriented
approaches,
be
used
against
them
and
to
them.
The
whole
thing
feels
like
spying,
so
over
time,
developers
have
become
suspicious
when
it
comes
to
productivity
tools
and
productivity,
trackers
and
even
the
word
productivity
itself,
so
we
were
thinking
putting
developers
first.
D
D
We
had
an
approach
we
wanted
to
test
it,
here's
what
we
did
for
two
weeks.
Every
day
we
sent
engineers
at
github
a
two-minute
survey
to
fill
out.
All
of
the
questions
that
were
included
in
that
survey
came
from
the
space
framework,
that's
how
we
used
it
and
there
we
asked
them
how
much
they
worked
with
others.
That
day,
how
much
they
helped
others,
how
many
breaks
they
took,
how
many
meetings
they
had?
What
was
their
sentiment
for
the
day?
D
All
of
these
things
are
critical
parts
of
the
daily
lives
of
developers,
and
yet
we
never
track
them
and
monitor
them
anywhere
and
after
two
weeks
of
these
daily
surveys,
we
sent
each
person
who
participated
their
own
personalized
report.
This
was
something
that
was
specific
to
them.
It
only
had
their
data
on
it,
nobody
else's
and
they
were
the
only
ones
who
had
access
to
it.
D
D
D
It
turns
out
the
daily
act
of
self-reflection
had
a
benefit
in
itself,
so,
above
and
beyond
anything
else,
we
gave
developers
those
two
minutes
at
the
end
of
the
day
to
reflect
with
a
couple
of
questions
or
a
handful
of
questions.
Rather
help
developers
be
more
intentional
about
how
they
spent
their
time
and
more
mindful
during
their
day,
and
it
also
gave
them
a
very
clear
end
point
to
their
day,
which,
as
the
boundaries
between
work
and
life,
have
blurred
quite
a
bit,
it
has
become
harder
and
harder
for
people
to
do.
D
We
also
looked
across
everyone's
data
because
we
wanted
to
see
if
there
are
any
patterns
that
are
showing
up
and
sure
enough.
We
saw
exactly
how
critical
the
efficiency
and
flow
dimension
of
the
space
framework
really
is
because
with
minimal
to
no
interruptions,
developers
have
an
excellent
chance
of
having
a
good
day.
D
The
two
minute,
a
day
reflection
was
a
benefit
that
was
mentioned
by
every
single
person.
So
if
there's
one
thing
to
take
away,
it's
that
and
that's
great
news,
because
anyone
can
get
started
with
this
at
any
given
point
today,
if
you
want
to
after
this
presentation,
if
you
want
to
you,
can
use
the
questions
from
the
good
day
survey.
We
have
shared
those
on
the
github
blog
and
you
can
take
two
minutes
at
the
end
of
the
day
to
answer
them
and
reflect
to
start
seeing
the
improvements
for
yourself.
D
D
Let's
look
at
three
trends
from
the
2021
state
of
the
octoverse
report
and
these
trends
represent
areas
for
long-term
investment
and
opportunity
in
your
organization
and
your
community
if
you're
working
with
one
and
they're
coming
from
a
pretty
detailed
and
thorough
investigation
of
an
unprecedented
scale
for
the
2021
state
of
the
octopus
report,
which
has
been
our
largest
one.
Yet
we
analyzed
data
from
over
3.5
million
repositories
and
responses
from
over
40
000
developers
to
a
very
detailed
and
lengthy
survey.
D
I
think
we
can
all
observe
that
the
workplace
is
shifting.
It
certainly
has
shifted
the
last
year
that
came
through
very
clearly
in
the
survey
developers
from
all
over
the
world
expressed
the
expectation
to
be
working
differently.
Moving
forward.
We
had
46
percent
of
the
participants
who
worked
in
companies
and
who
were
previously
co-located
now
expecting
to
work
in
a
fully
remote
or
hybrid
environment,
and
we
don't
know
how
much
of
this
is
going
to
shift
back
or
maybe,
if
any
of
this
will,
because
some
things
we
don't
go
back
from.
D
But
what
this
highlights
is
the
need
for
rethinking.
Do
you
have
the
tools
and
the
processes
in
place
that
will
allow
you
the
flexibility
to
work
in
a
fully
remote
or
hybrid
environment
without
sacrificing
efficiency?
What
do
you
need
to
do
to
get
to
that
point?
How
can
you
make
work
sustainable
both
for
the
employer
and
the
employee
for
the
long
term
mentorship?
I
kind
of
hinted
at
this
earlier.
Mentorship
is
proving
to
be
an
all
around
assets
both
for
open
source
communities
and
for
companies.
D
It
has
significant
productivity
benefits.
We
saw
a
46
boost
in
open
source
teams
and
16
boost
in
teams
and
companies,
but
it's
also
a
multiplier
when
it
comes
to
creating
and
sustaining
and
strong
and
healthy
culture,
and
that
that
is
the
sort
of
benefit
that
has
very
long
lasting
effects,
maybe
you're
already
thinking
about
mentorship
in
your
organization,
which
is
great.
Maybe
you
have
onboarding
bodies
when
people
join,
maybe
you
have
office
hours.
D
Now
we
packed
a
lot
of
things
in
a
short
time.
So
here's
the
summary:
here's,
the
tldr
holistic
measures
are
your
friend
when
it
comes
to
productivity.
They
allow
us
to
take
a
step
back,
look
at
a
lot
more
dimensions,
a
lot
more
metrics
pick
the
right
ones
and
that's
what
makes
productivity
sustainable?