►
From YouTube: Opening Keynote - GitHub Universe 2015
Description
From high school robotics classes to NASA scientists, everyone is building software. In the opening keynote of GitHub Universe 2015, GitHub Co-founder and CEO Chris Wanstrath looks back at how GitHub grew into a community of more than 10 million developers and shares some of the most unexpected and inspiring things people are building today.
Chris also makes a few announcements, including the Integrations Directory (https://github.com/integrations) that catalogs the apps and services that integrate with GitHub, Git Large File Storage 1.0 (https://github.com/blog/2069-git-large-file-storage-v1-0), and a partnership with Yubico (https://github.com/blog/2071-github-supports-universal-2nd-factor-authentication)—a provider of FIDO U2F keys—to outfit your GitHub account with cutting-edge security.
About GitHub Universe:
Great software is more than code. GitHub Universe serves as a showcase for how people work together to solve the hard problems of developing software.
For more information on GitHub Universe, check the website:
http://githubuniverse.com
A
A
B
Hello,
everybody
welcome
to
github
universe.
This
is
absolutely
incredible.
We've
been
talking
about
doing
this
for
such
a
long
time.
It's
really
a
dream
come
true.
So
thank
you
for
joining
us
in
this
amazingly
weird
and
incredible
space
that
somehow
turned
into
a
great
conference
venue,
so
we're
here
to
talk
a
lot
about
github
today.
Welcome
to
our
first
developer
conference,
focus
on
octa
cats
and
getting
off
to
catch
together.
No,
not
really
I
mean
this
is
a
conference
with
github
in
the
name.
There's
octa
cats
everywhere,
but
really
this
is
about
you.
B
Github
is
all
about
developers.
It's
all
about
people,
it's
all
about
building
things
for
people
using
them
and
over
the
next
two
days,
we're
going
to
talk
a
lot
about
building,
collaborating
on
and
deploying
software.
What's
interesting
is
we've
been
doing
this
now
for
about
eight
years,
and
this
is
the
same
thing:
we've
been
talking
about
the
whole
time.
B
B
So
this
is
our.
This
is
not
our
logo
right
now.
Some
of
you
remember
this.
This
was
a
one
of
our
original
logos.
We
went
through
a
couple
different
variations.
Our
first
tagline
was
social,
get
posting,
which
is
like
absolutely
incredible
right.
Everyone
loved
that
really
rolls
off
the
tongue,
but
eventually
we
landed
on
this
idea
of
social
coding.
We
realized
hosting,
isn't
interesting
and
while
get
is
really
cool,
the
get
part
isn't
what
makes
get
up
special.
B
It's
really
about
people,
it's
for
my
people,
working
together
to
build
software,
and
if
any
of
you
have
ever
experienced
the
pain
of
trying
to
learn,
get
as
a
new
user.
You
know
a
lot
of
people
join
github
in
spite
of
get
right,
there's
something
about
working
with
other
people,
sharing
ideas,
that's
just
so
powerful
that
you'll
learn
any
tool
or
go
through
any
pain
to
get
there.
Luckily,
that's
maybe
more
true,
eight
years
ago
about
get
being
painful
than
it
is
today
and
we're
going
to
talk
about
that.
B
But
the
point
is:
we've
always
been
focused
on
people
working
together
to
build
software
on
the
developers
on
the
software
development
experience
and
that's
been
reflected
in
our
logos
in
our
mascot,
in
our
development
or
open
source
and
in
our
conference.
So
that's
what
we're
going
to
talk
a
lot
about
today.
B
So
originally,
this
is
our
timeline.
There's
only
three
things
that
happens,
but
this
is
our
timeline
of
roughly
the
history
of
github,
and
so
you
know
when
we
started
github,
like
I
said,
we
really
wanted
to
add
a
social
layer
on
top
of
version
control
on
top
of
collaboration.
We
didn't
use
those
words.
What
we
really
wanted
was
just
an
easier
way
to
share
code
and
get
things
done.
B
What
we
ended
up
with
was
this
amazing
social
coding
experience,
but
at
the
beginning
we
only
targeted
individuals,
so
the
original
github
had
no
concept
of
organizations
or
groups
or
companies.
It
really
was
a
social
network
in
the
sense
of
you
had
to
sign
up.
You
had
your
own
account.
You
shared
software
on
your
own
account.
That
was
what
we
envisioned.
B
We
envisioned
just
a
bunch
of
people
using
this
off
this
site
to
share
code
and
work
together,
but
when
you're
are
focused
on
users
on
customers
on
developers,
you
have
to
get
really
good
at
listening
and
you
don't
have
to
be
that
good
at
listening
to
hear
the
overwhelming
feedback
that
what
the
hell
are
you
doing.
I
need
to
use
this
for
my
company.
Please
don't
make
me
pass
around
my
bosses,
user
login,
that's
not
very
secure,
so
we
decided
that's
a
great
point.
B
We
want
people
to
pass
around
user
logins
to
share
their
code,
there's
probably
a
better
way
and
really
that
came
from
you
that
came
from
people
saying
we
really
like
this
github
thing.
We
at
first
thought
this
would
be
a
good
way
for
us
to
share
code,
snippets
and
little
projects,
but
it's
turning
into
a
great
way
to
work
together
with
teams
both
open-source
nonprofits
and
corporations.
B
So,
in
2010,
about
two
years
after
we
launched
github,
we
rolled
up
this
feature
called
organizations
which
let
groups
of
people
work
together
for
the
first
time
on
github
and
we've
been
improving
that
ever
since,
in
fact,
there's
been
a
dramatic
increase
in
improvements
to
organizations
recently
CC
yesterday,
we
brought
some
really
awesome
ways
to
work
better
together
with
teams
and
know
who's
in
your
organization
and
have
more
control
over
who's.
Seeing
what
but
we
launched
organizations-
and
we
were
like
okay,
y'all
y'all
are
happy
now
right
and
everyone's
like
now.
B
This
is
that's
not
what
we
asked
for
right.
This
is
not
what
I
need.
We
would
meet
people
at
conferences
that
worked
for
a
small
government
or
a
school
or
a
major
bank,
and
they
would
tell
us
I
love,
github,
I
love
using
pull
requests,
I,
love,
sharing,
open
source,
but
I'm
not
allowed
to
use
this
inside
my
company.
We
have
some
bureaucracy
or
I
work
for
the
government
or
I
work
for
something
doing
with
secure
sort
of
financial
software.
I
can't
put
my
code
in
the
cloud,
so
what
we
felt
was
well.
B
The
cloud
is
the
future,
but
github
is
right
now,
so
why
don't?
We
find
a
way
to
help
people
work
better
together
in
any
environment
they're
in,
and
this
really
comes
from
the
fact
that
github
was
born
out
of
open-source.
We
were
built
on
top
of
get
from
the
very
beginning.
We
worked
with
the
gate
community,
we
contribute
to
the
gate
community
and
an
amazing
thing
about
the
gate.
Community
is
how
diverse
it
is.
There
are
so
many
different
tools.
There
are
so
many
different
applications.
B
There
are
so
many
different
ways
to
use
git
interact
with
get,
and
that
meant
that
the
day
we
launched
github
there
were
a
million
different
tools
you
could
use,
so
that
was
sort
of
guiding
our
philosophy
of
well.
We
can
be
opinionated
and
say:
the
cloud
is
the
only
way
to
build
software,
but
we
realized
that
there
are
a
lot
of
different
ways
to
build
software
and
what
we
care
most
about
is
helping
you
get
your
job
done
and
I,
don't
know
how
to
fight
the
corporate
bureaucracy.
B
Yet
to
get
your
code
in
the
cloud
we're
working
on
that,
but
we
do
know
how
to
ship
a
piece
of
software
that
you
can
run
behind
your
firewall.
So
around
2012
we
released
get
of
enterprise
which
let
you
collaborate
behind
the
firewall
and
we've
been
working
really
hard
on
that
ever
since,
but
an
important
thing
about
github
is
we
come
from
this
ecosystem?
We
are
at
the
core
closed
source.
B
We
participate
in
tons
of
open
source
and
love
the
open
source
community
and
we
don't
think
it's
either
or
we
think
its
a
mix
of
both
and
that's
really
where
our
focus
is
going
into
the
future.
We've
been
talking
a
lot
about
enterprise
over
the
last
couple
years.
We're
going
to
continue
to
talk
a
lot
about
it,
we're
going
to
talk
a
lot
about
open
source
in
the
next
two
days
and
beyond,
but
it's
not
open
source
vs.,
Enterprise,
anymore
and
I.
Think
all
of
us
know
this
by
realizing
this.
B
It's
very
much
about
open
source
and
enterprise.
That's
the
world
that
we
grew
up
and
that's
the
world
that
we
came
from
and
that's
rapidly
becoming
the
world
that
everyone
is
living
in,
which
is
really
exciting
for
those
of
us
that
are
open
source
fans
that
have
worked
in
companies
and
benefited
tremendously
from
the
work
of
people
putting
stuff
out
there
for
free
and
built
huge
companies
on
it.
It's
really
really
amazing,
but
it's
not
because
of
us.
This
is
just
the
way
the
world
is
moving.
It's
not
open
versus
closed
its
open
and
closed.
B
B
A
little
bit
easier,
apparently
that's
caught
on,
and
it's
not
just
developers,
it's
not
just
people
in
San
Francisco
that
are
building
ruby
on
rails
apps,
which
is
the
community
I
came
from
it's
kids
teachers
scientists,
it's
government's
now
of
all
things,
governments
are
being
very
progressive
in
terms
of
technology
sres
at
Google,
DevOps
people,
author's
writing
books.
The
word
developer
is
changing
right.
Some
will
say
that
there
are
20
million
developers
in
the
world
there's
no
way.
Half
of
them
have
get
of
accounts
right.
B
There's
just
there's
no
way
that
we
are
over
half
of
the
development
community.
I.
Just
don't
believe
that
I
think
there
are
way
way
more
than
20
million
developers
out
there
and
that's
because
we
can't
define
the
word
developer
the
way
we
defined
it
10
years
ago
or
15
years
ago,
yeah
there
are
maybe
20
million
people
that
are
1999
style
programming
engineers
employed
at
companies
sure
but
developers.
Journalists
at
are
writing
code
to
support
their
articles,
scientists
that
are
writing
code
to
go
through
data.
B
There
are
so
many
more
of
these
people
in
the
world
than
we
even
realize,
and
that
number
is
only
going
to
get
bigger
in
the
future.
So
this
is
an
amazing
number
for
us,
but
recently
we
started
thinking
what
is
github
in
our
company
in
github.
We
use
it
a
lot.
We
love
the
pull
request
for
many
of
us.
The
pull
request
is
the
focal
point
of
github,
but
when
we
start
asking
people
what
is
get
up
to
you,
we
realize
it
means
something
different
to
everyone.
Some
people
love
the
pull
request.
B
Some
people
love
the
open
source
community.
Some
people
love
that
they
can
use
this
software
behind
their
firewall.
Some
people
love
github
pages
free
static
site
hosting.
So
we
looked
at
that
and
we
said
this
community
is
bigger
than
11
million
people
and
there
are
more
than
11
million
people
using
get
up.
So
how
many
are
there?
B
So
we
undertook
this
large
enterprise,
this
big
project,
where
we
logged
into
Google
Analytics,
and
we
looked
at
how
many
people
use
our
website
and
it
turns
out
36
million
unique
people
visit
github
every
single
month,
so
this
community
is
way
bigger
than
the
people
that
have
signed
up
for
accounts.
It's
way
bigger
than
whatever
number
20
million
comes
from.
B
There
are
36
million
people
downloading
your
code,
reading
your
documentation
playing
with
your
video
game
that
you
publish
to
get
up
pages
every
single
month,
and
this
number
is
rising
rapidly,
the
point
being
that
none
of
us
have
any
idea
how
big
software
has
become
because
it's
moving
so
quickly.
20
million
may
have
been
an
accurate
number
a
couple
years
ago
and
if
it
was
it's
completely
blown
away
by
now,
and
it's
only
going
to
get
bigger
in
the
future.
B
B
This
is
the
part
where
I'm
supposed
to
talk
about
all
the
big
splashy
launches
that
we've
done,
but
I
think
that
at
our
company
we
really
care
about
details.
Details
are
really
what
makes
our
break
a
great
product
experience
and
abroad
example.
That
is
uncanny
valley
right.
If
you've
seen
this
there's
a
there's,
a
point
at
which
a
cartoon
face
starts
to
look
creepy
because
it's
too
close
to
a
human
face,
but
not
a
human
face
right
has
the
details.
B
Your
subconscious
you're,
always
looking
at
an
understanding
and
feeling
the
details,
even
if
maybe
you
can't
express
what
they
are.
So
when
we
talk
about
you,
making
your
life
better,
making
your
work
flow,
better,
pull,
requests
being
great,
we're
talking
about
little
details
that
add
up
to
create
a
better
experience.
So
this
is
something
that
we
shipped
recently
call
protected
branches.
So
now
you
have
way
more
control
over
when
and
why
a
pull
request
gets
merged.
B
You
can
hook
up
things
like
see,
I
to
say
you
can't
merge
this
pull
request
until
CI
passes,
which
basically
gives
you
a
huge
safety
net,
but
because
this
is
an
API
you
can
use
it
for
all
sorts
of
things
you
can
use
it
for
clas.
You
can
use
it
for
hooking
into
another
system.
That
maybe
has
a
processor
need
some
sort
of
sign
off
it
doesn't
matter.
B
We
want
to
help
make
your
workflow
easier
and
the
less
you
have
to
go
to
a
separate
document
to
use
a
checklist
and
the
more
CH
built
right
into
github,
the
more
just
part
of
the
way
you
work,
the
better.
We
think
that
experience
could
be
quick
pools.
We
are
big
fans
of
this
concept
called
github
flow,
and
it's
really
what
I'm
talking
about
it's
the
developer
experience
it's
cutting
out
all
the
friction.
B
It's
cutting
out
all
the
steps,
it's
letting
you
focus
on
the
work
you're
doing
and
not
the
work
you
have
to
do
in
order
to
get
there
right.
It's
not
about
configuring,
your
text
editor
or
your
terminal.
It's
about
writing
code
and
thinking
about
hard
problems.
Quick
pools
are
a
way
to
very
easily
from
editing
a
file
launch
into
a
pull
request.
B
It's
just
a
nice
simple
flow
thing
that
we've
done,
but
it
really
embodies
the
spirit
of
what
we're
trying
to
do,
which
is
just
remove
friction
and
make
it
way
easier
for
you
to
get
on
with
your
day
so
attached
files,
controversial
feature,
I
know
you
can
now
attach
files
to
issues.
Look,
not
everything
needs
to
be
and
get
in
fact
there
are
some
things
I
put
and
get
that
I
regret
putting
and
get
not
everything
should
be
in
version
control.
B
Sometimes
you
just
want
to
quickly
share
a
file
quickly
share
a
photo
quickly
share
an
idea.
We
want
to
make
that
really
easy
for
you
and
that's
now
built
into
issues
and
then
does
anyone
use
split
disks?
Does
anyone
ever
use
this?
This
is
amazing
right
when
we,
but
so
design,
is
a
difficult
thing
and
I'm
sure
there's
a
ton
of
designers
here
that
could
talk
at
length
but
have
way
more
experience
than
me.
But
one
of
the
beautiful
things
about
development
and
the
development
community
is
the
diversity
in
every
sense
of
the
word.
B
We
all
have
our
own
favorite
text
editor.
We
all
have
our
own
config
file.
We
all
have
our
own
keyboard
shortcuts
that
not
a
bug,
that's
a
feature.
So
this
is
another
thing
here.
We
have
for
a
long
time
only
use
unified
dips
and
we
had
the
opinion.
Some
of
us
myself
included.
This
was
a
better
way
to
view
diffs.
In
reality,
we
all
work
differently
and
what
we
want
to
do
is
provide
options
that
help
you
work
best.
B
Ok,
we
also
did
have
some
/
she
launches,
so
I
am
gonna.
Talk
about
those
all
right,
so
github
desktop
is
something
we
released
recently.
I,
don't
know
if
anyone's
tried
it
for
a
while.
We
had
a
Mac
application
and
a
Windows
application.
We
put
them
together
into
one
application,
called
get
up
desktop
now,
and
it
should
be
the
quickest
way
to
make
a
pull
request
and
really
my
pitch
to
someone
is,
you
know,
try
it
if
you
already
know
get.
If
you
already
love
your
workflow,
just
give
it
a
shot.
B
Again,
we
want
to
provide
as
many
different
options.
There
are
for
you,
whether
it's
integration
into
something
like
sublime
or
Adam,
a
standalone,
get
a
desktop,
client
or
support
for
get.
We
are
big
fans
of
the
get
project.
There
was
a
major
release
recently
that
we
blogged
about.
We
like
the
options
we
like
the
choice
and
we
want
to
support
as
many
different
choices
as
we
can
so
get.
Ab
Enterprise
I
talked
a
little
bit
about.
B
B
We
want
to
make
great
on-premise
software
if
you,
if
you
need
to
work
behind
a
firewall,
we
want
that
to
work
really
well
for
you,
so
we're
now
up
to
2.3
and
we're
getting
way
better
every
day
at
how
we
release
work
with
customers
and
manage
get
up
enterprise
and
a
part
of
that
is
not
just
saying,
download
a
vm.
Maybe
you
want
to
run
on
AWS.
We
now
have
enterprise
support
for
that
which
we
launched
last
year.
Maybe
you
want
to
run
on
Azure
or
any
one
of
the
number
of
clouds
out
there.
B
We
did
a
lunch
earlier
this
year
with
Microsoft,
where
we
unveiled
enterprise
on
Azure
and
pinch
me
I'm
dreaming.
We
have
github
built
into
visual
studio
now
as
an
open-source
plug-in
supported
by
microsoft
right.
That
is
absolutely
incredible.
So
now,
if
you
want
to
use
github
from
within
visual
studio,
all
you
need
to
do
is
download
visual
studio.
It's
there,
you
can
install
it
by
default.
You
can
look
at
the
code,
it's
on
open
source,
we're
collaborating
with
Microsoft.
It's
really
amazing
and
I
huge
fan
of
Microsoft
these
days,
so
good
work,
everyone.
B
It
feels
very
weird
saying
that
as
a
person
that
came
from
the
Linux
world,
but
we
are
in
a
new
age
like
I'm
saying
things
are
changing
faster
than
we
may
even
realize,
so
the
student
developer
pack
is
something
else
we
did
that
I'm
really
really
in
all
of
so
when
I
was
in
college.
Is
anybody
from
Adobe
I
used
to
pirate
Photoshop?
Okay,
like
when
I
was
in
college?
I
would
just
steal
software
and
I'm
sure?
Don't
quote
me
on
that?
Why
it's
because
I
couldn't
afford
photoshop,
I
would
have
paid
for
it.
B
I
would
have
liked
to
pay,
for
I
supported
it's
a
great
piece
of
software.
I
could
I
could
easily
afford
BitTorrent
right.
It's
a
lot
harder
to
torrent
github,
it's
a
lot
harder
to
torrent
github.
So,
but
we
still
want
to
give
that
to
students.
We
still
want
kids
to
use
professional
grade
tools,
the
same
thing
that
engineers
at
NASA
and
Facebook
are
using.
So
the
student
developer
pack
is
our
way
to
do
that.
We
have
over
a
quarter
of
a
million
students
that
have
signed
up
to
this
pack
and
they
get
free
github.
B
But
that's
not
all
we
have
stripe.
We
have
digital
ocean,
the
same
tools
that
you
use,
either
at
a
hackathon
or
to
build
your
massive
company.
Kids
can
now
use
for
free,
they're,
learning
the
same
tools.
It's
really
quite
amazing
and
then
Adams.
Anyone
use
Adam,
it's
cool
yeah.
All
right,
big
fan,
Adam
I
mean
what
is
more
core
to
the
developer
experience
than
the
text.
Editor,
that's
rhetorical,
don't
answer!
We
could
probably
go
a
couple
different
ways,
but
the
text
editor
right.
B
The
thing
that
you
don't
use
to
edit
text
the
thing
you
used
to
write
code,
the
text
editor,
it's
the
cornerstone,
it's
the
stepping
stone.
It's
the
first
thing
you
use.
It
shows
you
the
insides
right.
It
helps
you
tinker.
Adam,
for
us
is
a
is
a
huge
huge
project
and
a
very
important
milestone
and
core
to
our
business.
B
We
want
to
have
your
development
experience
first,
we
won't
be
able
to
take
your
feedback
and
make
that
better,
and
so
there's
one
way
to
do
that,
which
is
a
great
support,
team
and
working
with
customers
and
there's
another
way
to
do
that,
which
is
making
a
totally
open
source
and
free.
So
Adam
is
free,
it's
open
source
and
as
a
thriving
community,
you
can
write
plugins
for
it.
B
It's
all
built
using
web
technologies
and
there's
already
some
incredible
amazing
things
that
have
come
out
of
adam
like
the
electron
project,
so
there's
actually
a
project
that
powers
adam
that
allows
you
to
build
native
applications
and
web
technologies
that
we
release
that
we
support
now
is
being
used
by
slack
by
Facebook
by
Microsoft.
It's
really
incredible.
What's
going
on
and
for
us,
it's
really
amazing
to
see
Adam
take
off
to
over
hundreds
of
thousands
of
active
users
every
month
already
and
a
lot
of
people
that
use
it
and
love
it
myself
included
alright.
B
So
those
are
some
of
the
big
things.
We've
done,
if
you
haven't,
checked
out,
Adam
or
or
Enterprise
your
student
developer
back
I
highly,
encourage
you
to
do
so.
They're
pretty
awesome,
but
it
also
would
not
be
a
keynote
if
I
did
not
announce
something
new,
so
I
have
some
new
stuff
to
talk
about.
So
this
is
the
first
one.
This
is
probably
one
of
the
most
requested
features
in
the
history
of
I'm,
just
going
to
say
the
universe,
because
we're
at
universe,
right,
large
files,
support,
forget
and
github.
B
You
want
to
use
git
and
github
with
massive
files,
either
graphic
files,
terabyte
lot
large
files,
PDFs
datasets
or
just
like
a
big
image
right.
It's
been
a
huge
problem.
Get
has
never
been
good
at
that
due
to
some
of
the
it's
a
trade-off
that
they
get
community
made.
It
is
very
strong
at
some
things,
but
what
you
don't
get
is
the
large
file
support.
B
However,
we've
been
working
very
hard
on
creating
an
open
source
project
called
get
lfs
and
integrating
it
into
github,
and
we're
very
happy
to
announce
today
the
public
availability
of
git
LFS
for
github
users.
So
after
this
talk,
you
can
go
to
the
blog
post.
You
can
read
more
about
it.
You
can
download
the
software.
You
can
enable
your
for
your
organization,
and
now
you
can
throw
anything
you
want
just
give
us.
Your
database
dumps
huge
files
like
your
family
photos.
B
No,
don't
do
that
I'm
kidding,
but
now
you
can
store
large
files
in
git
and
github
with
ease
and
not
just
us.
There's
going
to
be
a
session
on
this
later
today,
we're
working
with
it
last
seen
on
this
we're
working
with
Microsoft
on
this.
We're
really
really
excited
about
this
feature.
We
really
believe
in
the
get
ecosystem.
We
think
this
is
going
to
be
a
huge
huge
part
of
it
so
check
it
out.
It's
generally
available
today
really
excited
about
that.
We've
been
working
out
for
a
long
time,
yeah.
B
All
right
number
two,
so
you
probably
have
seen
this
and
if
not
you're,
going
to
see
it
a
lot
over
the
next
couple
days.
We
think
about
software
development.
The
software
development
experience
in
many
different
ways,
one
of
the
ways
that
we
think
about
it
is
in
three
phases:
build
collaborate,
deploy
and
actually
I.
Think
you
could
make
the
argument
that
this
is
collaboration
right
when
you're
working
on
a
legal
document.
You
know
I'm,
not
a
lawyer,
but
you
write
it
you
get
reviews
and
then
it
becomes
whatever
it
becomes
right.
B
You're
working
on
a
movie
script,
you
do
the
first
drafts
you
do
a
bunch
of
reviews
it
gets
thrown
out.
You
start
over
there's.
Ten
years
later,
the
movie
hasn't
been
made.
Eventually
it
gets
shipped
right.
This
is
a
one
view
of
the
creative
process
and
we're
very
much
embracing
this
at
github.
We
think
that
this
is
a
very
good
way
to
think
about
software
and
even
better
way
to
think
about
tools
that
are
involved
in
the
software
development
process.
B
So
we're
very
excited
today
to
announce
the
launch
of
something
we've
been
talking
about
and
working
on
for
a
long
time,
which
is
called
our
integration
directory.
So
we've
partnered
with
some
really
awesome
development
tools
in
the
three
phases
of
building
collaborating
and
deploying
we've
made
it
super
easy
for
you
to
find
these
tools
to
read
about
them,
and
we've
made
it
even
easier
for
these
partners
to
build
and
give
you
an
amazing
experience.
We've
always
had
a
really
good
API.
It's
always
been
very
open.
B
B
It's
another
thing
to
have
the
support
of
get
up
the
company
to
be
able
to
talk
to
us
to
be
able
to
work
with
us
on
really
deep
integration,
and
it's
another
thing
to
have
this
be
an
easy
experience
right.
Why
are
you
going
to
Google
to
find
out
the
best
CI
for
Ruby
on
Rails
to
use
with
github?
You
should
be
able
to
go
to
github
and
see
what
the
options
are.
What
do
other
github
users
use?
What
do
people
like
me
that
are
building
software
like
me?
B
What
do
they
use
to
develop,
which
one's
actually
work
really
well
and
which
ones
are
curated
and
hand-picked
and
selected
by
github?
So
now
you
can
do
that.
We're
launching
that
right
now
you
can
check
it
out
on
the
blog,
if
you're
interested
in
building
applications
with
github,
we
want
to
work
with.
You
definitely
check
it
out
and
now
adding
plugins
such
as
slack
Circle,
C
I
Travis
is
going
to
be
easier
than
ever,
and
this
is
just
the
starting
point
for
us.
B
We're
going
investing
very
heavily
in
integrations
in
the
ecosystem
and
we're
just
super
super
excited
to
do
this
because
we
come
from
a
world
like
I
said
where
we
use
lots
of
different
tools.
There
are
different
ways
to
use
get.
There
are
different
issue
trackers
the
day
we
launched
get
up
issues.
We
had
a
disable
button
because
we
said
we
want
you
to
use
this.
We
think
it's
pretty
good
if
you
want
to
turn
it
off
and
use
a
different
issue
tracker.
We
want
to
work
really
well
with
that.
B
We
understand
that
choice
is
a
very
powerful
thing
for
developers
and
now
we're
helping
make
those
choices
easier,
more
prominent
and
hopefully
higher
quality.
So
we
want
to
work
with
the
best
in
breed
tools
all
over
the
world
to
help
make
your
development
workflow
experience
way
better,
and
so
the
integration
directory
is
a
place
for
us
to
start
doing
that.
Have
the
conversations
and
show
you
the
stuff
that
we
think
is
awesome,
so
I'm
really
excited
about
that
as
well,
and
then
I
have
a
third
thing.
I'd
like
to
talk
about.
B
So
it's
hard
to
imagine
that,
like
10
years
ago,
we
were
not
using
SSL
and
we
were
storing
our
passwords
in
plain
text
and
some
of
you
weren't,
but
a
lot
of
us
work.
Okay,
that's
absolutely
ridiculous!
The
Internet
has
this
naive,
misguided
design
principle
that
you
can
trust
people
right
and
that
has
not
worked
out
so
well.
I
mean
mostly
it's
worked
out,
so
we
have
about
three
billion
people
on
the
internet,
but
there
are
some
bad
actors
on
there
and
really
there
are
some
mistakes
that
people
can
make.
B
A
part
of
thinking
about
security
is
protecting
you
from
someone
who
wants
to
do
something
bad
and
part
of
it
is
just
protecting
yourself.
Part
of
it
is
building
in
safeguards.
So
you
don't
make
a
mistake,
so
you
don't
drop
a
production
database
which
some
people
in
this
room
have
done,
which
is
me
so
there
are.
B
There
are
things
that
you
sometimes
want
to
put
in
place
to
help
yourself
and
safeguard
yourself,
so
I
think
that
security
is
going
to
become
one
of
the
most
important
topics
in
software
and
the
next
ten
years,
and
that
may
sound
obvious,
but
I
don't
think
we
scratched
the
surface.
Yet
you
go
to
the
news.
You
see
every
day,
another
target
another
Sony,
another
Ashley
Madison,
we're
just
at
the
beginning
of
that
right.
Security
has
not
been
top
of
mind
for
developers.
It
has
not
been
top
of
mine
for
educators.
B
It
has
not
been
something
that
we
built
in
to
our
software.
If
anything,
it's
been
this
scary
world
of
academics
and
researchers
that
a
lot
of
new
beginners
are
afraid
of
and
sort
of
just
go
with
common
knowledge
that
has
to
change.
We
need
to
get
way
better
at
security.
Part
of
it
is
because,
like
I
said,
the
internet
is
getting
bigger.
Part
of
it
is
because
it's
been
getting
more
important
right.
We're
storing,
really
important
source
code,
really
important
medical
data
really
important
family
photos
on
the
internet.
We
weren't
doing
this.
B
20
years
ago
we
were
giving
amazon
our
credit
card
in
plain
text
right
and
then
they
were
sent
us
some
books.
It
was
way
different,
so
for
the
next
10
years,
security
is
going
to
become
one
of
the
most
important
things
and
technology
and
everyone
building
development.
Everyone
developing
needs
to
think
about
it
and
if
you're
not
thinking
about
it
today,
we
have
some
cool
stuff
to
talk
about
that.
We
hope
you'll
be
excited
about.
A
Some
cynics
say
that
the
game
is
over,
that
the
security
threats
and
the
breachers
we
see
today
are
so
bad
that
there
is
nothing
to
do
about
it.
I,
don't
agree
and
I'm
very
honored
to
be
here
today
to
share
why,
a
few
years
ago,
I
had
an
online
bank
where
they
told
me
that
I
could
log
in
with
a
username
password
a
software
certificate
that
I
downloaded
on
my
computer
with
that
my
bank
account
would
be
hacked.
A
I
mean
I'm,
not
sorry
that
my
bank
account
would
be
safe,
but
I
happen
to
know
a
banker
I'm.
Sorry,
a
hacker,
a
former
hacker.
This
hacker
told
me
that
it
would
take
him
a
day
to
write
the
code
to
hack
in
an
empty.
My
bank
account
so
to
inform
the
bank
about
this
security
risk.
I
called
him
up
and
I
got
a
very
clear
and
simple
answer
on
the
other
side
of
the
line.
A
We
developed
you
Becky,
it's
a
small
key
that
you
can
plug
into
the
USB
port
of
your
computer
or
you
can
tap
it
to
your
phone
and
when
you
use
it,
it
generates
new
encrypted
pass
codes.
Every
time
you
log
in
we
put
the
open
source
code
behind
this
on
github
and
we
shipped
these
keys
by
selling
them
online
250
countries
to
developers
to
geeks
to
political
leaders
all
over
the
world,
and
we
made
it
easy
for
developers
like
you
to
take
the
code
and
protect
your
computer's
networks
and
services.
A
So
one
day,
I
got
an
email
from
one
of
the
large
Internet
giants
here
in
sinkhole
at
Silicon
Valley.
They
said
they
had
integrated
the
key.
They
thought
it
was
awesome
and
asked
for
a
quote
for
20,000
units.
I
had
not
been
speaking
with
them,
they
already
integrated.
They
already
know
how
it
worked.
No
sales
questions
asked
at
the
time
I
convinced
the
former
hacker
who's.
By
the
way,
the
CEO
of
my
company,
and
also
the
my
husband
and
the
father
of
my
three
children,
I.
A
Convinced
him
to
move
here
from
stockham
to
develop
a
new
open,
authentication
standard.
We
approached
google
and,
together
with
the
google
security
team
and
nxp,
we
develop
you
to
f
universal
second
factor.
You
to
f
enables
simple
hardware
back
keys
like
the
Yubikey
to
work
across
any
online
service.
A
It's
based
on
public
key
crypto,
really
strong,
great
security
that
protects
against
roy
ins,
fishing,
man-in-the-middle
attacks,
but
without
that
whole
complexity
of
readers,
client
software
draw
drivers
and
costly
CAS,
and
this
is
a
secret.
It's
native
support
in
platform
and
browsers.
It
just
works
out
of
the
box
just
plug
and
play,
and
the
beauty
with
this
is
that
when
you
signed
up
a
key
to
a
service,
it
generates
a
new
set
of
encryption
secrets
that
are
only
stored
on
that
Pacific
service.
There
is
no
secrets
or
personal
data
shared
between
the
service
providers.
A
With
that
way,
we
can
build
a
really
highly
secure
and
scalable
authentication
ecosystems
where
there
is
not
a
single
service
provider
or
a
single
database.
Let's
store
your
secrets
or
share
your
secrets
and
can
be
hacked
so
since
Google
deployed
this
for
all
staff
and
may
support
in
gmail,
they
have
seen
really
good
stats.
It's
four
times
faster.
Forty
percent
support
reduction
and
a
significant
fraud
reduction
compared
to
the
mobile
app
Google
Authenticator,
and
here
today
we
have
a
present
for
you,
this
little
token
that
you
all
got
in
your
conference
bags.
A
It
begins
by
accepting
that
we
can
move
the
trust
to
a
small
key
that
would
put
in
our
pocket,
and
that
is
not
connected
to
the
Internet,
and
we
build
a
secure
link
between
the
key
and
the
service
we
wanted
to
connect
to.
With
this,
we
can
build
a
new
distributed
and
highly
scalable
trust
model
for
the
internet
and.
A
B
Awesome.
Thank
you.
Thank
you.
Amazing.
We're
really
really
excited
to
be
working
through
bacot
to
announce
that
today
and
github
now
supports
it,
but
I
implore
all
of
you
building
software
building
applications
to
support
it
to
look
into
it.
Think
about
security.
Take
it
seriously,
it's
a
huge
huge
deal
and
it's
getting
easier.
It's
getting
easier
to
do
the
right
thing
to
be
secure
and
to
beat
the
fraudsters
so
really
really
happy
and
check
out
the
session
later.
Today,
all
right
I
want
to
talk
a
little
bit
about
open
source.
B
It's
kind
of
a
it's
kind
of
a
thing,
that's
happening,
I,
don't
know.
If
you
all
know
there
are
over
twenty
seven
million
open
source
projects
on
github
today,
right
three
years
ago
there
was
like
1,000,000,
it's
ridiculous
and
that's
2012
right
I
thought
2012
was
the
future.
There
were
movies
about
it
right.
I
thought
that
was
the
end
of
everything
turns
out
it
wasn't.
Even
the
beginning,
open
source
is
growing
at
a
tremendous
rate
right.
This
is
just
on
github
right.
It's
a
big
deal,
but
I'll
be
honest.
I
said
this
couple
times.
B
I
don't
know
what
27
million
means
it's
just
like
too
big
I
don't
get
it
there's,
maybe
how
many
people
here,
five
million
six
million,
like
it's
just
too
big
to
even
understand
or
reason
about.
So
what
does
this
mean?
What
does
it
look
like?
What
is
it?
What
does
it
actually
mean
to
us
as
people
every
day,
1,000
people
create
their
first
public
pull
request
ever
that's
a
thousand
people
that
are
contributing
to
open
source
for
the
first
time
that
are
using
github
that
are
helping
build
software
for
the
first
time
every
single
day.
B
That's
absolutely
incredible.
That's
new
people
right
and
then
the
other
side
of
it.
Five
thousand
different
people
every
single
day
create
their
first
public
repository.
There
was
a
point
in
time,
not
that
long
ago,
when
there
were
5,000
open
source
projects
total
now
that's
happening
every
single
day
and
I.
Think
there's
a
lot
of
reasons
for
that.
B
I
think
one
of
the
reasons
is
the
barrier
to
entry
it's
become
so
low
and
the
definition
of
an
open
source
project
has
become
so
broad
that
now
we
are
encouraged
to
share
everything
the
smallest
snippet,
the
little
idea,
thus
wknd
hack
a
couple
years
ago,
a
decade
ago.
It
was
an
onerous
task
to
run,
maintain
and
publish
an
open
source
project.
Now
it's
almost
easier
to
just
throw
your
stuff
up
on
github
and
forget
about
it
than
it
is
to
keep
it
on
your
hard
drive
and
let
it
collect
dust.
B
So
it's
really
amazing
how
open
source
itself
is
changing
in
terms
of
adoption
numbers
and
just
what
it
even
means.
So
I
want
to
share
some
of
my
favorite
projects
that
popped
up
over
the
past
year
so
and
people
that
get
up
know
that
I
have
a
pretty
great
taste
in
weird
stuff.
So
here's
the
first
one.
This
is
called
term
you
I
it's
written
and
go.
This
is
a
terminal
library
that
lets
you
create
real
time
graphs
in
the
terminal.
B
So
if
you
want
to
recreate
war
games,
if
you
reject
this
notion
that
the
developer
is
changing
and
want
to
go
back
to
nineteen,
eighty
seven
or
whatever,
we've
got
you
okay,
you
can
work
all
in
the
terminal.
You
can
create
these
on
your
own.
It's
an
amazing
library,
I'm,
a
huge
fan
of
it.
There's
even
a
map
that
you
can
get
in
it.
So
highly
recommend
checking
out
turn
you.
This
is
an
amazing,
open
source
project.
B
Anyone
play
starcraft
or
did
they
ever?
Apologies-
apologies
to
adobe
before
apologies
to
blizzard.
Now
I
don't
know
if
this
is
this
is
cool
or
not,
but
someone
has
recreated
starcraft
entirely
in
HTML
and
javascript
and
published
it
on
github
pages.
So
any
of
you,
please
don't
do
it
on
the
Wi-Fi.
Any
of
you
can
go
and
play
starcraft
in
your
browser
now
a
version
of
it
on
github
pages.
It's
absolutely
incredible
right,
it's
absolutely
incredible!
Again!
Sorry
blizzard,
but
there's
just
really
cool
stuff
happening
and
a
lot
of
it's
just
for
fun.
B
A
lot
of
it
is
thought
experiments.
A
lot
of
it
are
just
new
ideas.
Not
all
of
it
is
enterprise-grade
software,
even
that's
a
huge
part
of
it
as
well,
and
those
are
fun
and
the
third,
but
the
third
one
I
wanted
to
talk
about
is
this
thing
called
a
cat.
So
this
is
the
software
that
powers,
the
system
that
stephen
hawking
uses
to
communicate.
I'm
sure
we've
all
heard
the
the
computer
voice
that
he
uses
it's
powered
by
software
and
it's
a
very
complex
input
system.
B
It's
really
fascinating
to
dive
into
this,
to
see
how
exactly
he
does
talk
and
communicate,
and
what
this
software
does
intel
has
created
it
and
recently
they
released
it
open
source
on
github.
So
this
is
something
that
anyone
can
use
now
you
can
play
with.
You
can
contribute
to
there's
some
really
really
amazing
stuff
like
this,
that,
while
starcraft
is
fun,
helping
people
that
aren't
able
coming
to
communicate
communicate
is
just
absolutely
mind-blowing.
This
is
another
great
example:
it's
not
an
enterprise
project.
B
This
probably
may
not
have
been
an
open
source
project
a
decade
ago,
but
now
it's
available
pushed
and
supported
by
intel.
So
those
are,
those
are
three
things
I
really
like
and,
of
course,
there's
a
lot
of
other
cool
stuff
going
on
too
there's
a
lot
of
name
and
open
source,
which,
in
and
of
itself,
is
an
incredible
concept
that
we're
in
a
place
where
oh
yeah
docker,
oh
yeah,
rails.
Oh
yeah,
my
signal,
we
know
about
that.
That's
that's
that's
real
stuff!
Everyone
uses
it
the
biggest
web
sites
in
the
world
use
these
applications.
B
These
frameworks,
these
libraries
to
do
open
source
and
they
actually
contribute
back.
This
is
now
just
standard
operating
procedure,
as
I
think
we
all
know-
and
part
of
that
is
the
companies
are
changing.
Like
I
said
thinking
of
Microsoft,
doing
open
source
is
pretty
remarkable,
10
or
so
years
ago,
Ballmer
set
on
an
earnings,
call
that
open
source
was
communism
right
and
I.
B
Don't
nobody
meant
by
that?
Exactly,
but
now
Microsoft
is
a
huge
proponent
of
open
source,
not
just
on
our
visual
studio,
plugin
Microsoft
last
September
release
dotnet,
which
is
there
basically
Java
competitor,
it's
their
platform
for
building
enterprise
and
all
sorts
of
different
software.
It's
been
around
for
over
a
decade,
really
awesome.
It
basically
runs
a
huge
chunk
of
the
world.
It's
now
completely
open
source,
it's
available
on
mac
and
linux,
and
in
only
the
first
few
months,
Microsoft
got
more
contributions
from
the
community.
Then
they
ever
got
internally.
B
There
are
more
external
non-microsoft
employees,
who've
contributed
to.net.
Then
there
are
Microsoft
employees,
that's
really
amazing,
they're,
actually
using
open-source
to
further
their
business
goals.
It's
not
just
a
toy
and
the
other
thing
that's
really
important
there.
The
other
nuanced
I
think
we
all
know
is
that
it's
not
just
people
throwing
code
at
net.
It's
not
a
Wikipedia
model
where
you
go
in
afterwards
and
have
to
remove
and
censor
the
edits.
Every
single
contribution
to
net
was
approved
by
a
Microsoft
employee
or
someone
that's
on
the.net
core
team.
B
In
many
cases,
software
gets
better
when
it's
released
as
open
source,
because
you
have
to
go
through
the
process
of
documenting
the
tribal
knowledge
that
you
and
your
coworkers
have
sort
of
known.
You
can't
just
go
to
Bob
or
go
to
Susan
anymore.
You
have
to
write
it
down
and
make
it
something
that
anyone
in
the
world
can
read
understand
that
forces
you
to
think
that
forces
you
to
talk
about
what
are
the
contributions.
What
are
our
standards,
so
open
source
is
really
I.
Think
elevating
the
craft
of
software
development
in
the
quality.
B
At
the
same
time,
it's
helping
companies
further
their
business
goals
and
it's
giving
us
stuff
like
Starcraft
in
the
browser.
So
I
don't
know
what
this
is.
I,
think
it's
a
microchip
or
a
transistor
I've,
never
been
much
of
a
hardware
person,
but
I
was
recently
lucky
enough
to
see
Gordon
Moore
at
a
fireside
chat
of
moore's
law
and
Tom
Friedman
was
the
interviewer
of
the
world
is
flat,
which
is
an
awesome
book
and
Gordon
must
be
in
his
late
70s
or
80s.
B
At
this
point,
I
mean
Moore's,
Law
is,
is
decades
old
and
the
interview
was,
you
know.
How
did
you
come
up
with
Moore's
law?
What
were
you
thinking
at
the
time?
How
were
you
so
damned
correct
about
everything?
If
you
look
at
the
original
Moore's
law
article
that
he
wrote
for
like
hardware
magazine
or
something
he
talks
about
having
computers
on
your
watches,
he
talks
about
carrying
around
computers
and
connecting
to
everyone
in
the
world.
He
talked
about
having
information
at
your
fingertips.
B
It's
all
this
stuff
that
came
true
and
its
really
really
remarkable
and
Tom
Friedman
asked
him
what
has
surprised
you.
He
said
social
networks
he's
like
I,
didn't
think
people
would
use
computers
just
to
chat,
share
baby
photos,
but
that
seems
to
be
the
number
one
thing
and
I
think
that's
sort
of
funny,
but
there's
something
Court
of
that
right:
computers,
connect
us
hardware,
brings
people
closer
together.
The
internet
is
so
magical
because
it
really
connects
the
world
and
that's
a
lot
of
what
Tom
Friedman
wrote
about
in
his
book.
B
The
world
is
flat,
so
treatment
asked
more:
what's
next:
what's
the
next
Moore's
law
and
Gordon
Moore
who's
really
funny,
and
all
this
was
like
it.
Don't
ask
me
like
I've,
no
idea
go,
ask
someone
young,
but
he
said
something
that
I
really
really
that
really
struck
me.
He
said
we
just
seen
the
beginning
of
what
computers
can
do
for
us,
and
this
is
a
guy
that
invented
Moore's
law
and
he's
watched.
It
come
true
over
decades
and
decades
and
decades
he's
watched
science
fiction
become
reality
and
he
thinks
we
haven't
even
scratched
the
surface.
B
Yet
he
can't
predict
what's
going
to
happen
in
the
future,
but
he
knows
we
haven't
even
started
and
when
he
says
computer
he
doesn't
mean
desktop
software
or
desktop
hardware
right,
he
doesn't
mean
mainframe,
he
means
anything,
that's
run
by
programming,
anything
that's
run
by
software
or
some
sort
of
embedded
hardware
device.
We've
just
seen
the
beginning
of
really
what
software
hardware
and
technology
can
do
for
us,
I
think
the
last
century,
the
20th
century.
You
could
make
the
argument.
It
was
all
about
Hardware
planes,
cars
assembly
lines,
computer
chips.
B
There
is
a
lot
of
amazing
innovations
in
hardware
that
transformed
the
way
we
all
live,
and
you
know
a
lot
of
that
was
here
before
we
were
born
and
it's
just
become
more
and
more
miraculous.
Since
we've
been
alive,
that's
changing
now
it
used
to
be
that
the
constraint
was
on
processing,
speed
right,
we
get
enough
processors,
we
couldn't
get
enough
bandwidth,
that's
not
the
case
anymore.
I
bet.
Some
people
here
have
spun
up
AWS
instances
in
this
talk
or
created
a
new
digital
ocean
thing.
B
You
can
get
hard
where
you
can
get
CPUs,
it's
not
that
difficult
anymore
and
that's
becoming
more
and
more
adequate
asst,
which
cheap
for
us
now
is
becoming
even
cheaper
for
everyone
else
in
the
world.
So
the
constraint
is
no
longer
hardware
or
it's
quickly
becoming
not
the
main
constraint.
Well,
what
is
it?
That's?
Why
we're
here?
It's
software
software
is
now
the
constraint,
the
lack
of
software,
the
lack
of
ability
to
produce
effectively
and
efficiently
software,
the
lack
of
speed
behind
creating
new
software,
turning
ideas
into
reality.
B
That's
the
constraint,
and
that's
only
going
to
get
worse
the
more
hardware
we
have
the
cheaper.
It
is
for
computers
to
be
in
every
part
of
our
lives
from
light
bulbs
to
our
smoke
machines,
the
more
we're
going
to
need
software.
We
don't
have
enough
right.
We
think
there
are
20
million
developers,
I'm
skeptical,
it's
not
nearly
enough,
as
I
said
before,
there
are
only
three
billion
people
on
the
internet,
only
that's
less
than
half
the
world.
B
What
happens
when
there
are
seven
billion
people
on
the
internet
they're
going
to
want
a
lot
more
software,
we're
not
equipped
to
deal
with
that.
We
don't
have
enough
software
already.
We
all
know
about
the
tech
job
market.
It's
only
going
to
get
worse
as
software
permeate
into
every
single
corner
of
the
globe.
I
really
think
that
software
is
going
to
become
the
biggest
driver
of
change
in
human
history
and
I.
Think
if
you
look
at
the
last
century-
and
you
looked
at
1915
compared
to
1999
we're
in
1915
right
now,
we
have
no
idea.
B
We
can't
even
predict
we
don't.
The
Moore's
law
won't
even
be
invented
for
the
next
20
25
30
years
right.
We
have
no
idea
what
it's
going
to
do,
but
I
do
think
that
we
have
not
even
seen
the
beginning
of
what
software
is
going
to
do
for
us,
and
what's
interesting,
is
that
when
you
want
more
software,
you
can't
just
build
a
bigger
factory.
You
can't
just
add
another
assembly
line.
You
can't
just
outsource
it
to
a
bigger
machine
right.
The
only
way
you
can
get
more
software
is
through
people.
B
You
either
have
a
person
that
writes
more
better
code
or
less
better
code,
or
you
have
more
people
writing
software.
The
only
way
to
get
more
software
right
now
that
we
know
about
until
the
AI
thing
happens
is
people.
So
it's
really
coming
coming
quite
fascinating.
That
the
last
century
was
about
hardware,
and
this
century
is
about
people
more
and
more.
I
think,
as
software
and
hardware
permeates
our
lives
as
the
menial
has
get
automated
away,
it
really
is
going
to
unlock
the
true
potential
of
humans
right.
B
Our
creativity
is
the
thing
that
we
can't
outsource
the
robots
right
now
we
can
outsource
lifting
boxes
right.
We
can
outsource
all
sorts
of
stuff.
We
can't
outsource
creativity
we
may
never
be
able
to,
but
we
need
that
we
need
your
brains.
We
need
as
many
brains
as
possible
working
on
software,
helping
us
build
the
future
of
the
world
and
not
just
in
San
Francisco,
not
just
in
North
America,
every
single
corner
of
the
globe.
B
So
this
fills
me
with
a
lot
of
hope
and
it
makes
me
really
excited
because
I
actually
think
humanity
is
going
to
become
more
human
as
we
embrace
technology
in
the
future,
because
software
is
driven
by
human
ingenuity
and
creativity
and
really
that's.
Why
we're
here
right?
This
conference
isn't
about
github,
it's
about
you!
It's
about
the
people
building
software
and,
more
importantly,
it's
about
why
you're
doing
it
who
you're
building
it
for
right,
we're
all
trying
to
make
the
world
a
better
place.
B
One
line
of
code
at
a
time
we're
trying
to
make
art
experience
better
we're
trying
to
make
our
analytics
better
we're
trying
to
make
our
customers
experience
better.
We
are
building
the
future
of
the
world,
whether
we
know
it
or
not,
and
not
in
a
let's
make
a
day
in
the
universe.
Sense
in
the
sense
of
there
are
going
to
be
a
hundred
million
software
developers
in
the
future
they're
going
to
be
way
more
people
that
want
to
be
writing
software.
B
There
is
no
end
to
the
world's
thirst
and
hunger
for
software,
and
we
still
don't
know
what
the
hell
we're
doing
right.
That's
why
we're
here
we're
here
to
talk
about?
How
do
you
build
software?
How
do
you
collaborate?
Which
tools
are
your
favorite?
We
are
just
at
the
beginning
of
this
industry.
That's
going
to
be
the
most
transformative
thing
the
world
has
ever
seen.
I'm
super
excited
about
it.
So
that's
why
we're
here?
It's
about
you!
B
It's
what
people
you're
building
software
for,
and
it's
about
people
right
so
over
the
next
few
days
meet
some
awesome.
People
share
ideas,
tweet
about
good
talks.
You
see
think
about
it,
play
the
starcraft
game,
sorry
blizzard
and
then
go
home
and
build
something,
absolutely
kick
ass,
because
at
the
end
of
the
day,
that's
why
we're
here
right,
we're
all
here
to
build
stuff,
we're
all
here
to
do
great
things,
we're
all
here
to
work
better
with
other
people
and
we're
all
here
to
make
the
world
a
little
better
place
and
in
the
future.
B
When
we
look
back
on
2015
and
we
are
so
embarrassed
by
the
tools
we
use,
it's
not
going
to
be
someone
else
that
got
us
to
this
miraculous
new
world,
where
software
is
running
everything
it's
going
to
be
the
people
in
this
room
and
everyone
you
interact
with.
We
are
the
future.
Our
community
is
the
future
it's
in
our
hands.
We
can
either
wait
and
see
what
happens
or
we
can
be
proactive
and
we
can
make
it
the
future.
B
We
want
to
make
so,
as
you
think,
about
software,
as
you
think
about
documentation,
as
you
think
about
lines
of
code.
Remember
that
what
we're
doing
is
a
really
big
deal
and
what
happens
next
is
totally
totally
up
to
us.
So,
thank
you
very
much
for
listening.
I
hope
you
have
an
awesome,
awesome
conference
and
welcome
to
get
up
universe.
Everyone.
Thank
you.