►
From YouTube: TT200: Introduction to Development
Description
YouTube description:
This is a Tanuki Tech session on 9/14/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
awesome
all
right,
so
I'm
really
excited
about
this
session.
Thank
you
all
for
joining,
and
what
what's
the
goal
of
this
session
right?
Everyone's
time
is
valuable
and
I'm
excited
about
this
session,
because
the
goal
is
to
have
better
conversations
with
developers
and
specifically
technical
people.
I
know
that
back
when
I
was
on
sales,
almost
all
of
the
presentations
that
I
had
that
were
technical.
It
was
just
sort
of
like
at
the
end
of
it.
A
A
The
most
important
thing
is
learning
to
speak
their
language
with
confidence.
So
it's
just
sort
of
like
if
I
got
someone
and
I'm
in
like
a
hardware
store-
and
I
start
talking
about
like
efficiency
and
like
value
and
stuff-
then
that's
not
going
to
resonate
as
much
as
like
if
someone's
super
technical
and
I'm
like.
Oh
man,
did
you
see
like
this
new
thing
that
came
out
it's
you
know
three
millimeters
instead
of
two
and
that
allows
you
to
get
like
more
whatever
out
of
like
your
pipes
or
something
like
that.
A
So
if
you
can
learn
to
speak
their
language,
then
I
think
that
that's
the
key
to
having
fruitful
developer
conversations
we'll
talk
about.
Why
that's
the
case?
Other
things
I
will
talk
about
is
life
as
a
developer.
I
was
one
for
half
a
decade,
so
I'll
share
some
more
stories.
There
are
many
and
I'll
talk
about
their
tools
and
workflow.
So
before
I
jump
in,
I
just
want
to
say
feel
free
to
interrupt
me
feel
free
to
ask
me.
A
A
All
right
so
before
we
talk
about
developers,
it's
really
important
to
understand
why
developers
exist
in
the
first
place
and
ultimately
like.
If
you
just
think
about
get
lab,
we
have
sales
and
marketing
their
entire
job
is
to
sell
stuff
right
and
bring
revenue
for
the
business
we
are
in
revenue
marketing.
A
What
developers
do
is
they
create
the
thing
that
companies
sell?
That's,
ultimately
what
they're
doing
and
sometimes
developers
don't
know
that,
but
that's
their
goal
right,
that's
their
functional
organization.
So
what
do
they
do?
For
the
most
part
they
create
applications,
not
all
of
them
create
applications,
but
the
most
of
them
do
and
the
reason
my
businesses
care
about
their
applications
is
because
applications
are
either
revenue
driving
themselves
or
some
sort
of
background
tool
that
ends
up
being
revenue
driving.
A
So
something
like
their
backend
system
like
salesforce
many
different
types
of
applications,
things
like
netflix
web
applications.
Facebook
amazon,
is
a
web
application.
You
have
applications
for
your
phone,
you
have
tools
and
then
you
have
games
and
things
like
that,
and
so
one
of
the
things
I
always
say
is
like
imagine.
A
If
you
and
your
family,
you
decide
to
pivot
your
career
and
you
want
to
buy
like
a
store,
and
so
you
take
out
a
business
loan,
300
000,
you're
mentally
and
like
invested
into
this
store
for
the
next,
like
5
10,
maybe
20
years
of
your
life
right.
So
you
think
about
everything
and
even
the
small
details
they
matter.
So
in
terms
of
like
making
my
business
successful
from
a
traditional,
brick
and
mortar
store,
then
I
think
about
small
things
like
where's
the
store
located
out
of.
A
C
A
C
A
Yeah
exactly
and
like
especially
moms
with
children
right,
so
you
can
just
imagine
like
a
mom
with
two
kids
walking
by
and
the
kids
are
like
hey,
I
want
to
go
inside
here.
There's
stuffed
animals,
there's
a
colorful
and
then
all
of
a
sudden
you
get
a
sale
right.
So
they
think
about
all
this
stuff
in
the
same
way
for
any
sort
of
digital
business
like
amazon,
amazon,
hires.
A
All
of
these
phd
psychologists,
sociologists,
anthropologists
and
they
study
human
behavior.
And
how
do
you
make
their
experience
like
as
addicting
and
interactive
as
possible?
And
if
you
think
about
it,
if
my
website
is
a
more
fun
experience
than
yours,
then
over
a
three
year
time
horizon
I'm
going
to
have
significant
advantages
over
other
people.
So
literally
what
amazon
does
is
they
do
sociological
experiments,
I'm
like
all
right.
So
what
are
the
different
types
of
people
in
the
united
states?
A
Well,
you
have
different
groups
right
and
they'll
figure
out
how
they
can
appeal
to
each
group
and
that's
a
little
bit
different
for
each
segment
and
especially
as
you
think
about
like
as
your
ebr
business
scales
out
internationally,
then
how
you
make
something
interactive
and
fun
for
someone
in
europe
is
going
to
be
different
than
someone
in
the
united
states.
So
that's
the
reason
why
they
invest
so
much
into
the
these
psychological
studies
and
things
like
that.
A
So
how
do
you
stand
out
in
like
a
digital
business?
There's
four
main
ways?
One
is
that
if
my
application
or
a
business,
our
website
does
something
that
yours
doesn't
so
imagine
like
lyft
and
uber
right,
if
one
like
has
some
new
option.
That,
like
is
going
to
reduce
my
cost
20,
because
I
can
like
share
a
car
with
like
a
bunch
of
other
people
or
something
like
that,
then,
and
the
other
one
doesn't
offer
that
option.
Then
I
could
steal
their
market
share
right
in
terms
of
speed.
A
This
is
something
that
matters
a
lot,
something
that
we
don't
think
about,
but
it
really
is
an
arms
race
and
a
lot
of
times
in
digital
businesses.
It's
a
winner's,
take
all
market.
It's
not
like
you
know,
new
york
city.
You
could
have
like
40
50
different
hardware
stores,
because
the
population's
so
large,
usually
what
happens
is
one
digital
business
wins
and
then
they
get
the
entire
market.
A
All
right
so
features
right
so
15
years
ago,
amazon
offers
books,
they're
moderately
successful
10
years
ago.
You
can
get
a
lot
of
things
on
there.
You
can
get
like
household
items,
you
can
get
cleaning
supplies
and
just
think
about
what
they've
done
in
the
last
three
years
right
so
in
terms
of
handcraft
goods,
they
own
etsy,
you
get
groceries
with
whole
foods
and
they're,
making
a
ton
of
money
off
of
this
with
coronavirus
in
terms
of
entertainment
they
own.
A
They
have
amazon,
prime
video
right
and
there's
now
television
series
that
are
only
exclusive
to
prime
video.
You
can
get
contractors
and
electricians
and
stuff
through
amazon
and
they
own
the
most
popular
gaming
platform
in
the
world
right
now
in
twitch,
and
so
amazon
has
got,
has
increased
their
revenue
for
500
in
the
last
half
a
decade
and
part
of
how
they've
been
able
to
do
this
is
by
increasing
their
service
offering,
and
all
of
this
takes
engineers
to
build
stuff
out.
A
This
is
why
they
have
so
many
engineers
and
some
of
the
best
engineers
in
the
world
in
terms
of
speed.
This
is
something
that
a
lot
of
people
don't
think
about,
but
I'm
just
going
to
let
the
data
do
the
talking
right.
So
pinterest
is
some
web
platform.
You
can
put
images
on
here,
but
they
found
that
they
increased
signups,
which
you
can
just
think
about
like
acquiring
new
customers
right.
A
They
increase
signups
by
15
after
they
reduce
their
wait
times
by
40
percent.
So
engineering
investment
reduced
wait
times
now
they
have
15
more
pipeline
growth
year
after
year.
So
how
much
does
that
matter?
Over
a
three
year
time
period,
well
that
makes
50
difference
right
so
15
times
three.
So
it's
a
big
difference:
british
broadcasting
corporation
just
a
new
site.
They
make
all
their
revenue
pretty
much
off
of
the
ads
that
you
see
when
you
go
to
their
site,
they
found
that
they
lost
10
of
users
for
every
additional.
A
A
Google
found
that
fifty
three
percent
of
mobile
will
excuse
me
mobile
website
visits
where
abandon
if
a
site
took
longer
than
three
seconds
to
load
so
over
here
on
the
bottom,
just
bringing
things
home
right.
So
these
are
the
annual
financials
for
amazon.com
2015.
They
had
107
billion
dollars
in
revenue,
bring
that
all
the
way
up
to
2020
they're
north
of
300,
and
so
what
I'm
really
trying
to
point
out
here
is
like
there's
a
lot
of
my
new
things
that
we
can
do
and
increasing
signups
by
15,
not
losing
10
percent
of
users.
A
But
what
I'm
trying
to
point
out
is
that
if
I
make
some
of
these
engineering
investments,
then
I
can
tweak
my
business
five.
Ten
percent
and
five
ten
percent
for
amazon
is
thirty
billion
dollars
for
ten
percent
right.
So
that's
the
reason
why
all
of
these
companies
have
so
many
engineers
performance
engineers
developers,
testers
qa
things
like
that
is
because,
ultimately,
this
helps
them
get
competitive
advantage
for
their
digital
business.
A
All
right
so
now
that
we
talked
about
the,
why
of
what
developers
are
here
to
do
we're
going
to
start
talking
a
little
bit
about
some
of
their
tools
and
workflows,
I'm
going
to
try
to
demystify
some
of
this
stuff.
If
there's
anything
that
I
can
help
to
clarify.
Just
let
me
know
and
feel
free
to
ask
me
whatever
questions
you
want.
So,
let's
just
talk
about
programming
languages,
all
of
your
applications
like
netflix
amazon,
youtube,
they're,
just
literally
written
in
programming
languages,
and
so
let
me
just
share
my
screen.
A
Real
quick
over
here
is
get
lab.
Get
lab.
Fundamentally,
is
a
bunch
of
text
files
and
every
single
application.
You
will
ever
use
like
google
documents
whatever,
if
you
were
to
take
a
look
at
what
these
actually
are
at
a
fundamental
level.
Is
that
they're
just
running
text
files,
and
so
this
is
get
lab
code?
If
you
ran
all
of
these
text
files,
which
is
just
machine
instructions,
then
gitlab
runs
and
all
of
like
this
text
over
here
it
is
just
a
programming
language.
A
So,
let's
just
start
talking
about
this.
Real
quick
applications
are
written
in
programming
languages,
programming,
languages,
fundamentally,
what
they
do
is
they
just
tell
machines
to
do
things
so
it
could
be.
You
know,
turn
on
zoom.
It
could
be
like
you
know,
shoot
missiles
at
like
some
test
site
or
something
like
that
and
there's
a
lot
of
different
programming
languages.
A
Fundamentally,
the
way
to
think
about
this
is
that,
like
in
human
interaction,
there's
a
lot
of
different
languages
in
general,
like
french,
spanish,
italian,
whatever
and
fundamentally
you
just
use
it
to
communicate
and
the
difference
with
the
programming
language
is
that
fundamentally
they're
doing
the
exact
same
thing,
which
is
to
just
tell
machines
to
do
stuff,
but
their
syntax
is
different,
just
like.
If
I
wanted
to
communicate,
hey
I'm
going
home.
I'd
say
that
differently
in
like
spanish
and
english,
so
it's
just
different
rules
for
telling
machines
to
do
certain
things.
A
A
So
that's
something
to
know
about
programming
languages
over
here
you
can
see
the
popularity
of
programming
languages
and
as
a
developer.
I
really
care
about
this
because
it
takes
around
five
to
ten
years
for
me
to
really
get
great
at
a
programming
language,
and
so,
if
I'm
investing
all
of
this
time
into
a
language,
that's
declining
in
use
that
decreases
my
market
value
right,
so
it
just
literally
makes
no
sense
for
me
to
be
programming
in
something
if
that
language
is
going
away.
A
Programmers
are
really
cognizant
of
you
know
these
trends,
because
this
is
their
ability
to
ultimately
make
bread
right
over
here
is
python
and
we
can
sort
of
figure
out
somewhat
of
what
this
is
doing
right.
So
this
is
some
sort
of
command
line
thing
you
can
do
like
dash
l,
which
is
an
option
dash
dash
graph,
which
is
an
option
so
on
and
so
forth.
Over
here
is
ruby
code.
This
is
actually
git
lab
and
so
over
here
this
is
something
called
a
runner.
A
A
A
A
All
right
so
that
language
that
I
just
shown
was
bash,
I
could
have
done
the
exact
same
thing
in
python
and
ruby
and
anything
else,
because
fundamentally
they're
doing
the
exact
same
thing,
it's
just
different
syntax,
all
engineers
are
doing
all
day
is
they're
writing
little
scripts
that
do
stuff.
So
it's
like.
I
wrote
that
script
that
created
folders
that
took
me
like
30
seconds
to
make
when
I
was
a
developer.
I
was
writing
scripts
that
made
websites
and
things
like
that
and
fundamentally
the
text
files
just
describe
like
how
a
website
should
run.
A
Fundamentally
all
developers
do
is
make
these
text
files
and
that's
how
they
get
paid,
which
is
kind
of
interesting
to
think
about
all
right.
So
let's
talk
a
little
bit
more
about
like
the
specific
things
that
they
do.
This
isn't
just
learning
technical
stuff
for
technical
stuff's
sake.
All
of
these
things
have
to
do
with
either
something
that
gitlab
does
or
something
that
developers
do
that
matters
for
them
and
that
gitlab
interacts
with
as
part
of
like
our
sales
motions,
so
libraries
and
dependencies
this
matters,
because
gitlab
manages
your
libraries
and
dependencies.
A
So,
let's
talk
about
what
they
are
right,
they're,
basically,
the
same
thing,
that's
kind
of
like
a
on
that's
a
little
bit
unfair,
but
for
all
intensive
purposes
they
are
the
same
thing
and
the
whole
idea
with
this
is
like
imagine
yourself,
25
years
ago,
when
computer
science
was
new,
so
people
are
making
websites
for
the
first
time
and
everything's
new
and
everything's
novel,
which
is
really
an
exciting
period
of
time.
So
it's
like,
if
you
think,
about
the
dot-com
bubble.
A
Part
of
the
reason
why
it
happened
is
because
there's
just
so
much
excitement
and
novelty
in
everything
right,
but
fast
forward
to
2020
and
most
stuff
has,
I
want
to
say
most
things
but,
like
a
huge
number
of
things
have
already
been
done
like
thousands
of
times,
so
it's
like,
if
I'm
making
some
button
for
a
website,
then
there's
30
000
other
businesses
around
the
world
that
are
making
very
similar
buttons
right.
So
it
doesn't
make
any
sense
for
me
to
reproduce
everything.
What
a
library
independency
is.
A
Is
it's
like
it's
a
bunch
of
different
code
snippets
that
you
can
use
so
that
you
don't
have
to
reinvent
the
wheel
the
entire
time,
so
you
have
libraries
that
create
buttons.
You
have
libraries
that
generate
random
numbers.
You
have
libraries
that
help
you
to
do
statistical
things
and
the
whole
idea
is
as
opposed
to
just
doing
everything
over
and
over
again,
then
you
can
use
a
library
instead
and
save
yourself
some
time
so
the
vast
majority
of
programmers
all
they
do,
is
they
specialize
in
a
few
popular
libraries.
A
So
it's
important
to
understand
how
libraries
are
used
just
like
in
a
car.
You
have
a
lot
of
different
components
right,
so
you
have
wheels
your
transmission,
your
engine,
you
have
like
the
frame
you
have
like
axles
and
things
like
that
in
software
and
in
applications
you
have
this
thing
called
a
stack
and
what
a
stack
is
is
that
it's
all
of
your
different
technical
components,
how
they
fit
together
and
what
components
actually
exist,
and
so
I'll
give
you
an
example
of
this
like
in
a
website.
A
A
If,
if
I
can
I'll
try
to
like
talk
about
like
the
new
developments
and
some
of
this
stuff
and
just
trying
to
get
credibility,
and
so
we
can
do
that
with
gitlab
right,
so
it's
like
hey,
you
have
gitlab
core.
Are
you
interested
in
learning
about
what
happened
in
the
new
version
of
it
or
something
like
that?
And
that
can
be
a
good
way
to
have
a
conversation.
A
So
let
me
show
y'all
an
example
of
a
dependency
real,
quick.
Let
me
know
when
you
all
can
see
my
screen.
It
should
be
the
big
black
thing
great,
so
I'm
going
to
go
into
python,
real,
quick
and
one
common
thing.
That's
really
popular
like
if
you've
ever
played
like
poker
online
or
something
like
that
is
that
you
gotta
generate
chance
right,
so
there's
52
cards
in
the
deck.
A
So,
right
now,
there's
this
library
called
random
that
I'm
gonna
use,
and
if
I
use
this
now
that
I've
called
random,
I
can
generate
random
numbers
right.
So
over
here
I
got
0.49
over
here
I
got
0.6
over
here
I
got
0.59
and
then
how
like
I
can
make
a
game
is,
if,
like,
let's
just
say,
I'm
rolling
a
dice
right
so
between
I'd
have
one
six
of
these
random
numbers
be
like
a
one
one.
A
Six
of
these
random
numbers
be
two
all
the
way
through
six
and
that's
how
I
can
simulate
like
dice
being
rolled
and
stuff
like
that,
and
I
didn't
have
to
write
any
of
this
stuff,
I'm
just
using
the
random
library
to
do
this.
For
me,
and
so
this
is
a
really
simple
example
of
generating
random
numbers,
but,
like
you
can
also
have
libraries
that
help
me
create
buttons
and
things
like
that.
A
And
one
one
thing
more
about
dependencies
and
libraries:
gitlab
can
store
them.
That's
part
of
the
reason.
That's
part
of
our
sales
motion
so
as
opposed
to
like,
if,
if
I'm
like,
actually
an
engineer
that
is
creating
some
sort
of
library,
then
gitlab
can
store
that
and
ultimately
that's
an
example
of
tool
chain
consolidation.
So
I
can
save
money
as
an
enterprise,
because
that's
just
one
less
tool.
One
listing
to
maintain
gitlab
can
do
that
for
you
all
right
source
control
management.
A
Fundamentally,
all
your
developers,
what
they're
doing
is
they're
just
creating
applications
and
the
applications
you're
just
running
sets
of
text
files,
which
is
interesting
to
think
about,
is
that
we
pay
all
these
people
fifty
dollars
an
hour
whatever
to
like
update
text
files,
and
so
you
need
some
sort
of
tool
to
manage
all
of
these
text
files.
Why
is
that
the
case
with
an
open
source
project
like
git
lab?
A
Then
we
have
maybe
500
engineers,
but
on
top
of
that,
we
have
in
any
given
release
like
several
thousand
oso
changes
that
are
coming
in
from
the
community
right.
So
if
you
have
now,
let's
just
say,
2500
different
people
editing
the
same
set
of
text
files
that
becomes
really
really
really
confusing.
So
that's
fundamentally,
what
gitlab
does
is
it
manages
these
text
files
and
also
runs
ci
and
we'll
talk
about
what
ci
is
in
another
tenuki
tech
class,
so
source
control
management?
A
This
is
the
tool
that
stores
all
the
code,
the
market's
consolidated
on
git,
as
you
can
see
in
the
bottom
left,
they
have
on
the
bottom
right.
They
have
almost
the
entire
market
share,
and
one
of
the
things
to
know
about
this
is
that
it
gets
free
and
because
it's
free
and
open
source,
what
other
people
do
is
they
take
it
and
then
they
make
like
enterprise,
better
versions
out
of
it,
and
that's
fundamentally
one
of
the
that's.
What
github
does
that's?
A
A
For
software
engineering
projects.
This
is
a
very
stressful
cycle
and
just
like
how
like
one
of
the
things
I
hear,
all
the
time
is
like
how.
How
can
I
keep
my
job
fresh
and
other
things
is
like?
How
do
I
prevent
burnout
right?
This
is
actually
something
that's
actually
pretty
common
for
engineers
themselves
is
burnout
and
I've
definitely
been
burnt
out
before
I
was
an
engineer,
so
we'll
talk
about
the
different
stages
and
what
they
call
the
release
cycle
and
a
release
cycle
is
basically
just
sort
of
like
one.
A
The
next
version
of
git
lab
right.
So
let
right
now,
let's
just
say,
we're
on
gitlab
like
13.1.
So
then
we
have
another
month
to
make
gitlab
13.2
right.
So
there's
a
couple
of
stages
in
general.
The
first
stage
is
the
plan
stage.
So
there's
these
guys
called
product
managers
and
what
they
do
is
they
figure
out?
What
sort
of
stuff
should
we
do
like?
What?
What
should
we
build
and
there's
all
sorts
of
roles
that
they
use
to,
like
figure
out
how
to
do
which
things
should
get
in
which
things
shouldn't
then?
A
After
that
you
have
test
or
qa
people
and
what
they
do
is
they
check
the
product
to
make
sure
that
it
actually
works,
and
then,
finally,
you
have
release
or
engineers,
and
then
they
make
the
next
version
available.
So
it
could
be
updating
all
your
servers
or
something
like
that.
All
of
this
cycle
is
really
stressful
and
we'll
talk
about
why
in
a
couple
of
slides.
A
So
let's
just
talk
about
this
from
a
gitlab
perspective,
your
product
managers
are
going
to
come
in
they're,
going
to
say
what
do
we
want
in
the
next
version
of
git
lab
and
then
after
they
figure
that
out,
they're
going
to
create
a
bunch
of
issues
that
correspond
to
all
these
new
things.
So
if
we
want
the
next
version
of
git
lab
to
have
like
x,
y
and
z
and
the
reason
why
is
because
this
is
the
way
the
market's
going?
A
We
think
that
the
engineering
investment
is
going
to
be
the
value
the
cash
value
of
this
is
going
to
be
one
million
dollars
of
our
engineering
time,
and
we
think
that
we're
going
to
be
able
to
get
like
five
million
dollars
of
revenue
out
of
it
additional
revenue
out
of
it
right.
So
they
do
a
bunch
of
financial
math
to
figure
out
what
things
we
should
work
on
and
then,
after
that,
they'll
create,
like
maybe
50,
100
different
issues
and
then,
as
an
engineer,
what
happens
is
an
engineer
gets
assigned
this
issue
right?
A
So
when
I
was
an
engineer,
they
would
create
a
ticket
and
then
put
my
name
on
it
and
then
that's
what
I'm
responsible
for
for
the
next
three
months
over
here.
People
are
collaborating
on
the
issues.
What's
the
best
way
to
do
this,
so
have
you
thought
about
doing
it
this
way
and
then
okay?
Well,
what
about
this?
A
And
I
and
someone
from
another
team
could
say:
oh,
I
did
something
similar
a
while
ago
and
you
should
think
about
doing
it
this
way
so
on
and
so
forth,
and
they
basically
collaborate
and
once
all
the
collaboration's
done,
the
developer
goes
and
disappears
somewhere
and
works
on
something
and
they
hand
in
their
work
in
what
they
call
merge
requests.
So
this
is
someone's
answer
for
this
issue
and
here's
like
the
changes
that
he
wants
to
make.
A
Fundamentally,
once
again,
all
applications
are
it's
just
text
files,
so
he
wants
to
add
in
this
green
text,
take
out
this
red
test,
replace
it
with
this
green
test
and
so
on
and
so
forth,
and
you
have
to
basically
like
prove
that
your
answer
is
the
best
right
because,
especially
in
like
an
open
source
project
like
git
lab,
then
you
have
people
that
are
submitting
like
junk
and
people
who
are
submitting
things
that
are
half-baked.
So
you
have
to
like
prove
like
I.
They
may
not
know
me
right.
A
I
could
be
some
random
guy
in
like
some
country
that,
like
doesn't
know
the
gitlab
development
team,
so
I
would
have
to
like
prove
like
you
should
accept
my
change
to
your
product
because
of
x,
y
and
z,
so
over
here
you
can
see
like
some
of
the
comments
right.
So
it's
like.
I
believe
that
this
is
the
best
way
to
do
things
because
of
this
and
I've.
You
know
like
I've,
taken
these
other
approaches
and
then
so
people
can
question
you
on
it.
Like
hey,
have
you
thought
about
doing
this
hey?
A
I
also
worked
on
this
before
and
you
know.
There's
a
better
way
of
implementing
this
change
so
on
and
so
forth,
so
you
have
to
basically
prove
it.
One
of
the
really
great
things
about
gitlab
is
because
so
many
different
teams
can
use
it.
You
can
just
have
a
better.
You
can
just
have
better
collaboration
in
general.
A
So
if
you're
using
something
like
like
I'd,
say
like
a
github
traditionally
is
just
developers
and
the
big
problem
with
that
is
that
your
collaboration,
if
you're
using
github,
is
just
going
to
be
developers,
but
one
of
the
great
things
about
gitlab
is
that
everyone
can
use
it.
So
I
also
have
the
test
perspective.
I
also
have
the
devops
perspective
and
so
on
and
so
forth,
and
ultimately,
the
better
collaboration
means
that
I
come
up
with
better
ideas
and
approaches
in
general.
A
So
we
walk
through
a
bunch
of
this.
So
after
the
merge
request
is
merged,
then
I
basically
am
done
as
a
developer,
and
so
now
there's
these
tester
qa
engineers
that
all
they
do
is
they
bang
on
the
product
and
make
sure
that
it
works.
If
I
invented
a
new
button,
then
they're
going
to
click
on
the
button
and
make
sure
that
it
takes
me
the
right
screen.
If
I
like
made
some
new
back-end
system,
they
might
turn
it
on
and
off
5
000
times
and
to
see
if
it
still
works.
A
That's
part
of
what
test
engineers
do
and
then,
finally,
when
we
think
that
everything's
validated,
then
the
release
engineers
they
create
the
next
version
of
the
product
gitlab
can
do
all
of
this
stuff.
So
as
opposed
to
most
teams,
they
have
like
one
product
management
tool,
one
developer
sem
tool,
one
like
test
tool
and
one
bunch
of
release
tools.
You
can
just
use
gitlab
for
everything
which
is
really
really
really
helpful.
A
We
get,
we
can
just
merge
requests
we
talk
about.
This
is
where
collaboration
happens,
and
that's
basically,
what
the
the
value
of
gitlab
is
that
our
merger
crush
collaboration
is
going
to
be
better
because
different
people
are
using
this
all
right.
I
think
that
this
is
something
that's
really
really
important
for
us
to
understand.
So
this
was
a
big
meta
study
that
was
done
in
2017
and
it
had
to
do
with
software
projects
right.
So
the
whole
idea
is
we
want
to
have
you
know
like
grass
fund
industry.
A
So
what
are
some
of
the
industry
trends
that
we're
seeing
regarding
it?
They
found
that
14
percent
of
iq
projects
fail,
but
out
of
these
failures,
that
was
only
a
small
percentage
of
the
failures
right.
They
found
that
out
of
the
projects
that
didn't
fail,
31
percent
didn't
meet
their
goals,
43
exceeded
their
initial
budgets
and
49
of
projects
were
laid
so
literally
out
of
it
projects
and
the
customers
that
we
talked
to.
A
They
are
late
50
of
the
time,
and
I
just
want
to
like
talk
a
little
bit
about
some
stories
about
just
like
one
of
the
things
that,
for
my
own
developer,
experience
right
is
that
I
think
that
being
an
engineer
is
really
really
stressful
and
we'll
talk
about
why
right
so
you're
constantly
being
asked
to
do
things
that
don't
exist
and
your
teams
are
consistently
failing.
So,
like
I,
I
was
working
when
I
was
an
engineer.
A
I
actually
worked
on
one
of
the
best
top
like
products
that
red
hat
had
to
sell,
so
it
was
like
the
top
dog
product
right.
Our
hiring
was
great.
A
lot
of
people
really
wanted
to
be
on
this
team
because
it
was
really
famous
and
we
hired
talent,
so
the
people
that
we
we
hired,
they
had
many
many
years
of
experience.
It
wasn't
just
some
sort
of
like
guy
that
we
got
out
of
college,
but
even
though
we
hired
all
this
talent,
we
were
still
late.
A
A
I
have
to
work
until
like
9
p.m,
a
bunch
of
days
in
a
row
and
what
ends
up
happening
is
the
test
engineers
don't
do
as
good
of
a
job
as
they
could,
which
means
that
we
release
software.
That
is
bad
and
has
defects
in
them.
So
it's
really
really
common
that
software
gets
released,
that,
like
doesn't
work
completely,
and
the
engineering
teams
actually
know
that
it
doesn't
work.
A
If
you
think
about
like,
like
updating
your
iphone,
then
a
lot
of
times
like
when
you
update
your
iphone
like
something
stops
working
or
it's
weird
a
lot
of
times.
The
engineers
actually
know
that
what
they're
releasing
doesn't
work
and
they
release
it
anyway,
because
they
have
no
ability
to
influence
like
the
release
date
because
of
some
sort
of
business
decision.
A
So
this
entire
and
then
what
ends
up
happening
is
once
again
like
these
projects
are
late.
50
of
the
time,
which
just
creates
a
lot
of
stress,
if
you
imagine
like
this
release
cycle,
might
take
three
months
and
so
every
three
months
after
work,
late,
like
pull
60
or
weeks
for
several
weeks
in
a
row,
so
burnout's
pretty
high
among
certain
engineering
teams,.
A
D
A
Your
entire,
like
user
interface,
could
be
one
library,
a
dependency
or
a
framework.
Sorry,
so
all
of
what
I
just
said
is
about
a
framework
framework
could
be
many
different
libraries
combined
together,
a
dependency
in
a
library
is
generally
more
specific
to
like
one
thing,
but
I'll
just
give
you
an
example
of,
I
think
I
use
django
over
here.
Django
is
really
a
framework
and
it
includes
many
different
libraries
and
dependencies,
but
the
whole
idea
is
that
django
is
responsible
for
your
entire
unit
user
interface.
A
E
One
quick
question
I
had
just
on,
like
the
verbiage,
I
I
hear
a
lot
of
other
like
people
using
bitbucket
or
github,
calling
it
a
pull
request
to
all
other
scm
solutions.
Call
it
a
pull
request
and
we're
the
only
ones
that
call
it
a
merge
request
or
are
there
others
that
also
call
it
merge,
requests
or
something
else.
A
A
We
like
to
be
special
a
lot
of
the
time,
sometimes
it's
being
special
for
being
special
sake,
and
sometimes
it's
because
we
have
really
good
reasons
for
making
things
different
and
yeah.
So
to
answer
the
question,
the
industry
uses,
pull
request,
pull
request
and
merge.
Requests
are
basically
the
same
thing.
E
A
Yeah,
so
that's
a
really
great
question
and
it
has
to
do
with
why
certain
engineering
organizations
are
better
than
others.
Honestly,
the
number
one
reason
why
an
engineering
organization
is
better
than
another.
One
is
because
of
the
culture
that
is
in
that
organization,
so
certain
organizations
you
can
just
think
are
really
really
big
right
and
because
they're
really
big,
you
may
have
a
development
team
in
india
and
then
your
test
team
is
in
china
and
then
and
then
things
are
sprawled
out
and
then
what
ends
up
happening.
A
A
lot
of
the
time
is
that
people
don't
communicate,
and
when
people
don't
communicate
between
your
groups,
then
there's
misses
all
the
time,
so
the
1a
and
1b
of
why
organizations
aren't
that
efficient.
One,
a
is
that
it's
just
like
a
cultural
problem,
so
lack
of
communication,
lack
of
people
working
together.
Lack
of
you
know,
accountability
and
transparency.
A
One
b
is
yeah,
so
one
is
culture.
One
b
is
lack
of
communication.
I'd
say
that
in
their
typical
engineering
organization
around
at
least
20
percent
of
all
of
your
engineering
time
is
completely
useless
because
people
didn't
communicate.
When
I
was
an
engineer
that
happened
all
the
time
is
that,
like
I'd,
be
designing
this
thing,
it
depended
on
someone
else's
work.
A
The
person
that
like
was
actually
building
the
thing
that
I
depended
on,
changed
it
and
then
so
he
didn't
and
then
he
didn't
communicate
it
with
me
and
then
so.
I
spent
the
next
three
days
like
building
something
that
ended
up
not
being
used.
That
happens
all
the
time
in
engineering
organizations
so
yeah.
So
it
comes
down
to
communication
and
culture
for
why
engineering
organizations
don't
deliver.
B
Chris,
when
you
say
many
of
the
projects
are
behind
schedule,
are
they
pushed
or
they're
pushed
out
with
bugs?
What
are
some
of
the
consequences
for
failures
from
let's
say,
an
engineering
perspective?
Are
they
are
engineering
staff
members
fired?
Are
they
reprimanded
if
they
push
out
something?
That's
not
legit.
A
Yeah
it
has
to
do
with
your
organization,
a
good
engineering
organization
will
hold
people
accountable,
but
a
lot
of
times,
there's
honestly
huge
problems
in
engineering
organizations
simply
because
I'll
just
put
it
this
way.
So,
like
I
play
basketball
right,
basketball
is
about
100
years
old,
which
means
that
we
have
a
lot
of
really
great
best
practices
for
basketball
and,
like
you
know,
if
you're
a
coach,
you
can
look
at
a
team
for
like
five
minutes
and
understand
how
like
mature
people,
are
right.
A
The
problem
with
software
engineering
is
that
software
engineering
has
only
really
existed
for
30
years
and
during
that
30-year
period
of
time
it
is
literally
changed
like
it
changes
dramatically
every
two
years,
and
so
the
roles
and
best
practices
for
software
engineering
are
completely
different
and
best
practices
only
exist
after
we
gather
data
right.
So,
for
instance,
like
the
public
cloud
is
something
that's
only
really
existed
for
four
to
five
years,
but
it
has
dramatically
changed
best
practices
for
software
engineering
yeah.
I
I
hope
I
am
answering
your
question,
but.
B
A
A
A
Cool,
so
now
that
we
talked
about
developers,
we
got
to
talk
about
the
hardware
side
of
things.
You
need
a
computer
to
run
all
of
these
text
files
right
and
these
computers
are
called
servers
so
over
here.
Each
of
these
rectangular
units
is
a
server
there's
around
60
servers
in
this.
This
picture,
all
of
like
a
vertical
row
of
these
servers,
is
what
we
call
a
rack
and
back
in
the
day,
what
you
do
is
if
I
were
a
small
business
I
buy
five
of
these.
A
A
Two
percent
of
it
goes
into
servers
in
the
united
states,
so
there's
more
energy
that
goes
into
these
machines
than
there
is
for
all
of
the
street
lights
and
traffic
lights
in
our
entire
country,
which
is
kind
of
really
crazy
to
think
about
over
here
you
can
see
a
map
of
some
of
the
data
centers
that
we
know
about
in
the
united
states,
and
one
of
the
things
that
I
really
want
to
point
out
to
is
like
speed.
So
we
talked
about
how
I
want
to
have
competitive
advantages
over
my
customers.
A
If
my
e-commerce
business
is
not
the
fastest,
then
I'm
at
a
disadvantage
over
a
five
year
time
period,
I
may
lose
20
market
share
right
compound
that,
with
the
fact
that
most
digital
businesses
and
markets
are
a
winner
take
takes
all
like.
So,
for
instance,
in
new
york
city,
you
can
have
there's
enough
market
there
for
probably
like
50
to
100
hardware
stores
in
electronic
business.
A
If
amazon
wins
that
pushes
out,
like
basically
everyone
else
right,
amazon's,
just
like
the
big
winner
right,
so
they
really
think
about
things
like
performance
over
here,
and
so
if
I
live
in
seattle
and
I'm
going
to
a
website
that
the
servers
are
in
austin
texas,
it'll
take
about
one
second,
for
you
know
for
me
to
go
talk
to
this
computer
server
over
here.
That
takes
some
time
to
get
a
response
takes
about
one
second,
for
that
response
to
go
back
and
so
all
of
a
sudden.
A
This
is
two
and
a
half
seconds
which
is
too
slow
right.
So
I'm
on
a
competitive
disadvantage.
If
that's
how
my
servers
are
distributed,
and
so
what
people
do
is
amazon's
smart.
They
know
that
they
got
to
go
win
the
performance
battle.
They
are
also
going
after
the
features
battle
right
and
they
got
to
have
competitive
advantage.
So
what
they
do
is
they
have
servers
in
seattle
in
portland
and
san
francisco
all
across
the
country,
and
then
they
have
all
of
these
performance,
optimization
engineers
where
they
basically
say.
A
Okay,
you
live
over
here,
you're,
our
closest
amazon
data
center
is
here.
Therefore,
you
should
go
talk
to
this
amazon
data
center,
and
so
they
actually
do
all
these
engineers
are
paid
like
75
an
hour.
It's
a
really
expensive
thing,
but
the
investment
is
worth
it
for
a
digital
business,
because
that's
how
I
have
competitive
advantage
over
my
competitors
is
just
by
being
the
most
fastest
and
reliable
service,
so
even
think
about
netflix
right.
A
A
Very
good,
okay,
so
cloud
computing
is
a
new
paradigm
in
technology
that
it's
transforming
how
the
id
space
previously
you
know
you
bought
five
of
these.
If
you're
a
small
business
that
cost
you
twenty
thousand
dollars.
The
big
problem
is:
if
I'm
scaling
up,
then
I
gotta
buy
another
one.
I
have
to
wait
two
weeks
for
that
to
come
in
the
mail.
I
should
go
through
procurement,
then
my
engineers
bang
on
it
for
like
a
month
and
then
all
of
a
sudden
like
I
have
a
new
web
server
and
that's
really
really
slow.
A
That
entire
process
takes
me
a
month
and
a
half
right.
So
with
cloud
computing,
you
can
do
this
way
faster
and,
as
opposed
to
you
owning
your
own
hardware,
then
someone
else
owns
your
hardware.
So
these
are
the
cloud.
Vendors
amazon
was
the
first
in
the
market,
so
they
have
a
huge
chunk
of
the
market
share.
Microsoft
is
number
two
google's
number
three
just
to
like.
Put
this
into
reference
get
labs
revenue.
Our
annual
revenue
right
now
is
around
like
130
million
dollars.
A
Microsoft
closed
one
deal
that
was
over
was
that
was
about
100
times
that
about
a
year
ago,
with
the
us
department
of
defense.
So,
like
one
deal
being
a
hundred
out
of,
like
you
know
the
40
000
that
they
have
in
a
year
just
that
one
deal
was
over
100x,
our
entire
annual
revenue.
So
it's
a
it's
a
huge
huge
market
and
part
of
the
reason
why
cloud
computing
is
so
successful
is
that
they
make
it
easy
for
people
to
get
new
hardware
right.
So
this
is
amazon
cloud
and
over
here.
A
If
I
want
to
get
like
a
new
server,
then
look
at
how
easy
this
is
to
get
a
new
server.
All
I
have
to
do
is
go
to
instances
launch
an
instance
and
what
type
of
instance
so
I
can
get
you
know,
amazon
linux.
I
can
get
red
hat
linux.
I
used
to
work
at
red
hat.
So
let's
pick
this,
it
asks
for
all
the
hardware
right.
So
how
many
cpus?
Do
you
want?
A
How
much
memory
do
I
want
all
of
this
stuff
costs
different
money,
so
in
general,
like
a
medium
size,
you
know
server
is
going
to
be
around
like
12
cents
per
hour,
but
like
a
big
one.
If
I
were
doing
big
data
stuff
would
be
like
around
40
cents
per
hour.
So
let's
just
pick
this
one
configure
instance
details.
A
I
want
a
hundred
of
them
right
and
keep
in
mind
like
the
old
way
of
doing
things
is
that,
like
I
buy
some
physical
server
as
I
go
through
procurement,
then
my
engineers
have
to
spend
it
like
a
month
banging
on
it
before
it's
ready
for
doing
anything.
I
can
get
500
of
these
servers
if
I
just
by
going
and
typing
this
in,
so
I'm
not
going
to
do
that,
but
I'll
put
in
two
add
storage
right.
What
kind
of
storage
do
I
want-
and
this
is
next
to
this
firewall
stuff?
A
So
it's
like
what
ports
do
I
want
open?
This
is
fine.
This
is
just
ssh
and
if
I
click
review
and
launch,
then
in
two
minutes
I
will
have
two
servers
that
are
ready
for
me
to
use,
and
so
this
is
literally
just
like
it's
a
huge
paradigm
shift
for
how
it
works
simply
because
you
can
do
things
way
faster
and
you
can
have
consumption
based
pricing.
Another
real
reason
why
the
cloud
is
a
big
deal
is
let's
just
say
that
I'm
a
small
business
right.
A
So
I
got
my
a
round
funding
two
million
dollars
in
funding,
and
I
don't
know
if
I'm
gonna
exist
in
three
years,
because
my
entire,
like
goal,
is
to
try
to
get
like.
You
know
two
hundred
thousand
dollars
in
revenue,
so
I
can
get
my
b
around
right.
So
what
I
don't
want
to
do
is:
invest
40
000
in
capital
expenses.
I'd
much
rather
pay
an
operations
cost
of
like
you
know,
100
a
month,
because
I,
if
I,
if
the
business
doesn't
work,
I
don't
want
that
sunk
cost
right.
A
I
want
to
just
pay
monthly
as
opposed
to
that.
So
this
is
important
because
git
lab
is
really
really
good
for
the
cloud
we
were
designed
with
the
cloud
in
mind
and
so
get
loud
can
scale
up
and
down
in
the
clouds,
saving
people
money
and
also
it's
really
good
for
a
lot
of
our
customers.
Do
is,
like
you
know.
A
All
right,
so
I'm
gonna
talk
about
virtualization
in
containers,
real,
quick,
I'm
I'm
gonna
try
to
explain
this
in
like
the
best
possible
way.
If
this
is
not
clear,
then
just
interrupt
me
and
let
me
know,
but
this
is
important,
because
our
customers
are
using
virtual
machines
and
containers
and
one
of
our
fundamental
value
drivers
is
that
we're
really
good
for
containers.
A
So
we
need
to
understand
what
containers
are
why
businesses
have
them
so
that
we
can
ask
really
great
questions
for
these
customers
and
help
to
educate
them
on
our
value
offering
regarding
this
stuff.
So
what's
virtualization
virtualization
is
the
ability
to
split
a
machine
into
a
bunch
of
machines?
A
So
if
you,
if
you've
ever
had
like
a
super
nintendo
emulator
or
something,
then
I
have
like
a
virtual
super
nintendo
running
on,
like
my
pc
and
so
like.
Why
does
this
matter
so
previously,
and
one
thing
to
important
to
note-
is
that,
like
in
general
in
engineering,
you
only
want
one
application
for
each
of
your
servers.
This
is
just
like
some
engineering
best
best
practice,
and
if
I
try
to
get
too
many
applications
on
one
server,
then
you
just
run
into
problems.
That's
just
how
it
happens,
one.
A
What
reason
why
in
general,
why
this
would
be
bad?
Is
that,
like,
let's
just
say
that
I
have
20
applications
that
are
running
on
this
server,
they're
important,
like
salesforce
and
all
this
other
stuff
is
running
on
it
right
my
email
system's
running
on
it,
and
then
I
update
one
of
these
applications
and
it
requires
a
restart.
Well,
if
I
restart
this
server
and
now
it
brings
down
20
of
my
applications
right
as
opposed
to
just
one.
So
that's
just
one
example,
but
there's
a
bunch
of
reasons
why
you
want
one
application
per
server.
A
So
here's
the
problem,
though
the
problem
is
what,
if
one
of
my
applications
only
requires
two
percent
of
like
the
memory
and
stuff
of
this
server,
so
it's
some,
like
my
printer
surface,
really
really
really
lightweight.
Well.
That
means
that
98
of
this
server
is
completely
wasted
from
a
resource
point
of
view
right.
So
it's
just
not
efficient
way
of
doing
things.
So
it'd
be
much
better
if
I
can
somehow
compartmentalize
the
server
into
a
bunch
of
different
like
operating
spaces.
A
A
If
someone
said
something
like
okay
great
so
over
here,
I'm
gonna
turn
on
this
thing
called
virtualbox
and
once
again
this.
This
is
just
a
mac
right,
but,
as
you
can
see
over
here,
I
have
this
red
hat
linux
server
that
I'm
going
to
now
turn
on
inside
my
mac,
and
so
I'm
going
to
hit
the
start
button
here
and
then
all
of
a
sudden
now
virtual
box
is
running,
and
now
my
linux
server
is
starting
to
boot
up
right.
A
It's
got
like
virtualized,
hard
drives
and
stuff
like
that,
and
this
is
like
the
login
screen
it's
hard
to
see
right
now,
but
the
whole
idea
is
that
like,
even
though
this
is
mac
os,
I
could
have
10
of
these
virtual
machines
running
on
my
mac.
Three
of
them
could
be
linux,
one
could
be
windows
and
the
idea
of
me
having
to
waste
all
of
the
rest
of
my
server
for
one
app.
A
A
Okay,
so
that's
virtual
machines
if
you
get
something
from
the
public
cloud,
you're
getting
fundamentally
a
virtual
machine
and
if
it's
on-prem,
they're,
probably
using
vmware,
all
right
we're
going
to
talk
about
containers
now,
containers
are
really
really
really
big
deal
and
it's
like
just
like
how
every
three
to
five
years
there's
something
that
dramatically
shifts
how
it
works.
Containers
are
one
of
these
things
and
it
is
dramatically
going
to
shift
how
it
works,
and
one
of
the
things
that's
really
important
to
note
is
just
like
sort
of
explaining
what
this
is.
A
A
The
way
I
think
about
containers
is
that
it
is
the
next
version
of
virtualization,
that's
just
better.
So
all
of
the
benefits
that
you
get
from
having
a
virtual
machine,
you
get
that
with
containers
as
well.
They
work
a
little
bit
differently,
but
from
a
business
perspective,
the
reason
why
people
care
about
them
is
that
they're
way
faster
and
way
more
resource
efficient.
A
So
the
idea
is
that,
like
in
my
mac,
if
I
could
get
10
vms,
I
might
be
able
to
get
like
50
containers
and
ultimately
I
can
do
more
workloads
and
run
more
web
applications
and
stuff
using
containers.
Then
so,
let's
just
say
that,
like
I'm,
a
digital
business,
my
operation
expenses,
for
my
servers
are,
let's
just
say,
a
million
dollars
a
year.
If
I
wanted
to
have
an
equivalent
workload
between
virtual
machines
and
containers,
I
could
probably
save,
like
maybe
50
of
my
operating
expenses,
I'm
sort
of
making
that
number
up.
A
So
don't
quote
me
on
that,
but
is
it
it
is
a
substantial
difference
in
terms
of
its
efficiency.
So
that
being
said,
the
entire
it
market
is
going
towards
containers.
It's
validated,
it's
not
some
sort
of
experimental
thing.
It's
something
that
every
single
like
it
director.
They
either
have
these
containers
or
they
want
containers
in
their
environment
because
the
value
is
already
substantiated
by
industry.
A
So
we
gotta
talk
about
what
docker
and
kubernetes
is
so
what
docker
is
is
if
I
want
containers
running
on
one
machine
so
like
my
mac,
then
I
have
docker,
but
you
know
like
if
I'm
netflix
or
from
amazon,
then
I
need
more
than
one
machine
right.
I
need
a
hundred
thousand
half
a
million
servers
all
running
like
my
web
application.
So
if
you
want
like
a
bunch
of
machines
running
containers,
then
what
I
really
need
is.
I
need
some
sort
of
like
overlay.
A
Oh,
like
overhead
layer,
that's
going
to
manage
the
entire
process,
so
this
sort
of
management
layer
is
going
to
determine
how
many
containers
are
on
each
which
each
machine,
how
many
machines
are
in
my
cluster.
What
happens
if
I
turn
a
cluster
like
a
server
off
like
those
containers
should
theoretically
migrate
to
another
machine
so
that
my
web
service
doesn't
stop
right
and
so
that
management
layer
is
what
we
call
kubernetes
kubernetes
is
a
management
layer
for
if
you
want,
like
fifty
thousand
a
hundred
hundred
thousand
machines,
running
containers
all
in
your
same
same
environment.
A
A
A
A
So
we're
really
greatly
positioned
for
this
right
now
and
just
to
summarize,
if
I
want
containers
running
on
one
machine,
I
use
docker.
If
I
want
50
000
machines
running
containers,
I
need
some
sort
of
management
layer.
That's
what
kubernetes
is
kubernetes
is
validated.
Everyone
wants
to
use
it.
It's
the
hot
stuff
in
our
industry,.
A
If
I
go
over
here,
however,
to
get
lab.com
api
v4
project
7764
and
this
7764
is
over
here
right.
So
this
is
the
endpoint
that
corresponds
to
what
we
were
talking
about
earlier.
Then
you
can
see
that
there's
this
gigantic
blob
of
text.
The
important
thing
is
that
everything
that
is
on
this
endpoint
is
also
here
somewhere,
so
id
7764
description
source
for
https
about.gitlab.com
description.
This
repo
project
is
the
public-facing
marketing
website
for
gitlab,
including
purpose
the
handbook
right,
and
so
every
single
major
web
service,
facebook,
google
maps
gitlab.
A
A
Yeah
so
like
this
is
a
restaurant,
that's
in
raleigh
and
as
I
scroll
down,
one
of
the
things
that
you
see
over
here
is
for
some
reason,
even
though
I'm
on
yelp
there's
google
maps,
that's
in
yelp
somehow,
and
so
immediately.
I
start
thinking
one.
How
does
this
work
from
an
engineering
perspective
and
two?
Why
would
google,
which
is
like
another
company,
allow
this
other
business
to
like
use
their
stuff
like
they
have
to
have
some
business
agreement
right?
Otherwise,
you're
just
like
copying
my
service
somehow
and
I
better
get
a
cut
of
it.
A
A
A
But
if
they're
using
an
api,
then
they
can
do
that
exact
same
thing
and
it's
going
to
be
way
way
faster.
If
you're
using
api,
it
basically
comes
down
to
speed,
and
so,
let's
just
sort
of
zoom
out
a
little
bit
every
single
major
web
application
or
our
e-commerce
business.
They
have
an
api
and
fundamentally,
why
I
want
an
api.
If
I
have,
one
of
these
services
is
because
if
people
are
using
my
data,
I
can
charge
your
money.
That's
what
google
does
right
and
the
other
thing
is.
A
This
increases
the
visibility
of
the
e-commerce
platform
or
service
that
I've
built
every
time.
Someone
sees
google
maps
on
some
other
website,
that's
not
google
maps.
It
just
increases
the
visibility
of
the
tool
that
I
built
out.
So
now
more
people
are
using
google
maps
and
now
I
get
more
people's
data
and
I
get
more
money
by
advertisements
and
things
like
that
right.
So
that's
why
I
want
to
have
an
api
in
general.
A
All
right,
so,
let's
just
bring
everything
home
technology
is
just
like.
I,
when
I
was
a
developer
for
five
years
right,
and
so
it's
almost
like
you
have
all
these
projects
you're
late,
sixty
percent
of
the
time
that
every
time
I'm
late,
not
the
project's
late,
I
already
know
going
into
it.
Then
I'm
going
to
pull
60
hour
weeks
right
and
that's
like
that's
that's
the
rule,
that's
not
the
exception
and
so
burnout's
really
high.
A
I've
definitely
been
burnt
out
as
an
engineer
before,
and
just
because
like,
if
you
just
imagine,
if
you're
late,
50
percent
of
the
time,
then
what
happens
people
are
stressed
out,
which
means
that
everyone's
blaming
each
other
right.
So
it
can
be
like
a
really
stressful
environment,
and
why
is
this
the
case
well?
A
Part
of
it
is
that
technology
changes
are
just
happening
so
fast
and
so,
like
I
have
a
friend
who's,
a
nurse
practitioner
and
I
watched
her
go
through
graduate
school
and
she
spent
like
you,
know:
200
hours,
learning,
neurology,
200
hours,
learning
the
cardiovascular
system
so
on
and
so
forth,
studied
her
butt
off
for
two
years.
But
now
her
skill
set
is
basically
going
to
set
her
up
for
life
right
because
it's
not
like
she
has
to
learn
like
new,
modern
medicine
practices
every
once
in
a
while,
but
like
when
you're
an
engineer.
A
If
you
have
a
web
service
that
is
best
in
class,
it
is
going
to
be
completely
obsolete
in
about
a
year
and
a
half
to
two
years
literally
like
it
will
be
like
it
will
be
completely
need
re-architecting
in
like
one
and
a
half
to
two
years,
so
you
never
really
get
there
just
because
technology
is
going
so
quickly.
If
I
had
a
really
great
application
before
the
public
cloud
came
out,
once
the
public
cloud
came
out,
then
it's
no
longer
like
a
best-in-class
application.
A
My
competitors
are
starting
to
implement
this
public
cloud
stuff
and
if
I
don't
do
it
they're
going
to
save
30
of
their
marginal
cost
on
me
and
if
they
do
that
for
a
long
enough
period
of
time,
they're
going
to
have
a
business
advantage
over
me
right.
So
it's
a
struggle
because
technology
just
changes
so
quickly.
What
are
the
specific
things
that
people
care
about?
A
You
know
so
in
terms
of
features
right,
so
we
have
a
team
here
that
literally
every
time,
microsoft,
devops
or
github
pushes
out
some
new
thing.
Then
we
immediately
need
to
know
about
it
when
we
need
to
like
update
all
of
our
competitive
sales,
intelligence
and
stuff
on
it,
and
everything
right
so
features
matters
a
lot.
If
git
hub
can
do
certain
things
way
better
than
us,
then
we
gotta
figure
out
like
how
to
combat
that,
because
over
a
five-year
time
horizon,
if
they
have
significant
features
over
us,
then
we
might
not.
A
We
might
lose
our
market
share
right
in
terms
of
user
experience.
It
happens.
It
just
changes
all
the
time,
what's
popular
in
one
season's
gonna
be
like
not
cool
in
in
the
next
couple
of
seasons
right
in
terms
of
security.
This
is
a
really
big
one.
I'll
just
put
it
this
way
if
twitter
can
get
hacked
for
you
know
like
the
twitter
hack
that
happened
like
about.
I
think
it
was
like
a
month
and
a
half
ago,
and
then
they
got
like
a
bunch
of
bitcoin
from
that.
A
A
Even
if
you
hired
all
these
guys
from
mit
and
stanford-
and
you
know
you
basically
had
them
audit
your
entire
application.
The
fact
that
your
application
is
just
changing
so
quickly
means
that
there's
always
going
to
be
vulnerabilities
right.
So
security
is
a
huge
problem.
Most
technology
companies
feel
behind.
Imagine
if,
like
you're,
literally
not
delivering
on
your
projects,
50
of
the
time
you're
thinking
about
like
that's
just
your
mindset
right,
it's
just
sort
of
like
it
like
being
on
a
sports
team.
That's
like
losing
a
lot!
A
So
there's
a
lot
of
pressure
from
that
as
well.
Where's
get
head
fit
into
this.
I
wouldn't
have
come
to
gitlab.
If
I
didn't
believe
in
the
product.
I
really
do
think
that
it
is
a
product
that
if
our
customers
were
able
to
leverage
it
completely,
it
would
help
them
to
systematically
have
competitive
advantages
over
other
people
simply
because
they
could
be
more
efficient.
As
an
organization,
so
I
was
a
developer
for
half
a
decade.
A
If
we
had
git
lab,
it
would
totally
have
helped
us
a
lot.
If
we
fully
utilized
some
of
its
capabilities
and
features,
we
would
be
maybe
at
least
like
20
percent
more
efficient
and,
if
you
think
about
it,
like
our
engineering
budget,
was
like-
maybe
a
million
dollars
a
year
so
like
to
become
20
more
efficient.
That
value
is
like
two
hundred
thousand
dollars,
you're
just
investing
in
one
tool
right.
A
So
how
do
we
do
this
become
more
efficient,
deliver
better
products
faster,
reduce
security,
risk
kind
of
leaving
the
session
on
cliffhanker
but
like
if
you
take
the
tanuki
tech,
210
and
211,
we'll
talk
about
exactly
diving
into
how
we
do
this,
and
you
know
the
questions
that
we
can
ask
our
customers
to
help
uncover
needs
and
basically
explain
why
this
is
the
case
all
right.
So
just
talking
about
homework,
real
quick.
A
So
how
you
all
get
like
credit
for
these
sessions
is
by
filling
out
these
google
docs
only
spend
around
30
minutes
on
this.
I'm
not
looking
for
people
to
spend
a
ton
of
time
on
it,
but
the
whole
reason
why
I
I
actually
pull
up
the
wrong
one.
Why
it's
important
to
go
through
some
of
these
questions
is
because
I
really
want
y'all
to
have
the
exact
terminology
down
for
when
you're
talking
to
like
a
devops
lead
or
like
a
lead
engineer,
and
the
reason.
A
Why
is
because
they
have
very
very
specific
terms
that
they
use,
and
then,
if
we
use
them
a
little
bit
wrong,
then
it's
real
easy
to
lose
credibility.
So
I
want
to
help
you
make
sure
that,
like
you're
having
great
conversations
with
these
people,
all
of
these
questions
have
to
do
with
technology
and
they're
questions
that
could
be
used
in
a
call
so
yeah.
Just
what
do
y'all
think
about
getting
this
in
committing
to
getting
this
in
by
are
on
friday
of
this
week,
so
that'd
be
four
days
out.
A
All
right
great,
so
that's
it
for
this
session.
Is
there
anything
that
I
can
do
to
like
clarify
anything
we've
talked
about.
I
know
that
we've
jumped
around
and
talked
about
many
different
topics,
otherwise
feel
free
to
you
know
thanks
for
your
time
and
I'll,
see
you
in
a
next
session,
but
I'm
happy
to
answer
any
questions.
If
anyone
has
any.
B
A
That's
a
really
great
question.
I
would
say
that
there
was
only
one
time
in
which
I
was
really
really
really
burnt
out
and
honestly.
The
emotions
that
I
had
was
just
sort
of
like.
I
literally
could
not
do
my
job
anymore
because,
like
I
couldn't
concentrate
and
during
that
period
of
time,
so
it's
like
to
just
sort
of
like
put
the
emotions
of
like
what
this
is
like.
It's
just.
A
I
was
specifically
a
test
engineer
and
when
the
developers
are
pushing
their
stuff
in
they're
late
all
the
time,
which
means
that
specifically
me
I
need
to
go
put
in
a
60
or
a
week
because
of
something
that,
like
I,
have
no
control
over
right.
It
was
honestly
really
frustrating
and
it
was
also
just
sort
of
like
if
you
imagine
just
doing
that,
every
single
release
we
have
releases
every
four
months-
they're,
not
I'm
salaried,
so
they're,
not
paying
me
any
more
money
right
like
so.
A
It
just
gets
really
really
frustrating
and
especially
because
it's
like
completely
100
avoidable.
So
it's
like
literally.
If
people
collaborated
more,
then
we
could
have
avoided
like
this
entire
situation
in
the
first
place,
burnout's
really
common
among
engineers,
it's
not
as
common
as
sales
sales
has
30
turnover
year
after
year.
So
it's
not
that
high,
but
it
is
high
in
general,
across
industry,.
E
A
Yeah,
that's
a
really
great
question,
so
we
the!
I
think
that
the
answer
is
that
gitlab
literally
can
integrate
with
everything
because
of
our
api,
and
is
that
a
concession
or
is
that
like
something?
That's
like
a
strength
of
us
people
are
used
to
because,
like
apis,
are
how
applications
talk
to
each
other
by
us
saying
you
can
integrate
with
anything
through
our
api?
That
is
literally
what
everyone
else
is
doing.
So
it
is
it's
not
a
concession
right.
It's
the
truthful
answer
is
that
you
can.
A
If
it's
jenkins,
you
can
integrate
github,
literally
whatever
sort
of
security
thing
that
you
want.
You
can
hook
it
into
get
lab,
so
obviously
we
don't
want
to
be
like
everyone
else.
We
want
to
have
competitive
advantages
over
other
people,
and
so
we
want
to
build
on
top
of
that
and
make
it
easier
right
so
like
our
well,
so
how
we
do
this
is
like
by
making
it
even
better
than
an
api
integration.
A
So
when
we
talk
about
our
terraform
integration,
we
make
it
even
easier
than
building
out
something
from
like
an
api
integration
standpoint,
and
I
know
that
that
was
kind
of
a
convoluted
answer.
The
short
summary
answer
is
that
we
can
integrate
with
everything
through
our
api.
That
is
not
a
concession
that
is
just
standard
industry
practice.
A
matter
of
fact,
our
api
is
very,
very
good.
You
can
there's
like
different
tiers
of
like
apis.