►
From YouTube: TT200: Introduction to Development
Description
YouTube description:
This is a Tanuki Tech session on 9/8/2020.
For more on Tanuki Tech, see here: https://about.gitlab.com/handbook/marketing/revenue-marketing/sdr/tanuki-tech/
For more on the speaker, see here: https://www.linkedin.com/in/christopher-wang-0835b226/
A
All
right
welcome
to
the
200
levels.
This
class
is
about
application,
development
and
I've
gone
through
so
many
different
sales
trainings
a
lot
of
the
times
when
I
hear
a
sales
training.
That's
about
something
technical!
I
just
think
oh
great,
there's
this
technical
guy,
that's
gonna
talk
about
like
you
know,
technology
and
I
can
tune
out
right,
but
I
really
want
to
talk
about
the
goal
of
this
session.
This
goal
is
to
have
better
conversations
with
developers,
developer,
managers
and
architects.
A
So
and
ultimately,
what
I
want
y'all
to
get
out
of
this
session
is
the
ability
to
speak
their
own
language
with
confidence.
Why
is
that
important?
So
if
you
all
ever
take
the
personas
class,
one
of
the
things
that
I
mentioned
is
that
when
you're
speaking
to
technical
people,
if
you
can
use
their
language,
you're
gonna
have
a
much
higher
response
rate
and
so
we're
not
really
asking
people
to
be
essays.
We're
not
asking
people
to
be
engineers
but
like
if
you
start
using
their
language
more
and
start
talking
about.
A
Like
oh
yeah,
you
know
your
ci
cd,
agile,
blah
blah
blah
stuff.
I
think
that
you're
going
to
get
a
lot
higher
of
a
response
rate
in
terms
of
your
outreach
and
also,
I
think
that
you're
going
to
have
better
conversations,
so
the
specific
goals
for
this
course
are
learn
about
the
life
of
a
developer.
That's
something
that's
really
important
understanding
what
they
care
about,
what
motivates
them
and
their
emotions.
A
I
think
a
lot
of
times
we
talk
about
what
they're
responsible
for,
but
I
want
you
to
understand
what
it's
like
to
be
a
developer,
because
you
can,
if
you
can
better
emphasize
with
them,
you're
going
to
be
able
to
better
have
conversations
with
them.
Obviously
I
want
you
to
learn
about
their
tools
and
workflow,
that's
really
important
and
the
ultimate
deliverable
and
the
thing
that
I
hope
that
you
all
get
out
of
this
session
is
to
once
again
speak
their
language
with
confidence
which
I
think
will
move
the
dial
for
you
all
right.
A
So,
let's
just
jump
right
in
right.
So
before
talking
about
what
developers
do
we
have
to
talk
about
the
businesses
that
they're
a
part
of?
Ultimately
it's
all
about
applications?
Why?
Because
the
businesses
that
they
work
for?
That's
how
they
make
money,
so
businesses
make
money
off
of
their
applications
and
you
need
developers
to
create
and
maintain
these
applications
right.
So
what
are
the
different
types
of
applications
that
we
have?
So
we
have
things
like
web
applications?
That's
like
netflix.
You
have
iphone
applications,
android
applications
for
your
phone.
A
A
So,
in
a
traditional
like
regular
business
like
let's
just
say
that
this
is
like
a
family
run,
you
know
establishment.
So
someone
took
out
a
huge
business
loan
to
get
this
establishment
and
they
know
that,
like
this
is
going
to
be
their
long-term
source
of
family
substance
right,
so
they
probably
spent
hundreds
of
thousands
of
dollars
into
the
store
in
business
itself
and
how
they
attract.
Clients
is
basically
whether
or
not
this
business
survives
or
fails
right.
A
So
every
single
thing
about
this
traditional,
brick
and
mortar
store
it
matters,
so
they
think
about
the
color
scheme.
They
think
about
the
location.
A
A
D
B
C
A
Yeah
exactly
so,
you
know
things
that
they
think
about
is
what
is
my
target
population?
Well,
it's
probably
young
families
and
children.
So
how
can
I
cater
to
that
population
just
like
that
for
traditional,
like
electronic
business,
like
amazon,
amazon
actually
spends
millions
of
dollars
every
year,
hiring
psychologists
and
sociologists
and-
and
they
actually
do
incredible
amounts
of
behavior
studies
on
color
schemes
for
their
website
how
to
cater
to
each
specific
type
of
population?
A
How
can
we
create
a
website,
that's
engaging
for
every
type
of
population
and,
if
you
just
think
about
it,
the
difference
between
this
store
having
a
colorful
storefront
and
one
that's
a
little
bit
plain,
maybe
20
of
sales.
The
difference
in
this
store,
having
like
a
good
location
in
the
middle
of
your
town
center
and
one
that,
like
you
know,
isn't,
is
a
little
bit
further
to
get
away
with.
Then
that
could
be
whether
your
business
survives
or
fails.
A
So,
in
terms
of
things
like
amazon.com,
the
ability
to
have
an
engaging
and
fun
and
intuitive
website
makes
a
difference
between
twenty
thirty
percent
difference,
year-over-year
compared
to
an
average
website,
so
there's
tons
of
research
and
investment
that
goes
into
building
out
these
websites
and
all
of
that
takes
developers
right.
So
that's,
ultimately
what
developers
do
is
that
they
maintain
these
e-businesses
and
electronic
applications.
A
So
how
do
you
stand
out
we're
in
a
competitive
marketplace
in
technology?
It's
often
a
winners,
take
all
market,
and
so
what
I
mean
by
that
is,
it's
not
like
you
know
a
town,
and
you
have
enough
of
a
population
to
support
three
hardware
stores
in
an
e-business.
Usually
one
person
wins
out
and
everyone
else
gets
kicked
out.
So
these
are
things
that
every
vp
and
cto
that
we
talk
to
they
think
about
is
what
is
my
competitive
advantage
on
every
other
business?
A
A
Other
things
is
like.
How
do
I
stand
out
as
my
e-business?
I
want
to
have
my
best
virtual
storefront.
This
is
the
reason
why
I
hire
all
of
these
sociologists
that
go
to
university
of
wisconsin
berkeley,
to
study
human
nature
and
do
hip
behavior
studies
so
that
I
can
have
the
most
interactive
experience
compared
to
my
competitors.
If
I
even
have
a
two
percent
better
website
than
someone
else,
then
that's
going
to
result
in
billions
of
dollars
for
me
year
over
year
for
something
like
amazon,
just
think
about
uber
versus
lyft.
A
A
Let's
just
talk
about
some
examples,
so
amazon
has
gone
up
their
revenue
around
three
times
in
the
last
five
years,
so
literally
plus
300
percent
in
terms
of
revenue
and
one
of
their
fundamental
strategies
is
to
basically
just
be
able
to
sell
more
in
different
things.
So
if
you
fast
forward
10
years
ago,
they
sold
books
and,
as
you
know,
time
progressed,
then
they
started
selling
household
things
and
then
just
look
at
the
things
that
they've
added
in
the
last
couple
of
years.
A
So
you
can
now
get
homemade
crafts
because
they
own
etsy,
you
can
get
groceries.
They've
made
a
ton
of
money
off
of
groceries
because
of
coronavirus
because
they
don't
now
own
whole
foods.
They
have
their
own
video
streaming
service,
so
they
own
prime
video.
I
was
using
that
this
weekend,
but
they
even
own
like
in
terms
of
the
gaming
market.
A
Twitch
is
the
most
popular
gaming
platform
right
now
and
they
own
it
right
so
they're
just
expanding
their
business
and
as
they
expand
their
business
in
terms
of
features,
that's
ultimately
how
they're
able
to
drive
revenue.
A
Let's
talk
about
speed
next,
so
this
is
something
that
people
don't
think
about,
but
it
matters
a
lot
and
there
are
tons
of
engineers
that
work
for
amazon,
microsoft,
google,
that
basically
they
have
master's
degrees.
They
get
paid
a
hundred,
fifty
thousand
two
hundred
thousand
dollars
a
year
to
basically
just
optimize
speed.
So
I'll
just
give
you
some
statistics
pinterest,
which
is
some
website
increased
signups
by
15
percent
after
it
reduced
their
wait
times
by
40.
So
I
had
an
engineering
investment
into
the
speed
of
my
website.
A
I
get
15
more
customer
engagement
right.
So
what's
the
cash
value
of
that
over
a
three
year
time
horizon
british
broadcasting
corporation,
which
is
they
found
that
they
lost
10
percent
of
users
for
every
additional?
Second,
their
site
took
the
load,
and
this
is
a
big
problem
for
them,
because,
ultimately,
how
they
get
money
is
through
ad
revenue
right.
So,
if
I'm
losing
10
percent
of
users,
that's
10
of
my
revenue
stream.
A
Google
found
that
53
of
mobile
website
visits
were
abandoned
if
a
site
took
longer
than
three
seconds
to
load.
So
this
is
what
engineers
work
on.
This
is
what
they're
paid
to
do
is
to
optimize
and
build
out
applications
to
help
out.
An
electronic
business
on
the
bottom
over
here
is
the
annual
financials
for
amazon.com,
as
you
can
see
in
2015
that
we're
at
100
bill
at
2019.
There
are
300
bills,
so
literally
3x,
right
and
part
of
how
they
were
to
do.
This
is
because
they
were
the
best
in
terms
of
their
competitive
advantage.
A
They
figured
out
weak
if
we
target
x,
y
and
z
versus
our
competition,
we're
gonna
win,
and
so
they
executed
on
the
roadmap
with
this
in
terms
of
features,
and
then
they
also
executed
and
maintained
things
like
site
responsibility
like
site,
like
responsiveness
and
things
like
that.
So
that's
how
ultimately
they
were
able
to
win
is
by
doubling
down
on
their
competitive
advantage.
A
So
now
that
we
have
an
understanding
of
what
developers
do
I'm
going
to
start
talking
a
little
bit
about
the
life
of
a
developer,
I'm
going
to
tell
some
stories
and
I'm
going
to
talk
about
some
of
the
tools
and
the
machinery
that
they
do
so
that
they
use
so
like
once
again
definitely
pay
attention
to
this,
because
I
really
do
believe
that
this
is
going
to
help
you
all
to
have
better
and
more
engaging
conversations
with
your
technical
audiences.
A
So,
let's
dive
right
in
okay
programming
languages,
applications
are
written
in
programming
languages.
So
ultimately,
what
a
programming
language
does
is
it
just
tells
the
machine
to
do
something.
That's
all
it
does,
and
so
there's
different
programming
languages,
just
like
there's
different
languages,
like
you
know
so
like
if
I
wanna,
communicate
that
I'm
hungry
in
english.
I
say
I'm
hungry,
but
if
I
wanna
communicate
that
in
spanish,
then
you
know,
I
just
say:
tango
hombre,
which
is
fundamentally
means
the
same
thing,
but
the
syntax
is
different.
A
That's
the
exact
same
thing
with
programming
languages.
Fundamentally
they
are
all
doing
the
same
thing.
Their
intended
purpose
is
to
just
tell
machines
to
do
something,
but
there's
just
a
different
syntax,
that
they
use
it's
important
to
know
that
some
programming
languages
are
used
for
different
purposes
and
technologies.
So
if,
if
I'm
working
at
mit
doing
big
data
samples,
I'm
probably
using
python,
if
I'm
building
websites,
I'm
probably
using
javascript.
C
A
You're
a
programmer,
you
really
care
about
what
programming
language
you
are.
You
are
investing
in
because
it
takes
around
five
to
ten
years
to
really
get
to
know,
programming
language
well
and
some
of
these
programming
languages
are
disappearing
in
terms
of
their
industry
use.
So
if
you
just
think
about
that,
if
I'm
investing
all
of
this
time
into
getting
better
at
something,
if
people
stop
using
it,
then
my
ability
to
take
home
bread
for
myself
has
basically
dried
up.
A
So
it's
really
important
for
developers
to
know
that
the
tools
that
they
are
using
on
a
day-to-day
basis
that
they
are
being
more
widely
adopted
in
industry,
because,
ultimately,
that's
going
to
increase
their
market
value
people.
Basically,
if
you're
an
engineer,
they
think
about
the
hottest
languages
and
trends
and
stuff,
and
then
they
basically
want
to
learn
that
stuff
to
increase
their
market
value.
A
A
My
personal
take
on
this,
and
hopefully
this
doesn't
get
too
much
repeated-
is
that
gitlab
would
be
better
off
if
it
were
in
python,
but
that's
just
my
personal
opinion,
so
let's
actually
just
do
a
demo
now
I
think
that
sometimes
things
can
get
too
abstract.
So
let
me
just
share
my
screen
with
you
and
let
me
let
me
know
when
you
can
see
my
desktop.
It
should
just
be
the
background
of
my
mac.
A
And
I'm
going
to
show
you
basically
what
this
little
code
thing
that
I
made
does
right.
So,
if
you're
just
going
to
take
a
look
at
it,
it
says
that
like
says
to
print
some
stuff
making
directories
and
then
so
on
and
so
forth.
So
let
me
just
run
this
and,
as
I
run
this
and
hit
enter,
I
want
you
to
pay
attention
to
what
happens
to
my.
A
A
Yeah,
so,
ultimately,
all
this
code,
snippet
does
is
that
it
created
a
bunch
of
folders
and
then
deleted
them,
and
the
takeaway
point
with
this
is
one
you
might
ask
yourself
the
question
of
like
who
cares
right
like
I
can
create
a
folder
right.
Click
click
new
folder,
but
what
happens
and
the
power
of
programming
languages
is
really.
How
do
I
do
things
at
scale
in
an
automated
manner?
So,
let's
just
say
I'm
an
engineer.
A
I
need
to
control
10
000
servers
because
they
need
to
get
updated
or,
like
I
have
10
000,
like
you
know,
sensors
for
an
electricity
grid,
that's
distributed
across
three
states
in
the
united
states.
So
now
with
the
programming
language,
I
can
go
do
that
in
an
automated
and
scaled
way,
as
opposed
to
doing
everything
manually,
anything
that
you
can
do
by
right-clicking
and
creating
folders
and
stuff,
you
can
do
using
this
thing
called
a
terminal
and
ultimately,
what
developers
do
is
they
write
this
code
so
over
here?
A
I
just
want
to
bring
this
point
home
so
a
lot
of
times.
I
think
that
things
can
get
really
abstract.
This
is
get
lab
project
itself.
Fundamentally,
what
gitlab
is
is
that
it
is
a
set
of
text
files
and
over
here
you
can
see
these
exact
text
files.
If
I
go
down
into
this
specific
file
over
here,
it's
just
text,
so
every
single
application,
amazon.com
google
netflix,
fundamentally
literally
everything
that
it
is
and
its
entire
value-
is
that
it's
a
running
set
of
text
files.
So
it's
just
kind
of
interesting
to
think
about.
A
All
right
so
now
that
we
have
understand
what
programming
languages
are
and
what
they're
used
for
we're
going
to
talk
about
libraries
and
dependencies.
So
this
is
a
term
that
we
hear
from
time
to
time.
The
reason
why
it's
important
is
because
git
lab
actually
houses
dependencies,
it's
one
as
part
of
our
value
proposition,
and
what
these
are
is
that
they're,
fundamentally
pre-packaged
chunks
of
code
that
you
can
use.
A
If
you
just
think
about
it,
a
lot
of
developers
are
just
doing
the
same
thing
over
and
over
again
right,
so
to
basically
create
a
button
like
a
one
single
button.
A
website
is
probably
around
100
lines
of
code
and
buttons
are
like
pretty
interchangeable.
All
the
time
you
might
want
to
swap
out
the
color
you
want
to
might
want
to
change
the
design
somewhat,
but
you
can
basically
like
copy
and
paste
this
chunk
of
code
right
and
so
what
a
library
or
dependency
is.
A
Is
it's
like
a
templated
chunk
of
code
that
you
can
use
so
that
you
don't
have
to
copy
and
paste
and
reuse
that
hundred
lines
of
code
over
and
over
again?
So
basically,
what
I
mean
by
that
is
that
there's
libraries
for
creating
buttons,
there's
libraries
for
creating
charts
and
the
whole
point
of
this-
is
that
someone's
already
invented
the
ability
to
do
this.
So
as
opposed
to
you
building
this
out
yourself
just
use
someone
else's
library,
the
vast
majority
of
programmers.
They
specialize
in
just
using
a
few
popular
libraries.
A
So
I'll
give
you
an
example
of
this.
When
I
was
an
engineer,
our
I
was
working
on
a
website
and
our
website
used.
This
thing
called
django
and
django
is
basically
something
that's
used
to
create
apis
people
literally
just
had
their
entire
careers
using
django
and
that's
basically
how
they
got
paid
another
library
that
we
use
a
lot
is
this
thing
called
selenium
and
this
is
web
automation.
So
it's
like
you
can
tell
your
browser
to
like
go
click
on
these
buttons
and
do
it
in
like
a
loop,
10
000
times.
A
The
reason
why
this
is
important
is
that
it's
it's
just
sort
of
like
taking
a
step
back
a
lot
of
times
when
we
look
at
a
website.
We
just
see
this
is
a
website,
but
beneath
the
hood,
there's
actually
a
bunch
of
different
components
that
are
working
together.
This
is
exactly
the
same
as
how,
if
you
look
at
a
car,
you
could
look
at
it
and
see.
This
is
a
car.
This
is
a
honda
accord,
2009
edition
lx
right,
but
to
a
trandie.
You
know
that
there's
engines
there's
a
transmission
everything
there's.
A
Maybe
you
know
a
thousand
different
parts
and
they're
all
connected
together.
It's
the
same
thing
in
technology
and
in
technology.
Instead
of
having
like
a
transmission
and
an
engine,
we
have
things
like
databases
and
apis
and
messaging
cues,
and
things
like
that.
All
of
that
stuff
is
connected
together,
somehow
and
developers
figure
out
and
developers
and
architects
they
figure
out
which
components
to
use
and
also
how
they're
connected
so
here's
an
example
of
just
like
how
people
get
jobs
off
of
these
libraries.
A
These
are
literally,
you
know,
just
a
popularity
of
specific
libraries
for
making
buttons,
and
it's
just
four
different
frameworks
that
you
can
use
for
making
like
graphical
elements
for
websites.
A
So
this
is
my
terminal:
can
you
see
like
the
black
box
yep
all
right
great?
So,
let's
just
say
one
of
the
things
that
we
see
in
games.
All
the
time
is
simulating
chance
right.
So
it's
like
if
I'm
playing
holdem
online
or
something
like
that.
A
I
gotta
simulate
chance
and
I
could
write
out
all
of
that
code
itself
or
I
could
use
a
library
that
or
has
already
built
for
this
purpose-
and
that
saves
me
a
bunch
of
time,
so
the
library
for
building
out
chance
in
python
is
this
thing
called
random
and
as
what
you
can
do
over
here
is
you
can
generate
random
numbers.
So
I
just
generated
a
random
number.
I
just
generated
another
random
number.
Ultimately,
what
this
library
does?
It
saves
me
a
bunch
of
time.
A
I
don't
have
to
design
all
of
this
code
to
generate
random
numbers.
I
can
just
use
someone
else's
stuff
and
this
is
a
in
the
future
classes.
I'm
going
to
gloss
over
this
a
little
bit,
but
this
is
one
of
the
things
that
gitlab
does
and
it's
part
of
the
reason
why
we
make
money.
So
it's
important
to
understand
that
this
is
the
reason
why
developers
want
to
understand
about
libraries
and
dependencies
and
how
we're
packaged
managers
and
how
we
can
like
hold
containers
and
things
like
that,
all
right
source
control
management.
A
This
is
obviously
gitlab-
is
source
control
management.
A
Once
again,
I
just
really
want
to
reiterate
this
point
that
fundamentally,
every
single
application
that
we
use
is
just
a
running
set
of
text
files
when
you
download
a
new
installer
for
something
else.
All
you're
doing
is
downloading
a
bunch
of
text
files,
but
developers
need
a
tool
to
store
all
this
code.
So
that's
what
we
call
source
control
management,
there's
a
lot
of
different
tools
that
exist
and,
as
you
can
see
the
market
on
the
bottom
right
over
here,
the
market
is
consolidating
on
git
git
is
different
than
git
lab.
A
What
git
is
is
it's
free
and
open
source,
and
what
other
people
do
is
because
it's
free
and
open
source
they
take
it
and
then
they
add
on
features
to
it,
and
so
that
is
both.
What
gitlab
and
github
is
is
that
they
took
git
as
an
underlying
engine
and
then
they
added
on
additional
things,
and
then
we
repackage
it
and
sell
that.
So
that's
how
people
make
money
off
of
open
source
software
like
get.
A
Let's
talk
now
about
like
what
the
life
is
like
as
a
developer,
so
we
have
sales
quarters
here
right.
You
have
a
quota
at
the
end
and
in
the
beginning
you
may
be
doing
you
know
what
you're
doing
each
month
is
different
depending
on
where
you
are
in
that
quarter
and
it's
the
same
thing
for
engineers.
A
Another
thing
that
I
really
want
to
point
out
to
is
just
like
how
there's
goals
and
the
pressure
builds
until
the
quarter
is
over
and
then
it's
just
almost
like.
You
have
to
gather
your
breath
and
you
know,
breathe
a
sigh
of
relief,
it's
very
similar
to
how
engineers
actually
operate.
We
don't
have
a
quarterly
system.
We
have
this
thing
called
a
release
system
and
and
basically
what
a
release
is
is
a
big
project.
So
let's
actually
just
go
through
the
phases,
but
the
first
phase
is
that
it's
a
planning
phase
right.
A
So
you
have
all
of
these
product
managers.
They
scope
out
all
the
work.
They
say
hey
in
this
next
version,
like
you
know,
version
1.2.3
of
our
website.
We
want
a
b
and
c
implemented
x,
y
and
z,
and
the
reason
why
is
because
you
know,
like
apple
corp
and
this
other
company,
they
want
it,
and
we
think
that
they're
gonna
give
us
two
million
dollars.
A
If
we
build
this
thing
out,
so
their
product
managers
determine
what's
important
and
then
the
work
gets
assigned
to
engineers
after
so
that's
stage,
one
stage,
two
in
the
development
cycle
this
this
is
also
called
like
the
software
development
cycle
is
that
developers
they
work
on
implementing
this,
so
they
have
to
build
out
this
new
stuff.
A
After
this
happens,
then
people
basically
like
they
can
all
breathe
a
sigh
of
relief,
and
one
thing
that
I
want
to
like
point
to
with
this
is
that
the
amount
of
stress
in
among
engineering
teams
it
basically
just
ratchets
up
as
you
get
closer
and
closer
to
a
release
date,
because
the
vast
majority
of
engineering
projects
are
late
and
we'll
take
we'll
see
some
data
on
that.
Let's
talk
about
how
this
actually
works
from
a
gitlab
point
of
view,
so
you
have
these
guys
called
project
managers.
A
They
determine
the
work,
that's
involved
and
then
after
they've
created
the
work,
that's
involved,
they'll
create
these
things
called
issues
right
and
so
an
issue
is
an
individual
unit
of
work.
If
we
go
over
here
into
the
get
lab
issue
board,
then
there's
all
these
things
that
like
people
are
asking
for,
so
it
could
be
update.
This
chart
could
be
create
some
sort
of
new
thing
and
then
people
are
collaborating
on
the
best
way
to
do
this.
So
what
fundamentally,
fundamentally
engineers
get
assigned
issues?
Let
me
actually
just
go
back
to
here.
A
So,
as
you
can
see,
there's
this
person
called
garva.
Darva
is
responsible
for
implementing
this
one
issue.
This
is
how
they
get
credit,
and
this
is
how
they
get
paid
so
management.
Then
they
assign
the
issues,
they
say
sally.
You
get
three
chris
you
get
two
and
then
ultimately,
now
the
developers
they
start
working
on
these
issues
and
they
have
to
update
code
to
basically
solve
it.
Qa
they
test
it,
and
then
your
release
engineers
release
a
new
version
of
this
application.
A
Before
I
dive
into
this,
I
just
want
to
show
you
how
this
works
from
a
gitlab
perspective.
So
we've
talked
about
how
you
know
step
one
is
that
issues
are
created,
then
collaboration
happens
and
we
also
talked
about
how.
Fundamentally
all
software
is
is
just
a
running
set
of
text
files,
and
so
how
I
hand
in
my
work
as
an
engineer
or
a
developer,
is
that
I
modify
these
text
files.
That's
literally,
all
I'm
doing
I'm
getting
these
engineers
get
paid
like
x,
amount
of
money
to
fundamentally
just
change
text
files
right.
A
So
what
are
the
changes
that
this
guy's
making?
Well,
what
he's
doing
here
is
he's
taking
up
this
green
text
and
then
he's
adding
in
this
red
tag.
This
excuse
me
he's
taking
out
this
red
text
and
he's
adding
in
this
green
text
and
so
on
and
so
forth.
So
this
is
basically
what
developers
do
all
day
is
modify
text
files
just
like
how
like
an
editor,
is
looking
at
books
and
just
trying
to
like
you
know,
make
them
sound,
better
and
stuff
like
that.
A
These
developers
are
writing
a
novel
in
terms
of
software
and
as
opposed
to
just
like
a
story
and
a
narrative,
then
it's
all
functional
right.
So
it's
fundamentally
trying
to
create
something
in
this
particular
instance:
it's
creating
gitlab,
so
they
hand
in
all
of
their
code.
It's
fundamentally
just
these
changes
to
this
text
file,
and
so
then,
in
this
merge
request,
collaboration
happens
right,
so
people
go
back
and
forth
on
hey.
Is
this
the
best
way
to
do
it?
A
You
know
like
I,
I
don't
like
the
fact
that
it's
you
know
you
did
it
this
way.
You
should
do
it
this
other
way
and
then
people
go
back
and
forth.
So
this
is
how
collaboration
happens
in
terms
of
get
lab
and
ultimately,
once
the
code
is
submitted
and
those
text
files
are
changed,
then
those
original
issues
are
closed
and
now
the
developer
can
say
to
his
manager.
I'm
done
give
me
my
credit,
like
I'm
going
to
go
home
and
I
deserve
xyz
bonus.
A
So
that's
really
important
for
people
to
understand
from
an
engineering
point
of
view,
I'm
not
going
to
dive
super
into
this.
The
next
class
talks
about
how
this
works,
but
there's
this
thing
called
branching
and
commits.
If
you
take
210,
then
we'll
talk
about
what
that
means,
but
this
one
chart
is
super
super
super
important
to
understand.
A
So
we
talked
about
what
they.
What
engineers
do?
We
talked
about
some
of
the
emotions
behind
it,
and
this
really
just
reiterates
why
people
feel
the
way
that
they
do
so.
This
isn't
just
the
developers.
This
is
the
managers.
This
is
the
directors
right,
so
in
2017
there's
a
report
by
the
project
management
institute.
A
A
Outright
31
didn't
meet
what
they
set
up
to
do,
originally
43
were
over
budget
and
49
of
these
projects
were
laid,
and
so
when
we
talk
to
these
managers
and
these
directors,
and
even
if
we're
talking
to
architects,
it's
important
to
understand
that
they're
under
pressure
and
like
one
of
the
things
that
I
always
tell
people
is
that
almost
everyone
needs
get
lab,
because
this
isn't
some
sort
of
niche
problem.
Engineering
teams
being
late
on
their
projects
and
failing
in
some
regard
is
the
rule,
not
the
exception.
A
And
so,
when
you
go
into
these
conversations-
and
you
ask
how
you
know
like
what
sort
of
bottlenecks
do
you
have
in
your
organization,
they
can
tell
you
bottlenecks
and
there's
definitely
things
that
they're
concerned
about.
Why?
Because
if
the
average
engineering
manager
is
late,
forty,
nine
percent
of
the
time
that
means
that
a
huge
chunk
of
them
they're
having
those
conversations
with
their
direct
reports
and
their
direct
reports,
are
asking
them
about
why
their
projects
are
consistently
laid.
A
So
we
can
leverage
this
we
can
go
in.
Have
these
conversations
tell
me
about
your
team.
Tell
me
about
your
devops
processes.
What
are
some
of
your
bottlenecks?
You
know
I'd
love
to
be
able
to
help
explore.
You
know
how
to
speed
this
up.
For
you,
these
are
things
that
trigger
their
emotions,
because
no
one
wants
to
be
late
and
be
failing
on
their
projects
consistently
right.
A
So
it's
definitely
something
that
hits
home
all
right.
So
now
that
we
talked
about
the
emotions
behind
it,
I
explained
the.
Why?
Just
to
recap:
what's
this
all
about
this
is
about
digital
businesses
to
get
a
digital
business
to
run,
you
need
developers
developers
what
they
do.
Is
they
develop
the
best
software
businesses
care
about
having
developers
and
giving
them
tools
fundamentally
because
they
want
their
businesses
to
run.
When
we
talk
to
these
audiences,
most
of
them
are
behind
and
we
can
help
a
lot
of
these
people.
A
I'm
just
gonna
go
back
and
talk
a
little
bit
about
my
story,
as
an
engineer
is
that
I
worked
for
red
hat
and,
honestly
speaking,
our
stuff
was
some
of
the
best
in
industry
like
in
terms
of
our
development
practices
and
the
talent
that
we
hired.
It
was
really
really
really
good.
That
being
said,
we
had
extreme
on
my
team.
We
had
around
80
turnover
over
a
three
year
time
period,
just
because
of
how
much
emotions
and
churn
this
release
cycle
took
up.
So,
as
you
can
see,
I
was
a
test
engineer.
A
My
job
was
to
validate
software
for
functionality.
What
happened
all
the
time
is
that
developers
were
always
late,
but
the
project
deadline
would
never
get
pushed
back,
because
managers
don't
want
to
look
bad.
So
that
means
that
the
test
team
would
get
crunched
and
they
say,
as
opposed
to
you
having
a
month
to
validate
all
this
stuff
too
bad.
A
The
developers
were
two
weeks
late,
which
means
that
you
only
have
two
weeks
to
validate
all
this
stuff,
and
so
all
the
test
people
they'd,
have
to
work
late,
they're
all
stressed
out
the
test
manager
stressed
out-
and
this
happened-
probably
I'd
say,
two-thirds
of
the
time
in
my
engineering
group.
So
once
again
just
a
story
to
bring
things
home.
A
We
can
help
people
to
not
have
to
work
late
at
night
and
for
managers
to
be
able
to
systematically
deliver
better
products
for
their
end
stakeholders
and
their
customers
through
the
power
of
automation,
get
lab.
So
that's,
that's
you
know,
that's
that's
the
power
of
git
lab
all
right.
So
now
that
we
talked
about
applications
and
sort
of
talked
to
you
know
recapped
a
bit.
We
got
to
talk
about
how
these
applications
are
actually
running
right.
A
So
they
are
a
running
set
of
text
files,
but
they
need
to
run
somewhere
right
like
and
the
machines
that
these
text
files
run
in
are
these
things
called
servers,
and
so
this
thing's
called
a
server
rack.
Each
of
these
rectangular
things
is
a
server.
So
in
this
picture,
there's
five
different
racks
and
each
of
these
racks
you
can
see
around
20
different
servers
and
each
of
these
servers
cost
like
over
a
thousand
dollars
and
they're
just
stacked
up
on
top
of
each
other.
A
So
it's
important
to
understand
that
this
is
the
backbone
of
the
internet.
If
you
want
to
know
what
the
internet
looks
like
this
is
what
the
internet
looks
like
it's
just
machines
that
are
running.
You
know
like
sending
data
all
over
the
place
in
terms
of
what
netflix
looks
like
what
google
looks
like
what
you
want
to
do.
Is
they
have
these
buildings
called
data,
centers
they're,
all
over
the
entire
planet?
A
And
then,
ultimately,
once
you
went
into
these
data
centers,
you
would
see
these
running
machines.
That's
where
all
the
magic
happens.
That's
where
these
text
files
are
running.
Tell
me
about
this
picture.
So
this
is
a
new
data
center.
What
are
some
of
the
things
that
you
observe
about
this
picture?.
A
A
Yeah,
that's
very
good.
Tell
me
about
its
color
scheme,
what
what
color,
what
colors
are
in
this?
You
know
this
warehouse.
A
And
a
gray
yeah
exactly
and
let's
talk
about
why?
Right
so,
if
you're,
amazon.com
you're
on
this
great
growth
trajectory
and
if
you
have
some
sort
of
big
security
problem
where
people
break
into
the
building
and
steal
customer
data,
how
much
does
that
affect
your
digital
business?
Well,
it
affects
it
more
than
ten
percent
and
when
your
revenue
is
four
hundred
billion
dollars,
ten
percent
is
forty
billion
dollars.
So
every
single
detail
in
this
building
is
meticulously.
Crafted.
There's
no
windows
to
even
get
into
most
data
centers.
A
You
have
to
go
through
three
layers
of
security,
so
we're
talking
about.
Like
you
walk
into
these
chambers,
they
scan
your
eyes.
They
fingerprint
you
that
makes
you
go
through
like
you
know,
layer
one.
Then
they
show
your
badge
and
then
you
have
voice
recognition
and
then
they,
like
pat
you
down
to
make
sure
that,
like
you,
don't
have
any
embedded
devices
and
stuff
like
that
on
and
then
that's
tier
two
and
then
take
to
get
into
a
google
data
warehouse.
You
have
to
go
through
literally
three
layers
of
security.
A
Now
the
natural
question
is
that
is
that
necessary,
and
the
answer
is
that
if
once,
if
google
had
like
any
sort
of
vulnerability
in
terms
of
their
data
sovereignty
at
all,
how
much
money
does
that
impact
their
business?
Well,
it's
billions
of
dollars
right.
So
that's
why
they
put
so
much
effort
into
making
sure
that
these
buildings
are
as
secure
and
uninviting
as
possible.
They
don't
really
don't
they.
Don't
really
want
you
to
know
that
this
building
is
here
and
they
usually
like
have
them
in
obscure
locations.
A
We
got
to
talk
about
speed
here.
This
is
the
united
states.
I
know
that
we
have
several
people
from
emea,
but
the
same
thing
applies
in
europe,
but
you
have
data
centers
all
over
the
country
and
the
reason
why
is,
let's
just
say,
I'm
in
seattle
and
I'm
visiting
some
website-
that's
based
out
of
austin
texas.
A
A
couple
in
portland
a
couple
in
eugene
set
many
in
california
all
over
the
place
and
the
whole
idea
is.
I
want
the
fastest
possible
web
service.
My
web
service
is
the
fastest.
Then
I
have
a
competitive
advantage,
so
like
youtube
versus
like
netflix,
or
something
if
one's
really
slow,
then
the
other
person
is
going
to
get
all
the
you
know
the
customers
given
a
long
enough
period
of
time,
and
once
again
this
is
just
all
an
engineering
problem.
A
This
is
engineers
going
into
rooms
and
figuring
out
the
best
way
to
do
this
cloud
computing.
Who
wants
to
give
me
a
summary
of
cloud
computing.
A
All
right
I'll
dive
right
into
cloud
computing,
so
I
let's
just
talk
about
this
from
like.
Can
you
see
my
screen?
It
should
be
like
a
drawing
thing.
A
Yeah,
so
here's
the
story
of
cloud
computing,
so
a
traditional
e-business,
then
on
the
bottom's
time
on
the
y-axis,
is
number
of
servers
and
then
so,
let's
just
say
that
this
is
a
calendar,
so
january
february,
june
july
november
december.
Let's
just
say
that
there's
a
traditional,
you
know
e-commerce
place.
Let's
just
say
it's
amazon,
and
this
is
the
number
of
computers
that
they
need
to
keep
their
web
service
running.
So
in
january,
everyone's
cold,
so
people
are
on
their
site.
Buying
a
lot
of
stuff
spring
comes
around.
A
A
So
in
a
traditional
like
the
first
paradigm
that
we
had
for
computing,
is
you
have
some
sort
of
website
that
means
go?
Buy
some
servers
install
your
web
application
on
these
servers
that
are
now
running
your
website
and
that's
how
you
basically
do
things
so
everyone
owned
their
own
their
own
hardware,
but
the
big
problem
with
this
is
that
over
here,
let's
just
say
that
this
is
amazon.
A
If
we,
if
our
analysts
expect
this
amount
of
web
traffic
in
the
november
and
december
time
frame,
then
we
got
to
build
ourselves
some
buffer
in
case
these
guys
are
wrong.
So
we're
going
to
get
a
little
bit
more
than
that,
and
the
problem
with
this
is
that
for
the
vast
majority
of
year,
all
of
this
capacity
is
just
computers
that
are
sitting
around
not
doing
anything
and
literally
like
they're,
not
making
me
any
money,
it's
just
like
a
sunk
cost
and
I
don't
really
need
them
right.
A
So
what
the
cloud
is
is,
as
opposed
to
me
owning
my
own
hardware.
I
can
now
rent
someone
else's
hardware
and
pay
them
on
an
hourly
basis,
and
so
you
know
with
the
advent
of
cloud
computing,
what
we
could
do
is
we
could
say.
I
only
want
this
amount
of
capacity
and
I'm
going
to
rent
out
this
capacity
and
this
capacity
from
the
cloud
to
supplement
my
server
fleet
during
periods
of
time
of
peak
utilization,
and
so
that
is
what
the
public
cloud
is
for,
so
just
to
recap:
traditionally,
people
own
their
own
stuff.
A
A
So
this
is
a
huge
deal.
Git
lab
this
year
is
going
to
make
probably
around
like
150
million
dollars.
There
was
recently
one
deal
for
the
us
government
that
was
10
billion
dollars
for
cloud
computing
and
microsoft
won
that
deal
so
we're
talking
about
a
huge
market.
That's
expanding
over
here
in
the
right.
Here's
the
market
share
by
cloud
provider.
You
can
see
that
amazon's
a
number
one
microsoft's
a
number
two
google's
a
number
three.
The
reason
why
amazon
is
number
one
is
because
they
had
first
movers
advantage.
A
They
were
the
first
people
to
do
it
and
to
do
it
well
and
because
of
that
they
their
service
offering
is
more
comprehensive
than
a
lot
of
other
people.
What
we
also
see
is
that
there's
a
huge
consolidation
in
the
market,
so
it's
kind
of
like
economies
of
scale.
If
I
have
a
lot
of
this
stuff,
then
I
can
do
it
much
more
cheaply
than
other
people,
which
means
I
can
squeeze
out
the
smaller
guys.
A
Ultimately,
what
a
lot
of
people
are
doing
is
their
auto
scaling
applications.
What
that
means
is
that
I'm
just
gonna
go
scale
up
and
scale
down
the
number
of
servers
that
I
have
depending
on
my
utilization
through
the
public
cloud,
and
that
was
a
lot
of
terms.
Basically,
the
whole
idea
is,
as
opposed
to
owning
my
own
servers,
I'm
just
going
to
continue
rent
them
and
then,
when
I
rent
them,
then
you
know
I'm
only
paying
for
what
I
use
and
so
that's
becoming
more
common.
Now.
A
Too,
all
right,
so
we
got
to
talk
about
virtualization
containers
and
kubernetes,
so
it's
going
to
get
a
little
bit
more
technical
stay
with
me
here,
because
this
is
going
to
be
something
that's
important
to
understand
all
right.
So
there's
this
thing
called
virtualization
and
what
virtualization
allows
you
to
do
is
to
get
multiple
machines
inside
of
one
physical
machine,
so
I
could
have
one
server
that
has
like
five
different
virtual
servers
running
inside
of
it.
Let
me
show
you
an
example
of
this.
A
Let
me
know
when
you
can
see
my
desktop
again.
It
should
be
the
same
one
with
the
black
box
over
here
in
it
all
right.
So
this
is
my
mac,
but
over
here
you
can
see
that
I
have
this
thing
called
virtualbox
running
and
even
though
I'm
running
mac
os,
I
have
a
linux
virtual
machine
running
on
my
my
my
mac.
So
over
here
is
the
login
screen.
I'm
not
going
to
go
into
it
because
sometimes
my
computer
gets
upset
with
me,
but,
like
this
is
a
linux
virtual
machine.
A
That's
running
on
my
mac,
I
could
have
on
my
mac
five
virtual
machines
that
are
running.
At
the
same
time,
I
could
have
one
being
windows,
one
being
linux,
three
of
them
being
mac.
I
can
really
do
whatever
I
want
with
them,
but
this
was
a
really
big
deal
when
people
invented
virtualization
and
the
reason.
Why
is
because.
A
Okay,
so
the
reason
why
is
because,
let's
just
say,
I'm
a
small
company
and
in
general,
like
you,
only
want
to
install
one
application
on
any
server?
That's
just
like
an
engineering
best
practice
stuff
gets
really
confusing
if
you
install
a
lot
of
applications
on
the
same
server,
but
the
problem
is
that
each
one
of
these
servers
cost
me,
like
you,
know
four
thousand
dollars
or
something,
and
what,
if
the
application
that
I
want
running
on,
it's
really
really
small
only
uses
two
percent
of
the
server.
A
Well,
then,
having
the
ability
to
split
the
server
into
10
servers
using
virtualization
is
a
really
great
use
case
for
that.
So
that
was
the
original
reason
why
they
created
virtualization
is
so
that
they
can
compartmentalize
these
servers
and
get
more
utilization
out
of
them
once
again.
The
rationale
is
that,
like
in
general,
how
these
applications
work
is
one
application
per
server.
If
you
have
multiple
applications
on
a
server,
then
generally
really
bad
things
happen
and
virtualization
was
a
way
to
solve
this
problem.
A
So
nowadays,
some
one
thing
that's
important
to
understand
is
that
basically,
all
applications
are
running
as
virtual
machines.
Amazon.Com
youtube
netflix
they're
running
as
virtual
machines,
somewhere,
probably
in
the
public
cloud,
but
you
don't
have
to
use
the
public
cloud.
If
you
want
to
have
your
own
servers,
then
you're,
traditionally
using
something
called
vmware
or
hyper-v.
Vmware
is
owned
by
dell
and
hyper-v
is
owned
by
microsoft.
A
All
right!
So
now
now,
let's
take
things
a
little
bit
step
further.
So
there's
these
things,
containers
and
kubernetes.
This
is
really
really
important
for
us
to
understand,
because
I'd
say
almost
like
15,
maybe
10
to
15
percent
of
our
fundamental
value
proposition
has
to
do
with
containers
and
kubernetes.
A
A
Then
people
came
up
with
virtual
machines
that
allowed
me
better
granularity
and
more
flexibility
and
what
we've
seen
the
last
five
years
is
basically
version
2.0
of
containers
and
a
virtualization,
and
so
the
way
to
think
about
containers
is
it's
basically
better
virtualization.
It's
way
faster.
It's
way
more
efficient,
every
business
wants
this
because
it
can
save
them
money.
A
If
you're
building
a
website
using
containers,
then
it's
going
to
have
competitive
advantages
in
terms
of
speed
versus
other
types
of
architecture,
so
the
entire
market
is
going
from
your
regular
virtual
machines,
two
containers
around
20
percent
of
the
market
right
now.
This
is
kind
of
like
a
wild
guess,
maybe
15
to
20
percent
of
all.
Applications
right
now
are
running
on
containers
in
the
next
five
to
10
years.
A
That
will
go
to
about
a
hundred
percent
unless
there
are
specific
reasons
why
something
it
can't
be
a
container
but
get
lab
is
in
a
really
great
position,
though,
because
we
were
built
for
containers,
and
we
already
are
where
the
market
is
going.
That
is
really
important
to
understand.
Part
of
our
value
prop
is
that
we
are.
We
have
great
integrations
with
docker
and
kubernetes
the
market's
going
here,
we're
perfectly
positioned
to
snatch
up
customers
as
they
have
this
technical
journey
all
right
from
business
perspective.
Why
do
people
care
it's
way
faster
way,
more
efficient?
A
Fundamentally,
what
I'm
doing
is
I'm
if
I'm
a
business,
I'm
spending
a
ton
of
money
on
these
servers
right.
I
can
get
more
out
of
my
servers
if
I
use
containers
than
if
I
use
traditional
virtual
machines,
so
basically
just
like
save
a
ton
of
money
in
terms
of
cost
all
right,
so
we
got
to
talk
about
some
of
the
tools
that
run
these
things.
A
If
I
want
one
machine
so
like
going
back
to
this
this
slide,
this
rectangular
thing
over
here
is
one
server.
If
I
want
containers
to
run
on
one
machine,
then
that's
what
docker
is
for.
If
I
want
50
machines
all
running
containers,
then
I
need
something
that
sort
of
like
oversees
that
entire
process,
because
now
it's
more
complicated
right,
and
that
is
what
kubernetes
is
so
just
a
rephrase,
because
I
know
there's
a
lot
of
terminology.
A
Docker
manages
containers
on
one
machine.
If
I
want
50
100
1
000
machines
running
containers,
then
I
need
an
additional
management
layer.
That's
going
to
make
sure
that
things
make
sense
in
my
environment
and
that's
what
kubernetes
is.
Gitlab
works
really
really
really
well
for
both
of
these
things,
and
so
that's
really
important
to
know
gke.
What
we
refer
to
git
lab
actually
runs
on
gke,
but
this
is
google's
cloud
kubernetes
offering.
So
it's
basically,
we
are
paying
google
money
to
use
their
kubernetes
cloud
offering.
A
Right
cool,
so
here
is
so
here's
docker
right
now.
You
can
see
nothing's
running
in
docker,
but
let's,
let's
actually
do
something
right.
So.
A
Just
hit
that
real,
quick,
you
know
what
did
I
do?
I
did
this
thing
called
a
docker
start.
A
A
This
is
really
important
to
understand
so,
like
I
know
that
jesse
you're
in
europe,
but
for
miami
crowd,
do
you
all
use
this
restaurant
review
website
called
yelp?
Have
you
ever
heard
of
yelp
before.
D
A
A
Okay
cool,
so
this
is
like
a
restaurant
review
website
and
you
know
so.
This
is
a
really
popular
website
in
the
united
states,
but,
as
you
can
see
over
here,
if
I
scroll
down
what
we
actually
find
is
that
there's
google
maps
that's
somehow
embedded
in
yelp,
and
so
you
know
for
the
untrained
eye
you
just
might
think
like
who
cares?
But
you
know
like
one:
are
they
just
like?
Is
this
copyright
infringement?
Did
they
steal?
A
Google
maps
is
like
data
or
like
how
does
this
even
work
from
an
engineering
perspective
and
how
this
actually
works
is
that
there
are
apis
talking
to
each
other
behind
the
scenes,
and
google
has
actually
allowed
yelp
access
this
data.
If
we
scroll
scroll
over
here,
we
can
see
how
much
money
they
get
right.
So
the
pricing
for
google
maps
for
a
static
map
every
thousand
times
this
is
displayed.
A
Yelp
has
to
give
google
maps
two
dollars
if
they
want
the
more
dynamic
interactive
maps.
This
costs
seven
dollars
per
1000
requests,
and
so
this
is
the
commercialization
of
data
that
happens
today
in
technology.
You
have
companies
like
google,
they
invest
millions
like
hundreds
of
millions
of
dollars
to
get
your
data
and
the
reason
why
is
so
that
they
can
sell
it
to
marketers?
A
They
can
sell
it
to
other
people
around
the
world,
other
web
services
and
that's
how
their
business
works
and
how
all
this
stuff
works
behind
the
scenes
is
through
these
things
called
apis,
and
so
let
me
just
pull
up
so
this
is
the
handbook
site
over
here.
Right,
www.getlab.com
and
one
of
the
things
to
point
out
is
that,
even
though
this
is
gitlab,
we
have
an
equivalent
version
of
this,
which
is
actually
the
api
endpoint
that
corresponds
to
this
site.
A
And
so
let
me
just
show
you
that
this
blob
of
text
is
actually
the
exact
same
information
as
this.
So
over
here,
there's
id
7764
idea,
7764
right
and
then
the
description
is
sourceforabout.getlab.com.
This
repo
project
is
for
the
public
facing
marketing
website
for
gitlab
blah
blah
blah,
and
then
that's
what
it
says
here:
description
source
for
about
gitlab.com
this
repo
project
is
the
public-facing
marketing
website
for
gitlab,
so
flies
this
important.
A
This
is
important
because,
ultimately,
if
you're
an
e-business,
then
having
the
ability
for
other
people
to
integrate
with,
you
is
part
of
how
you
increase
your
visibility
on
the
internet.
Every
time,
there's
yelp,
there's
a
google
maps
embedded
in
another
website,
then
one
you
get
money
directly
right,
but
two.
It's
increasing
visibility
of
your
web
service,
more
people
know
about
google
maps
and
the
fun
underlying
machinery
that
allows
all
this
stuff
to
work
is
apis
and
once
again,
apis
is
just
an
alternative
version
of
your
website.
A
So
as
opposed
to
www.gitlab.com,
we
have
you,
know
api,
slash,
v4
projects,
slash
7764,
says
the
exact
same
information
as
this,
and
this
is
what
allows
people
to
integrate
with
different
web
services.
Whenever
we
talk
about
servicenow
integration
or
jenkins
integration,
our
jira
integration,
how
this
works
is
that
we
have
an
api.
If
a
customer
ever
asks
you
can
I
integrate
x,
y
and
z
with
git
lab?
The
answer
is
yes,
because
we
have
an
api.
Some
of
the
integrations
are
better
than
others,
but
it
always
pretty
much
like
100
of
the
time.
A
All
right
so,
let's
bring
it
all
home.
To
recap.
A
Yeah,
so
it's
a
technology
race
and
the
problem
with
the
race
is
that
it's
just
getting
faster
and
faster.
I
think
that,
like
20
years
ago,
a
politician
could
reasonably
have
good
policy
decisions
in
terms
of
managing
how
people
talk
on
the
internet
and
like
things
like
the
dark
web
and
stuff
like
that.
But
at
this
point
in
time,
technology
is
moving
so
quickly
there
are
legal
systems
lagging
behind.
Businesses
are
lagging
behind,
so
it's
a
great
place
for
innovation.
A
If
you
can
take
advantage
of
that
and
build
a
business
out
of
it,
you
can
make
tons
and
tons
of
money,
but
the
big
problem
with
it
is
that
it's
changing
so
quickly
that
it's
somewhat
unmanageable
at
this
point.
That's
just
the
reality
of
the
world
that
we're
in
from
an
engineering
point
of
view,
bringing
this
back
to
sales
and
the
conversations
that
we're
having
with
our
customers.
A
I
kind
of
want
to
just
like
also
give
a
story.
So
I
have
a
friend
who
just
finished
graduate
school
two
years
in
terms
of
a
nurse
practitioner
program,
and
you
know
so
she
would
spend
300
hours
doing
the
digestive
system.
Then
400
hours
studying
the
neural
system,
but
when
she's
done
with
that
two-year
program,
she
doesn't
have
to.
She
needs
to
learn
new
trends
and
stuff
like
that.
But
fundamentally,
all
of
our
education
is
done
right.
A
So
that's
a
ton
of
pressure
on
the
engineers,
the
managers,
the
directors,
because
they
want
to
have
a
competitive
web
service
because
they
want
their
business
to
be
successful
and
the
fact
that
all
of
this
is
changing
so
quickly
just
means
that
they
feel
behind
all
the
time
right.
So
there's
a
struggle
to
keep
up
with
the
latest
trends
they're
constantly
looking
at
their
competitors
in
terms
of
the
features
that
they're
building
out
in
terms
of
user
experience.
A
If
you've
amazon's
done
all
of
these
studies
on
psychology
and
sociology
and
anthropology,
and
all
this
other
stuff
but
tastes-
and
you
know
what
counts
as
like
a
fun
interactive
experience.
Web
experience
is
going
to
be
completely
different
in
six
months
right
and
so
engineers
now
have
to
go.
Make
out.
That
latest
version
of
that
website
terms
of
speed
and
security
security
is
the
one
that
I
really
want
to
harp
on
your
website.
A
If
it's
completely
a
hundred
percent
locked
down
today
is
going
to
be
out
of
date
in
a
week
and
if
you're,
google
or
amazon,
and
if
you
just
have
one
major
security
vulnerability,
then
how
that
that's
going
to
be
a
huge
disaster
for
your
business,
so
most
technology
companies
feel
behind,
and
you
can
ask
them
about
this.
You
can
be
like,
and
sometimes
they
may
not
be
aware,
but
I
think
that
most
people-
this
is
a
very
emotional
thing
for
them.
A
A
Get
lab
allows
for
organizational
transformation
so
that
people
can
get
ahead
and
that's
a
breath
of
fresh
air
for
a
lot
of
the
people
that
we
talk
to.
I
think
that
it
takes
sometimes
you
know
it
takes
some
education
for
people
to
understand
the
value
of
gitlab,
but
once
they
get
it,
then
they
understand
that
this
could
actually
be
one
of
their
linchpin
sources
of
organizational
success
so
that
they
can
actually
not
be
late
on
these
projects
time
and
in
china,
and
things
like
that.
How
do
we
do
that?
A
This
is
what
we
call
command
of
the
message:
become
more
efficient,
deliver
better
products
faster
and
reduce
security
risk.
We
don't
go
into
that
in
this
session,
but
if
you
take
tanuki
tech,
210
and
211
we'll
talk
about
exactly
how
we
deliver
this
for
customers,
so
yeah
that's
the
session
for
today
can
I
I
know
that
that
was
a
ton
of
information.
Can
I
clear
up
anything
for
anyone.
A
I
know
that
we
sort
of
like
talked
about
a
lot
of
different
technical
things
really
quickly,
but
I'm
interested
in
hearing
what
you,
what
you
all
think
and
if
I
can
clear
anything
up
for
anyone.
A
These
slides
will
be
available,
and
I
will
also
share
a
google
doc
with
you.
This
is
how
y'all
get
credit
for
this
course
is
by
filling
out
the
google
doc
there's
some
questions
at
the
end.
A
It
stands
for
actually
don't
know.
C
A
C
A
Cool
awesome
yeah.
So
let
me
talk
about
what
I
owe
y'all
from
here
on
out.
So
thanks
for
attending
the
session
today,
I
really
at
the
end
of
this
week
there
will
be
a
survey
that
goes
out
feel
free
to.
Let
me
know
if
there's
anything
that
I
can
improve
on,
but
filling
out,
I'm
not
at
the
end
of
this
session.
There's
two
things
that
are
gonna
happen.
One
is
I'll
share
the
slides
with
y'all
and
two
is.
A
I
will
share
a
google
doc
with
y'all
and
filling
out
this
google
doc
is
going
to
be
how
you'll
get
credit
for
this
course.
I
don't
do
this
so
that,
like
I
give
you
like
busy
work,
but
this
is
really
to
help.
You
all
understand
like
what
each
of
these
things
mean,
because
I
just
really
want
to
see
if
I
can
help
in
terms
of
like
our
customer
conversations.
So
every
one
of
these
questions
here
is
something
that
a
customer
could
ask
you
it's
not
busy
work.
A
A
Awesome
well,
thank
you
all
for
all
his
time
today,
I'm
looking
forward
to
seeing
everyone
in
a
future
session.