►
From YouTube: TT210: Create and Plan
Description
YouTube description:
This is a Tanuki Tech session on 9/21/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
Good
all
right
so
welcome
to
create
and
plan.
What
are
we
going
to
be
talking
about
today
and
what's
the
goal
right
so
get
labs?
Really
deep,
we're
going
to
be
talking
about
is
two
specific
product
features
with
git
lab,
and
one
of
the
things
I
always
say
is
make
this
conversation
your
own.
If
you
already
know
some
of
this
stuff,
just
let
me
know
we'll
skip
a
bunch
of
slides
if
there's
things
that
you
want
to
hear
more
about
just
interrupt
me.
A
Ultimately,
my
goal
with
this
session
is
so
that
I
can
serve
you
and
to
better
like
make
you
understand
and
articulate
this
so
that
you
can
better
have
better
conversation
with
customers
right.
So
that's
it
so
yeah.
The
goal
of
this
session
is
to
have
better
conversations
regarding
these
two
parts
of
our
product.
How
do
we
plan
on
doing
this?
I
want
everyone
here
to
understand
what
source
control
management,
agile,
ticketing
solutions
are.
A
I
know
that
there's
a
lot
of
buzzwords,
and
so
it's
just
sort
of
like
I
want
to
demo
a
lot
of
this
stuff
and
the
last
two
parts
are
exactly
that.
So
I'll
do
a
quick
demo
for
some
of
these
things,
and
then
we
have
our
own
mini
project
so
we'll
see,
if
there's
time
at
the
end,
to
do
the
mini
project.
A
So
let's
jump
right
in
get
lab's,
really
broad
right,
there's
10
different
product
stages.
What
we're
talking
about
right
now
with
is
simply
these
two
product
stages.
There
are
an
additional
three
sessions
that
cover
the
rest
of
the
product.
A
If
you
take
a
look
at
this
picture
in
the
bottom
right,
you
know
imagine
if
you
had
like
one
stand
in
this
market
and
there's
literally
like
40
other
people
that
are
selling
the
exact
same
thing.
Unfortunately,
that
is
the
case
with
create
and
plan
I'll.
Just
show
you
a
quick
slide
over
here,
so
agile,
ticketing
solutions.
A
I
just
googled,
like
you,
know
just
rankings
and
then
the
first
article
that
appeared
is
40
best
project
management,
software
and
tools.
You
really
do
not
want
to
be
on
the
list
of
one
out
of
40
right.
You
want
to
be
have
unique
differentiators
so
that
you
stand
out.
If
you
are
real
literally
like
one
out
of
40,
then
one
it
takes
a
ton
of
effort
to
get
on
that
list.
A
In
the
first
place,
you
have
to
put
a
ton
of
effort
to
maintain
your
ranking
on
that
list
and
there's
all
these
other
people
that
are
trying
to
take
away
your
market
share
right.
So
that's
why
we
talk
about
unique
differentiators
in
get
lab.
This
is
how
we
stand
out
and
I
never
try
to
sell
with
create
and
plan
what
I
try
to
sell
with
a
fact
is
that
we
are
one
tool
for
the
entire
devops
life
cycle.
That
is
our
unique
differentiator.
A
If
we
lead
with
that,
and
if
we
articulate
that
really
well,
then
that's
something
that
basically
no
one
else
can
really
do
and
that's
how
we
stand
out
and
so
really
the
value.
Isn't.
The
fact
that
we
have
scm
and
agile
ticketing
solutions
is
the
fact
that
everything
is
built
in
together,
and
so
that
saves
all
of
your
engineers,
time
money
you
get
better
collaboration,
efficiency
and
so
on
and
so
forth,
because
everything
is
built
into
the
same
thing.
A
A
Yeah,
okay,
well,
that's
cool
we'll
go
through
it,
so
it's
really
important
when
we're
talking
about
sem.
We
have
to
understand
why
sem
exists
in
the
first
place
right
and
one
of
the
things
that
was
really
a
big
shock
to
me
when
I
started
programming
about
like
seven
years
ago,
was
that
basically,
every
single
website,
every
single
application,
every
single
thing
that
engineers
do
all
day,
it
is
literally
just
a
text
file.
That's
all
it
is,
and
so
programming
languages
is
like
the
syntax
of
this
text
file.
A
So
like
right
now
we
are
working
on
git,
lab
and
fundamentally,
what
git
lab
is.
Is
it's
just
all
of
these
text
files?
If
we
go
into
this
specific
text
file,
this
is
one
of
the
text
files
that
actually
makes
up
gitlab.
There
may
be
around
10
000
total
files
that
make
up
gitlab,
but
netflix,
google
amazon,
all
of
these
websites,
fundamentally
at
the
deepest
level.
All
they
are
is
a
bunch
of
text
files
and
so
yeah.
A
So
all
applications
are
written
in
programming
languages
and
they
just
make
up
these
text
files,
and
it's
really
important
to
understand
that
all
these
procuring
languages
are
doing
is
they're
telling
machines
to
do
things.
So
let
me
just
show
this
in
action.
Real,
quick.
A
Great
and
so
aletha,
let
me
see,
let
me
know
what
you
see
is
happening
in
the
background
in
my
desktop
after
I
hit
enter
over
here.
So
what
I'm
basically
going
to
do
is
I'm
going
to
run
this
script,
and
so
you
can
see
this
script
over
here.
This
is
there's
only
20
lines
and
let
me
know
what's
happening
in
the
background
on
my
desktop
after
I
run
this
script.
A
Yeah,
that's
exactly
it
right,
so
it's
just
creating
a
bunch
of
folders,
so,
instead
of
creating
a
bunch
of
folders
all
these
co,
all
this
code
that
I
was
looking
at
earlier-
this
is
just
like
could
be
create
a
button
for
git
lab
could
be
do
something
else
could
be.
A
So,
let's
talk
about
what
source
control
management
is
all
applications
are,
is
just
a
running
set
of
text
files
and
ultimately
you
need
a
tool
for
storing
these
text
files.
I
was
an
engineer
for
about
half
a
decade
I
literally
spent
maybe
five
I
probably
spent
like
10
percent
of
every
day,
working
with
source
control
management
and
the
way
to
think
about
it
is
like
there's
a
bunch
of
tools
that
every
sort
of
craft
person
needs
right.
So,
if
you're
a
plumber,
then
you
need
a
plunger.
A
You
need
probably
a
wrench,
and
those
are
just
tools
that
you
use
every
single
day
for
your
job.
For
software
engineering,
you
need
sem
it's
not
like
one
of
those
things
where
it's
like
it's
nice
to
have.
You
basically
spend
maybe
10
to
20
of
your
entire
day,
working
with
it,
and
it's
one
of
the
fundamental
tools
that
you
use.
A
So
scm
is
a
tool
that
we
use
for
storing
these
text
files
and
the
way
to
think
about
it
is
that
get
lab
is
maybe
10
000
different
text
files
and
in
every
version
of
git
lab,
there's,
probably
something
like
two
to
three
thousand
different
people
who
edit
this
text
file
this
same
set
of
text
files.
So
just
think
about
the
complexity
there
right
so
obviously
there's
a
lot
of
different
things
that
happen.
A
A
But
that's
a
good
thing
from
a
business
perspective,
because
we
have
engineers
that
are
volunteering
their
time
to
improve
our
product.
So,
as
opposed
to
us
having
to
pay
the
engineer,
we
get
that
value
for
free
right.
So
that's
some
of
the
benefit
of
having
an
open
source
project,
but
the
downside
and
the
complexity
is
that
you
just
need
to
manage
all
these
outside
contributions.
A
So
if
I'm
on
a
gitlab
engineering,
team
and
other
people
that
I
know
are
making
changes-
and
I
trust
their
stuff.
But
what
if
I
get
like
you
know
a
change
request
from
someone
from
some
country
that
I've
never
heard
of
before
literally
anyone
can
add
in
merge
requests
to
gitlab
and
there
needs
to
be
some
sort
of
gate
for
the
quality
of
the
stuff
that
gets
in.
A
So
one
thing
that
you
could
imagine
is
that
in
an
open
source
project
a
lot
of
times,
it
becomes
very
political
right,
so
our
competitors
could
try
to
basically
create
in
merge
requests
to
make
our
product.
Worse,
if
they
were
trying
to
do
that,
that
has
happened
before
in
open
source
technologies,
but
there
needs
to
be
some
way
of
like
vetting
all
of
the
edits
that
are
coming
in.
A
So
that's
another
thing
that
sem
does
so
just
to
summarize
there's
a
lot
of
complexity
in
managing
this
code,
because
literally
gitlab
is
10,
000
text
files
and
we
have
maybe
3
000
different
people
trying
to
edit
it.
So
you
just
need
some
sort
of
tool
to
manage
that
entire
process.
A
So
what
are
some
of
the
things
that
it
does?
It
gives
a
history
of
the
changes
made
just
so
that
otherwise
it'd
be
super
chaotic
and
the
other
problem
is
trying
to
solve
is
to
allow
a
distributed
team.
So
like
people
in
europe,
africa,
asia,
united
states
to
work
on
the
same
text,
files
right
git
is
the
most
popular
tool.
As
you
can
see
in
the
bottom
right,
the
entire
market
has
consolidated
on
git,
so
right
now
they
have
around
90
market
share.
A
And
what
we're
going
to
see
is
that
this
consolidation
is
going
to
continue
because
gets
basically
the
best
solution.
One
thing
to
keep
in
mind,
though,
is
that
git
is
free
and
open
source.
It's
existed
for
about
15
years,
and
so
how
people
make
money
off
of
free,
open
source
software
is
that
they
add
on
additional
features
onto
it
and
then
so,
that's
fundamentally
what
github
and
gitlab
do
is
that
gets
the
engine
and
then
they
build
on
additional
functionality
on
it
and
that's
what
we
sell.
A
So
I
think
that
we've
all
done
this
before,
where
you
had
to
study
we
had
to
like,
create
a
essay
or
something-
and
you
know
you
had
version
one
then
version
two
then
version
three
and
then
sometimes
you
try
to
put
comments
in
right.
So,
like
version
11
with
edits
version
15.,
I
finally
proofread
it.
Then
I
you
know
like
formatted
everything
version
16
and
then
you
have
like
final
and
then
you
actually
had
to
make
a
change
afterwards.
Then
you
have
actual
final.
A
So
this
is
something
that
get
lab
does
for
you
as
opposed
to.
This
is
a
big
problem
right
because
now
I
have
20
different
files
for
this
one
file
and
we
talked
about
how
gitlab
may
be
10
000
files.
If
we
did
this
for
every
single
file
in
our
repository,
then
this
becomes
unmanageable
right
problem
number
two
is
imagine
a
school
project
right,
so
let's
just
say
that
we're
working
on
the
same
school
project,
I
have
to
write
the
introduction,
and
then
you
know
the
the
first
one.
A
Third
alyssa
has
to
write
the
next
third
and
then
so
on
and
so
forth.
We
have
to
tie
everything
together
at
the
end
and
then
it's
always
like
this
simple
idea
right.
So
the
idea
is
we'll
just
all
write
our
independent
chunk
copy
and
paste
everything
in
the
same
document,
and
then
it
will
be
easy,
but
it's
never
that
simple
right.
A
So
what
ends
up
happening
is
that,
let's
just
say
that
one
person
changes
the
font
to
font
10
and
everyone
else
is
at
12
right
and
then
what,
if,
like,
I
ended
up
writing
part
of
letha's
section.
Well,
then,
you
know
like
that
becomes
not
intuitive
either.
So
the
whole
merging
process
creates
a
lot
of
complexity.
A
Obviously
this
isn't
that
creative
example
with
three
people,
but
imagine
if,
like
20,
people
are
trying
to
edit
the
same
file
when
we
have
a
large
software
project
like
git
lab
where
3
000
people
are
editing
it
every
month,
then
it's
entirely
possible
that,
like
five
ten
twenty
different
people
are
trying
to
edit
the
same
text
file.
So
there
can
be
huge
like
conflicts
when,
like
you
know,
so
many
people
are
trying
to
edit
the
exact
same
file.
A
So
let
me
just
show
you
how
all
this
stuff
works.
So
this
is
gitlab
right
and
we
already
saw
how
gitlab
is
just
a
fundamental
set
of
text
files
and
let's
talk
about
the
actual
version
control
so
over
here
is
the
commit
section,
and
you
can
see
that
this
is
all
of
the
past
versions
of
our
code.
So
just
like
how
that
one
essay
I
had
it
was
like
version,
one
version,
two
version,
20
version
20
with
final,
whatever
here's
all
of
the
different
versions
of
our
file,
so
of
of
our
project.
A
In
other
words,
in
the
last
hour,
there
was
literally
nine
updates
to
our
project
and,
if
we're
to
go
into
any
of
these
individual
changes,
we
can
see
that
this
is
the
change
right.
So
they
took
out
this
red
text
they
added
in
the
screen
test,
and
this
was
the
entire
change.
There
also
needs
to
be
an
explanation
of
why
this
change
was
made
just
because
like
if
you
just
think
about
it,
it's
like
I'm
an
engineer
we
find
out
that
something
broke.
A
We
want
to
go
back
to
the
change
that
actually
introduced
this
problem,
and
if
that
you
know
like
it's
very
possible
that
the
person
who
worked
on
this
may
no
longer
be
on
our
team
or
like
if
it
happened
two
years
ago,
then
without
like
this
context,
we
don't
really
understand
what
this
change
is
about.
So
that's
another
thing
that
we
give.
You
is
the
ability
to
create
context
for
why
this
change
happened
and
then
another
thing
that
we
do
is
so
that
was
the
entire
project
level
of
view.
A
So
if
anyone
makes
any
changes
in
any
of
these
files,
it
shows
up
in
this
history
log,
but
we
also
have
you
know.
Every
single
individual
file
has
its
own
history
log.
This
is
a
pip
file.
If
I
go
the
history
of
this
file,
then
we
can
see
the
changes
that
happened
here
and
there's
only
two
changes
right.
A
So
when
we're
talking
about
source
control
management,
then
we're
really
talking
about
the
management
of
these
text
files
and
how
we
allow
different
people
to
work
on
it.
So
we
just
talked
about
like
how
we
give
history.
Merge
requests
are
how
we
allow
a
lot
of
different
people
to
work
at
the
same
set
of
text
files.
We
talked
about
how
there
needs
to
be
some
sort
of
gate
right
without
the
gate,
then
you
know
our
competitors
can
come
in
and
destroy
our
product.
A
You
can't
just
have
it
so
that,
like
anyone
can
edit
the
text
files
and
so
that's
why
people
have
to
create
emerge
requests,
and
so
what
a
merge
request
is
is
people
are
have
to
defend
their
change
and
then
their
change
has
to
get
approved.
So
over
here
is
someone.
What
they're
trying
to
do
is
implement
some
sort
of
standard
where
you
can't
create
this
thing
in
gitlab,
that's
longer
than
80
63
characters.
A
So
if
I
wanted
to
name
this
thing
like
big
fluffy
dog
went
to
paris
and
then
went
to
france
and
it's
that
title
is
longer
than
63
characters,
then
this
change
would
make
it
rejected
right.
So
over
here's,
the
changes
and
how
we
allow
for
contributions
from
all
these
different
people
and
create
this
gate
is
that
over
here
are
the
changes
and
then
other
people
have
the
ability
now
to
challenge
this
person
about
why
they
made
these
changes
right
and
so
different
people
can
say,
like
hey,
did
you
do
this
the
best
possible
way?
A
A
Let's
talk
about
the
workflow,
it's
important
to
understand
how
this
works
at
like
a
high
level,
I'm
not
going
to
get
super
granular,
and
this
is
an
engineering
class
right,
but
the
whole
idea
is
that
there's
a
master
branch
and
what
the
master
branch
is
is
it's
that
it's
the
universal
and
best
version
of
our
code,
and
so
whatever
is
currently
running,
that's
considered
the
master
branch.
So
now,
let's
just
say,
I'm
I'm
some
developer,
I'm
starting
to
work
on
my
new
thing.
A
My
boss
asked
me
to
make
a
new
button
or
a
chart
or
something
so
what
I
actually
do
is
the
first
thing
that
I
do
is
once
again.
Gitlab
is
a
set
of
maybe
10
000
text
files.
I
create
what
I
call
a
new
branch
and
the
whole
idea
of
branching
is
I'm
going
to
copy
and
paste
that
set
of
10
000
text
files
from
the
master
branch
onto
my
local
machine?
So,
right
now,
when
I
created
this
branch,
these
two
sets
of
code
contexts
are
absolutely
identical.
A
It's
literally
just
copied
and
pasted
all
those
10
000
files.
Now
I'm
going
to
start
to
implement
this
like
new
button
or
chart
or
something
so
I'm
going
to
start
coding.
Every
time
I
hit
save
that's
what
we
call
commit,
so
I
make
some
incremental
progress
hit
save
this
is
one
commit.
Then
I
make
more
progress
hit
save
again.
A
Finally,
I
have
three
saves
and
then
my
charts
done
right
and
I've
solved
my
issue
so
now
what
I
want
to
do
is
I
want
to
get
all
of
my
changes,
which
I'm
very
proud
of
back
into
the
master
branch
and
then
that's
ultimately
how
I
get
credit
as
an
engineer.
So
what
I
do
is
I
finally
create
this
merge
request.
The
merge
request
is
needs
to
get
approved,
but
once
it's
approved
and
merged,
then
these
three
saves
are
going
to
be
reflected
in
the
master
branch
and
I'm
done.
B
Quick
question
chris,
so
when
you
said
that
when
we,
you
know
the
blue
dots
in
there
like
your
work,
you
said
that
when
we
save
something,
it's
it's
called
commit,
and
I
also
often
heard
of
something
called
push
like
so
commit
and
push
so
are
those
like
two
different
things
or
yeah.
So
how
does
how
does
push
work.
A
Yeah,
that's
a
really
great
question,
so
every
time
you
hit
save
that's
a
commit,
you
can
literally
think
save
equals
commit,
but
the
idea
of
pushing
all
of
these
saves
what
that
is,
is
like
I've
made.
All
of
these
saves
on
my
local
version
of
my
files,
but
now,
let's
just
say
I
want
these
saves
to
be
reflected
in
like
the
gitlab
server
or
something
like
that.
So
I
I
know
that
like
this
is
this
is
this
is
a
truthful
answer.
A
A
So
the
master
branch
and
all
of
these
files
are
in
a
google
data
center.
When
I
start
my
own
work,
I'm
creating
what
we
call
a
local
branch,
and
so
I
copy
and
paste
all
these
files
onto
my
computer,
and
now
these
files
are
existing
locally,
as
opposed
to
in
the
cloud
service,
and
eventually
I
need
this
branch
back
on
the
cloud
server
for
comparison
purposes,
and
so
that's
the
idea
of
pushing
my
changes
back
into
the
cloud
service.
So
pushing
basically
means
are
just
a
like
sort
of
go
from
the
beginning.
A
Master
branch
is
basically
what's
currently
running.
I
want
to
edit
this.
I
can't
edit
the
master
branch,
because,
if
I
screw
it
up,
then
gitlab
goes
down.
So
what
I
do
is
I
create
my
own
copy.
My
own
copy
exists
on
my
mac
and
every
time
I
hit
save
and
make
you
know
some
incremental
progress.
That's
a
commit,
and
now
that
I
have
this
code
updated
on
my
macbook.
A
Then,
if
people
want
to
see
it-
and
you
know,
compare
it
to
decide
if
they
like
it,
then
they
need
to
have
a
version
back
in
the
cloud
service
so
that
the
cloud
service
can
compare
the
master
branch
to
whatever
I've
been
working.
On
right,
they
can't
just
compare
it
with
whatever
is
in
my
macbook,
because
it
doesn't
know
about
what's
in
my
macbook,
so
the
idea
is
I'm
going
to
push
this
entire
branch
into
the
gitlab
server
and
then
the
gitlab
server
is
then
going
to
compare
these
two
branches.
A
B
Yeah
yeah,
that
that
explains
thanks
so
like
it's
the
same
in
sas
and
self-managed
right,
whereas
in
self-managed
like
maybe
my
own
work
will
be,
you
know,
copied
and
copied
and
pasted
from
the
company
server
to
my
own
laptop
and
then,
when
I
push
it
it
was.
It
will
be
like
pushed
back
to
the
company
server.
A
All
right,
thanks
for
asking
that
all
right,
so
let's
just
go
through
everything
again
my
manager,
so
so
from
start
to
finish,
how
I
get
credit
as
an
engineer
is
I
solve
a
lot
of
issues
if
I
solve
a
ton
of
issues
and
I
get
a
promotion,
and
so
each
issue
is
like
you
know,
create
a
button.
Go
fix.
This
thing
do
this
whatever,
and
so
how
I
want
to
solve
these
issues,
and
I
need
to
make
changes
to
my
code
right
so
in
git
lab
and
for
all
scm
tools.
A
How
that
works.
Is
that
there's
one
universal
master
branch?
This
is
what's
currently
running.
This
needs
to
be
protected,
because
if
anyone
just
writes
to
it,
then
it
destroys
our
product
right
and
gitlab
goes
down.
So
all
of
this
stuff
over
here
is
the
master
branch
I
got
to
somehow
like
implement
changes,
and
so
what
I
do
is
I
copy
all
of
these
files
from
the
gitlab
server
onto
my
local
machine
and
I
actually
edit
those
files
that
exist
on
my
mac.
A
I'm
not
editing
these
files
because
these
files
need
to
be
protected
after
I
make
saves
on
these
local
version
of
my
files,
so
like
add
in
text
whatever,
then
I
need
to
get
them
back
in.
Obviously,
there
needs
to
be
a
gate,
otherwise
people
just
destroy
our
product.
People
try
to
do
that
in
open
source
projects,
and
so
what
they
do.
A
What
I
do
is
I
push
the
code
back
into
gitlab
and
then
I
need
to
create
a
merge
request,
and
so
what
the
merge
request
is
is
it's
basically,
I
am
proposing
to
gitlab
that
they
should
accept
my
changes
because
of
this
reasoning
that
I
give
they
don't
have
to
accept
my
merge
request.
A
lot
of
merge
requests,
get
rejected
from
open
source
projects,
and
so
here's
the
change
that
I'm
trying
to
make
once
again.
A
Literally
all
this
engineer
did
is
change
some
text
files,
that's
what
they
get
paid
to
do,
which
is
kind
of
really
weird
to
think
about.
But
if
enough
people
approve
this,
then
so
you
can
see
this
says
requires
approval
right.
This
is
the
gate.
Not
everyone
can
accept
stuff
into
gitlab,
but
if
enough
people
approve
it,
then
it
will
get
merged
and
then
once
it
gets
merged,
then
gitlab
will
get
updated.
So
that's
how
sem
does
it
from
start
to
finish.
A
All
right,
so
I'm
gonna
skip
that
exercise.
I
hope
that
there's
time
at
the
end
for
us
to
do
it,
but
I
think
that
it'll
be
really
good
for
us
to
do.
A
So
let
me
talk
about
what
that
actually
means.
It's
a
lot
of
like
technical
mumbo-jumbo
right
and
don't
get
intimidated
by
this
server
diagram.
So
what
I
mean
by
high
availability?
Is
that
all
right?
So
the
idea
is
like
this:
if
you
have
netflix
or
amazon
or
google,
if
your
web
service
goes
down,
then
you
lose
millions
of
dollars
every
second
that
it
goes
down.
Your
web
service
can
never
go
down
right
and
so
engineers
what
they
do,
is
they
figure
out
these
systems
so
that,
like?
A
If
my
data
center
sets
on
fire,
then
the
web
service
is
still
up
and
how
they
do.
That
is,
they
make
their
web
service
have
high
availability.
This
is
what
their
term
means.
So,
just
to
recap,
we
want
highly
available
services
so
that
my
services
always
up,
which
is
important,
so
my
e-business
continues
to
make
money.
A
A
So
the
way
to
make
this
highly
available
is,
let's
have
50
of
these
servers
right,
and
so,
if
this
one
dies,
then
I
still
have
this
one,
and
so
that's
why
you
want
a
group
or
cluster
of
these
servers,
so
just
to
recap,
high
availability
is
good
for
my
business.
It
makes
it
so
that
people
continue
to
access
my
website
in
case
there's.
Problems
in
engineering
problems
happen
all
the
time
right.
A
Even
major
players
like
amazon,
they
have
problems
that
shut
down
their
web
servers
from
time
to
time.
So
it's
really
really
really
important
to
have
a
highly
available
web
service.
How
we
actually
do
this
from
an
engineering
point
of
view
is
we
have
lots
and
lots
of
servers
and
we
make
it
so
that
if
a
bunch
of
them
die,
then
there
are
still
other
ones
that
can
take
on
the
load,
and
so
that
is
a
highly
available
web
service
with
advanced
clustering.
A
So
that
is
our
main
differentiator
in
terms
of
in
terms
of
sem,
and
it
is
the
one
the
huge
ways
in
which
we
win
over
github
and
like.
Let
me
sort
of
explain
why
right
so
we
have
two
ways
of
deploying
gitlab
one
is
self-hosted
and
the
other
one
is
sas.
If
you
are
a
defense
contractor
working
for
the
government,
you
get
billion
dollar
missile
contracts,
then
it's
extremely
extremely
extremely
important
for
you
to
make
sure
that
whatever
you're
building
is
safe
right.
A
So
it's
just
sort
of
like
you
have
all
these
people
that
are
trying
to
hack
your
servers.
Take
all
of
your
stuff
literally
a
lot
of
the
united
states.
Military
projects
have
already
been
hacked
and,
like
so
just
think
about
this.
From
a
society
point
of
view,
united
states
spends
20
billion
dollars
in
this
project
and
then
some
other
country
comes
in
and
takes
all
that
stuff.
Then
that's
really
bad
for
the
united
states
right,
not
trying
to
get
political
but
like
it's
just
understanding
that
why
we
get
some
of
these
contracts.
A
So
for
a
lot
of
like
these,
like
government
agencies,
they
do
not
buy
the
sas,
they
can't
buy
the
sas
because
it's
not
secure
enough
because
they
need
to
control
themselves,
and
so
what
these
government
agencies
do
is
they
have
all
of
these
servers
in
some
sort
of
underground
bunker,
they're
not
connected
to
the
internet,
and
they
have
all
of
these
like
levels
of
security.
Why?
A
Because
the
code
that's
like
on
these
servers
is
worth
billions
of
dollars
right,
so
we
don't
trust,
get
lab
servers
we
need
to
have
our
own,
and
so
in
that
market
gitlab
is
really
really
good.
We
are
way
better
than
any
other
person
any
other
company
in
the
market
right
now.
So
that's
one
of
the
huge
differentiators
that
we
have
in
terms
of
sem.
B
Can
we
like
go
back
a
bit
about
the
load,
balancer
thing
so
like
we
know
about
high
availability,
but
not
so
much
about
load,
balancer
and
and
my
internet?
It
was
kind
of
started
earlier,
so
I
didn't
hear
much
about
load
balancer,
so.
A
Yeah
for
sure
all
right
ariana
is
this:
can
I
help
clarify
anything
for
too.
C
I
mean
it's
kind
of
clear,
then,
with
the
questions
you
know
with
the
homework.
I
guess
it
becomes
clearer
for
me,
like
I
listen
to
it
again
and
I
try
to
answer
the
question
so
like
on
the
first
shot.
For
me,
it's
always
like
a
bit
blurry.
Then
I
check
the
questions.
I
really
listen
to
it
and
then
you
know
I
it
becomes
clearer.
I
don't
know
it
was
like
this
for
me,
but
for
now
everything
has
a
sense.
Let's
say
this.
A
Yeah
for
sure,
so,
okay,
let
me
just
recap
this
real
quick,
our
main
differentiator
for
scm,
and
one
of
the
big
ways
in
which
we
went
over
github
is
that
we
have
high
availability,
which
is
really
good,
and
this
especially
matters
for
the
self-hosted
market.
Once
again,
we
have
a
sas
and
then
we
have
self-hosted,
and
so
the
reason
why
this
is
really
good
is
because,
if
I'm
a
government
agency,
I
don't
trust
to
get
lab
servers.
I
need
to
go.
A
Have
the
code
in
my
own
servers
and
I'm
gonna
put
these
in
servers
or
in
some
sort
of
underground
secret
chamber
right
because,
like
that's,
and
this
is
required
for
the
ability
to
do
this
is
required
for
some
sort
of
contractor
to
win
a
deal
with
me.
If
they
want
my
business,
they
have
to
be
able
to
do
this,
and
this
is
why
we
win
a
bunch
of
government
contracts.
A
So
what
high
availability
is?
This
is
just
sort
of
like
the
idea
that
I
gotta
have
whatever
my
website
running
at
all
times.
I
have
a
bunch
of
servers
that
are
running
this
website
and
this.
If
one
data
center
sits
on
fire
explodes
then
my
website,
my
web
service
should
be
unaffected
and
so
over.
Here
I
have
how
you
actually
do
this.
Is
you
create
a
cluster
of
servers
with
a
load
balancer,
and
so
the
whole
idea?
A
Is
that,
like
what
a
load
balancer
does
at
a
really
high
level,
is
you
have
all
these
people
are
trying
to
access
my
website?
So
you
know,
if
I
go
to
google,
then
what
the
load
balancer
does
is
that
it
says.
Okay,
this
server
take
the
first
job.
Then
this
server
take
the
second
job.
Then
this
server
take
the
third
job.
Then
this
server
take
the
force
job,
so
it
basically
distributes
all
the
work
among
the
servers
that
you
have
and
then
so
that's
a
important
ingredient
of
a
cluster
and
the
whole
idea
is
high.
A
Availability
is
if
this
server
dies,
then
I
still
have
additional
servers
that
are
ready
to
work,
and
so
that's
how
I
implement
high
availability
through
a
cluster
with
all
this
other
stuff.
The
whole
point
is
that,
like
just
to
recap,
government
contract,
are
you
know,
like
advanced
security
protocols
in
general
will
require
high
availability.
A
So
if
we
hear
like
that,
people
are
interested
in
self-hosted,
you
can
ask
them
why
if
they
say
we
have
all
these
security
stipulations
then
tell
them
about
all
the
great
high
availability
stuff
that
we
have
we're
the
best
at
this.
If
you
just
say
literally
great,
I
understand
that
you
want
to
self-hosted
because
of
all
your
security
compliance
protocols
we're
the
best
at
this.
Let
me
tell
you
why,
then
we
instantly
have
demonstrated
something
that
a
product
can
do
that.
A
No
one
else
can
do,
and
then
it
dramatically
increases
your
chance
of
getting
an
sao.
So
definitely
keep
this
in
mind.
Okay,
so
other
things
that
we
do
advanced
merge
request
approvals.
So
this
is
something
that
github
doesn't
do
and
it's
something
that
I
really
like.
The
whole
idea
is
that,
like
we
showed
that
like,
if
you
want
to
get
your
merge
request
approved,
then
you
need
a
bunch.
You
can
make
rules,
so
what
you
can
do
with
git
lab
that
you
can't
do
with
github.
A
Is
be
able
to
say
all
right,
I
need
one
person
from
the
test
team
to
approve
it,
two
people
from
the
security
team
to
prove
it,
and
if
it
changes
this
really
really
important
file,
then
I
need
a
directory
level
or
bob
to
prove
it
right.
Github
cannot
do
this
right
now,
but
we
can
make
this
really
granular.
So
that's
really
cool
and
in
general,
that's
our
differentiators
all
right
great,
so
project
management.
A
B
A
A
Okay,
cool:
let's
talk
about
project
management,
so
when
we're
talking
about
plan,
this
is
what
we're
talking
about
plan
from
a
gitlab
perspective
that
product
feature
set.
So
it's
like
you
know
this
is
create,
and
plan
plan
is
project
management.
A
So
let's
talk
about
why
this
is
important:
we're
planning
a
huge
wedding,
there's
string
of
people
coming
to
our
wedding.
This
is
obviously
a
huge
organizational
challenge
right.
So
there's
a
lot
of
different
things
that
we
got
to
do.
We
have
to
come
up
with
all
these
lists
of
things
to
do,
then
we
have
to
assign
who
you
know
who's
going
to
be
doing
what,
like
my
weddings
planners,
can
be
doing
this.
A
I'm
going
to
be
doing
this,
but
you
know
my
fiancees
can
be
doing
this
whatever
so
and
so
forth,
and
then
you
have
to
have
progress
on
each
item
right.
So
it's
just
sort
of
like
one
way
that
you
could
do
it
is
that
you
can
have
conversations,
but
what
happens
if
there's
five
people
working
on
your
team
right,
so
you
have
three
wedding
planners.
Your
two
parents
are
involved
and
then
it's
you
and
your
spouse
right.
Your
partner
and
then
so
it's
just
sort
of
like
do.
A
I
have
individual
conversations
with
all
four
people.
That
seems
like
a
lot
of
work
right
and
then
the
other
thing
is
which
items
need
to
be
done
in
a
certain
order
right,
so
for
my
wedding
planning,
I
can't
send
out
the
invitation
list
two
days
before
the
wedding.
I
need
to
send
it
out
in
the
beginning
right.
Certain
things
need
to
be
done
in
a
certain
order
and
then
there's
ways
in
which
organizations
can
optimize
this
flow
of
work.
So
what
project
management
does
is
it
takes
care
of
all
of
this?
A
The
whole
idea
is,
you
have
really
complicated
projects
and
from
a
workflow
perspective,
how
can
you
create
a
tool
that
makes
this
digestible
and
make
sure
that
all
of
these
things
are
being
taken
care
of?
So
every
engineering
organization
uses
project
management,
wedding
planners
use,
project
management,
any
sort
of
like
if
you're
throwing
a
big
party,
you
can
use
project
management.
It's
really
really
really
big
tool.
There's
billions
of
dollars
in
this
industry
jira,
I'm
sure
that
you've
heard
about
them
before
they
have
literally
billions
of
they're.
A
Really
really
expensive
software
company
and
all
they
do,
for
the
most
part
is
project
management.
So
it's
a
really
big
deal
and
software
development.
Everyone
uses
project
management
and
I
was
probably
spent
like
maybe
10
percent
of
my
entire
day
in
project
management
tools.
When
I
was
a
developer.
So
let's
talk
about
setting
goals.
I
know
that
that's
kind
of
abstract,
but
it's
important
to
understand
why
we
do
what
we
do,
but,
like
here's
an
example
of
a
bad
goal,
a
bad
goal
is
like.
I
want
to
lose
weight
which
is
or
like.
A
I
want
to
become
more
intelligent
right.
It's
just
sort
of
like.
I
understand
that
you
want
to
do
that,
but
like
what
a
better
goal
is
that,
like
hey,
I
want
to
lose
two
pounds
in
two
weeks:
hey.
I
want
to
go
sign
up
for
a
gym
at
the
end
of
this
week,
so
why
is
this
better
one?
It's
specific
right,
I'm
actually
giving
some
sort
of
behavior
that
I'm
measuring,
as
opposed
to
like
hey.
I
want
to
become
more
intelligent
like
how
do
you?
How
do
you
even
like
that's,
not
specific
right?
A
Better
goals
are
measurable
right,
so
it's
like.
I
want
to
lose
two
pounds,
that's
way
better
than
like.
I
want
to
lose
weight
because
I
can
actually
evaluate,
if
I'm
moving
closer
to
my
goals
or
not,
it
needs
to
be
achievable.
So
if
my
goal
is,
I
want
to
become
like
an
olympian
athlete,
that's
not
as
good
as
like
hey.
I
want
to
lose
like
two
pounds
in
the
next
two
weeks
and
then
it
needs
to
be
time
bound
right.
So,
if
my
goal
is,
I
want
to
lose
weight.
A
Well
then,
by
when
right,
if
so
like
great
organizational
leaders,
they
implement
things
like
this
in
their
organization,
and
they
really
think
about
like
how
can
we
have
discrete
goals
and
create
accountability
so
that
my
organization
moves
forward?
The
difference
between
like
a
new
leader
and
like
a
leader,
who's
really
advanced,
is
that
they
are
really
good
at
implementing
things
like
this
and
creating
accountability.
A
So,
let's
talk
about
how
this
works
for
software
development,
each
individual
unit
of
work
is
an
issue.
We
already
understand
that,
and
we
group
them
together
and
milestones
and
epics,
and
one
of
the
things
I'm
going
to
say
is
that
like
gitlab
is
great,
because
all
of
these
things
over
here
are
literally
features
that
we've
built
into
gitlab.
So
we
make
our
goals
our
issues
like
specific.
We
make
them
time-bound,
and
then
this
is
one
of
the
reasons
why
gitlab
plan
functionality
is
really
really
really
good
and
I'll.
A
Show
you
how
we
implement
smart
goals
with
gitlab,
so
you
can
group
together
as
milestones
in
epics,
and
what
are
the
benefits
right
like
we
got
to
talk
about
what
sort
of
organizational
benefit?
How
do
we
help
out
our
customers
right,
so
issues
allow
for
public
collaboration.
We
already
saw
that
they
provide
history.
A
Works
actually,
I
already
have
it
up.
So
here's
the
issues
list,
let's
scroll
into
this
one,
and
so
this
is
like
a
unit
of
work
for
an
engineer.
If
an
energy
near
does
this,
then
they
get
credit.
If
they
do
a
bunch
of
these
fast,
they
might
get
a
promotion
right
literally
like
all
the
engineers
in
general
are
ranked,
and
so
it's
just
sort
of
like
if
I'm
doing
50
issues
and
then
other
people
are
doing
like
10.
A
Well,
then
my
manager
is
going
to
see
that
and
they're
going
to
that's
going
to
be
part
of
why
someone
gets
promoted
and
why
someone
doesn't
get
promoted.
So
here's
the
issue
and
let's
talk
about
smart
goals
right
so
time
tracking.
A
This
is
as
engineers
put
in
the
amount
of
time
that
they're
spending
on
this,
then
that's
how
we
keep
track
of
it
and
then
so.
This
helps
out
a
manager
because,
like
if
someone's
not
spending
any
time
on
it,
then
I
know
like
hey,
that's
a
problem
right.
Another
thing
is:
if
an
engineer
is
spending
way
too
much
time
on
it,
it
means
that
they're
probably
stuck,
and
maybe
they
need
help
right,
so
the
manager
can
come
in
see
what
sort
of
bottlenecks
I
have
in
my
organization
through
time,
tracking
other
things
is
due
date.
A
This
is
how
you
make
it
your
goals.
Time
specific.
We
talked
about
that
with
smart
goals
so
as
opposed
to
just
having
you
know
like
before.
Like
all
of
these
project
management
solutions,
then
you
just
say:
like
hey
rachel,
you
need
to
do
this,
hey
bob.
You
need
to
do
this,
but
like
now
that
everything
is
super
visible.
You
can't
argue
with
it.
You
can't
say
that
your
due
date's
forgotten,
because
when
I
was
a
manager-
and
I
created
this
issue-
I
created
a
due
date
right,
so
there's
discrete
accountability.
A
Now
other
things
are
important,
assignee
right,
so
that's
really
important
to
know
who's
working
on
it
so
on
and
so
forth.
But
the
issue
is
created.
This
is
what
they
need
to
do.
They
need
to
go.
Do
something
for
integration
tests
all
right,
great
and
then
now
people
can
collaborate
on
this,
and
so
let's
talk
about
this
wedding
example.
A
So
our
let's
just
talk
about
like
yeah.
This
wedding
example,
one
of
the
things
that
I
said
is
there
could
be
five
people
on
your
wedding
team
right.
So
you
and
your
partner,
your
parents,
your
wedding,
planner
and
then
like
your
maid
of
honor
right
and
one
of
the
organizational
challenges
that
you
have
is
like.
Let's
just
say
that
you
found
a
great
venue
and
what
you
can
do
is
you
now
need
to
communicate
that
to
four
people
right?
A
So
if
you
had
one-on-one
conversations
with
four
people,
then
that
takes
you
10
minutes
times
four
people
which
is
40
minutes.
If
you
create
an
issue
and
then
you
just
say
like
hey,
you
know
like
hey,
hey
everyone,
and
then
you
list
all
their
names
like
this
person,
this
person
and
then
the
four
people
on
your
wedding
planning
team
and
then
I
I
found
a
great
venue.
A
It
is
here.
I
like
it
because
a
b
and
c
all
of
a
sudden
I've
communicated
it
with
my
entire
team,
which
saves
me
time
and
then
also,
let's
just
say
that,
like
I
find
out
that
a
new
person
wants
to
come
on
right
and
then
help
out
with
my
wedding
planning,
then
all
I
have
to
do
is
I
have
a
history
of
all
this
stuff.
That's
been
going
on
in
my
decision
making
process
for
my
wedding.
They
can
just
go
in
the
issue
and
then
read
why
we
made
this
decision.
A
Otherwise,
if
someone
I
put
someone
new
on
my
wedding
team,
then
I
have
to
have
a
conversation
with
them.
I
pick
this
venue
at
this
date
because
of
this,
and
instead,
if
I
got
a
new
wedding
planner,
then
I
could
be
like
hey.
Take
a
look
at
all
of
these
issues
that
have
to
do
with
our
venue
and
our
catering.
A
It
has
all
the
history
there
can
you
do
x,
y
and
z,
and
then
they
can
just
read
the
history
and
then
understand
what
still
needs
to
be
done,
as
opposed
to
like
all
that
stuff
being
forgotten
right,
so
yeah,
the
history
is
really
important,
a
lot
of
times
developers.
A
There
is
some
change
that
was
made
by
someone
who
doesn't
work
for
the
company
anymore,
and
then
the
decision
was
made
two
years
ago.
So
by
having
all
of
your
issues
and
all
of
this
history,
it's
really
important
because
now
there's
a
discreet
way
of
us
understanding
why
we
made
certain
changes
the
product
like
two
years
ago
right
so
they
go
back
and
forth
they
collaborate.
All
this
collaboration
makes
us
have
a
better
product.
A
Gitlab
is
really
really
good
at
collaboration,
because
it's
one
tool
for
the
entire
devops
life
cycle,
so
as
opposed
to
just
the
developers
collaborating
on
it.
You
can
have
the
security,
the
test,
devops
people
collaborating
on
it
and
all
of
this
collaboration
ultimately
makes
when
you
use
gitlab,
you
get
better
software
out
of
it.
This
is
something
that's
really
really
really
important.
It's
not
just
fluff.
When
I
was
an
engineer
like
if
we
had
this,
this
would
have
saved
us
time
all
right,
so
public
collaboration
is
really
important.
A
Anyone
can
come
in
and
see
it
as
opposed
to
having
five
different
conversations.
You
just
have
one
providing
history.
This
is
really
important.
If
you
know
someone
gets
fired
and
then
two
years
later,
the
person
who's
working
on
this
thing
doesn't
ex
isn't
in
the
organization
anymore.
We
can
just
go
in
the
system
and
see
why
what
he
was
thinking
about,
so
that
shared
history
is
really
important.
A
Accountability
with
due
dates,
that's
really
important,
give
management
a
sense
of
progress
and
optimally
sequence
work.
So,
let's
talk
about
this.
This
is
additional
things
that
we
have
in
gitlab.
Github
does
not
have
this,
but
one
of
the
things
that's
really
important
for
organizations
is
like
predicting
how
long
this
is
going
to
take.
If
you
think
about,
like
I'm
planning
my
wedding,
I
have
a
certain
amount
of
time
that
I
need
to
put
into
this.
My
wedding
date
is
already
communicated
with
200
people,
so
it's
like.
I
can't
change
that.
A
I
need
to
figure
out,
if
I'm
tracking,
to
like
get
this
done
on
time
or
not,
and
if
not,
I
need
to
go
figure
something
out
right.
So
it's
like,
I
need
some
sort
of
way
of
figuring
out
how
much
work's
left.
So
this
is
what
we
do
with
milestones
over
here.
You
can
see
this
project
started
with
662
issues
and,
as
people
start
doing
these
issues,
then
they
start
getting
closed
right
and
then
over
here
we're
about
50
done
over.
Here
we
can
say
like
all
right.
A
We
are
now
on
track
to
finish
our
project
in
august,
and
I
can
discreetly,
from
a
data-driven
manner,
understand
that
so
it's
like,
if
I
were
wedding
planning
with
this
and
we're
two
weeks
away
from
the
wedding
and
we're
still
up
here,
then
we
gotta
we
gotta,
go
push
our
wedding
date
back
right,
so
this
is
really
really
important
for
management.
It's
important
for
directors,
about
just
sort
of
like
one
great
question
to
ask
is
like
how
do
you
know
how
much
work
is
done
in
your
projects?
A
95
of
them
have
no
real
good
way
of
figuring
it
out,
and
so
milestones
is
a
really
important
thing
for
a
lot
of
people
over
here.
If
they
have
jira,
then
jira
does
have
this,
but
like
for
people
with
just
github
and
stuff,
they
don't
have
this
all
right.
So
now,
let's
talk
about
optimally,
sequencing
work
so
like
in
terms
of
our
project.
One
thing
that's
really
important
is
like.
I
can't
send
out
my
invitations
per
wedding.
A
At
my
end,
I
need
to
send
it
in
the
beginning,
there's
other
things
that
it
has
to
be
like
in
a
certain
order
right
and
then
other
things
is
just
sort
of
like
imagine.
You
have
like
five
people
on
your
team
right.
One
person
is
going
to
be
on
vacation
these
two
weeks
and
he's
the
only
person
who
knows
how
to
do
this
stuff.
A
A
The
roadmap
tells
you
who,
like
what
we're
working
on
when
and
the
whole
idea,
is
that,
like
all
right,
if
there's
too
much
stuff
all
in
the
beginning,
then
we
gotta
go
spread
all
this
work
out
more,
and
so
that's,
basically
what
the
road
map
view
does
so,
just
to
recap,
this
shows
you
all
the
different
projects
that
are
happening
in
my
organization
at
any
point
in
time,
and
so
a
project
manager
can
go
into
this
view
and
then
he's
going
to
think
about.
Like
man,
I
got
to
go
spread
all
this
stuff
out.
A
If
not
everyone's
going
to
be
super
stressed
out,
so
we
need
to
go
spread
this
out.
How
do
we
spread
this
out
in
a
way
that
makes
sense?
Well,
this
project's
the
most
important?
Let's
do
it
first,
these
projects
have
due
dates.
This
project
doesn't
matter
as
much,
so
we
can
just
put
it
in
here.
This
is
what
the
roadmap
view
does,
and
this
is
how
organizations
organize
their
work
better.
B
Okay,
cool,
so
so
for
the
burn
up
and
breakdown
chart.
Those
those
things
are
like
basically,
the
opposite
right,
so
so
burn
down.
Chart
shows
the
issues
that
are
closed
over
time
and
burn
up.
Chart
is
like
showing
the
issues
that
are
worked
over
time.
Is
that
correct.
A
B
C
So
the
burn
down
chart
shows
the
open
issues
and
no,
how
was
it.
D
A
So
one
of
the
things
that's
kind
of
confusing
to
me
is
that
this
burn
up
chart.
I
know
that
we
can
customize
our
stuff
in
gitlab,
which
is
why,
like
this
burn
up,
chart
is
like
so
I
actually
I'm
going
to
take
as
an
action
item
to
investigate
this
burn
up
chart,
because
I
think
that
we
may
have
it
configured
differently.
Traditionally
burn
up
charge
show
the
number
of
closed
issues,
but
what
this
graphic
is
showing
is
the
number
of
open
issues
which
is
confusing
to
me.
So
I'm
going
to
take.
A
All
right,
thanks
for
thanks
for
I'll,
get
back
to
you
all
about
that.
So
the
theme
of
all
of
this,
like
planned
stuff,
is
work
right.
So
for
some
massive
project
I
have
100
people
working
on
this
thing.
All
sorts
of
different
things
managers
need
to
understand
what's
happening,
they
need
to
like
plan
out
like
who's
doing.
What,
when
and
the
difference
between
doing
this
well
and
doing
it
really
well,
is
a
huge
difference
from
our
organization
right
and
that's
what
agile
planning
does
and
that's
what
our
plan
functionality
does
in
general.
A
The
reason
why
it
helps
out
organizations
is
that
we
allow
people
to
implement
smart
goals.
If
you
implement
smart
goals,
your
organization
is
going
to
win,
and
if
you
implement
smart
goals
in
your
own
life,
then
you'll
have
better
goals
in
general
too,
and
this
is
something
that
is
pretty
resilient.
So,
let's,
let's
talk
about
kanban
charts.
This
is
something
that
you
can
do
in
git
lab,
I'm
not
showing
git
lab,
I'm
actually
showing
one
of
our
competitors.
A
This
is
trello
our
competitor,
and
so
what
I
can
bam
chart
is
is
each
of
these
is
an
issue
and
the
whole
idea
is
like
the
campaign
started
with
factories
in
japan,
and
so
there
was-
and
it's
like
this
gigantic
conveyor
belt.
That
goes
down
right.
So
in
the
first
stage,
then
people
do
something
and
they
put
it
back
in
the
conveyor
belt.
Then
it
goes
to
the
second
thing
and
they
do
something
else
with
the
product
that
they're
working
on
and
then
at
the
end
of
the
conveyor
belt.
A
They
have
like
their
product,
that's
done
and
ready
to
sell
right.
So
what
a
cam
dam
chart
is
from
like
a
project
management
point
of
view,
is
you
have
a
bunch
of
columns
and
it
mimics
this
conveyor
belt.
So
in
the
beginning,
nothing's
happened
yet
and
at
the
end
things
are
done.
So
the
idea
is
that
here's
this
issue
it's
in
the
queue
that
hasn't
started
yet
then
someone's
going
to
want
to
start
it.
So
you
know
I
assign
myself
to
it,
I'm
going
to
start
it
and
then
so
the
first
column
is
like.
A
A
The
whole
idea
is
I'm
gonna
give
you
another
example.
We
have.
We
have
this.
We're
planning
a
wedding.
You
you
us
three
are
wedding
planners
right,
so
there's
300
things
that
we
need
to
do.
We
create
300
issues
for
everything
everything
from
like
what
tablecloth
are
we
using?
What
flowers
are
we
using?
A
Have
we
sent
out
guests
whatever
all
of
the
issues
start
out
in
the
queue
I
assign
aletha,
one
third
ariana,
you
get
another
third,
I
got
a
third
right
and
then
so
we
put
our
faces
on
it
and
then
we
start
doing
it
and
as
the
issues
go
from
left
to
right,
we
know
how
much
proj
how
much
work
is
left
in
our
project.
So
all
the
issues
start
out
here
and
then
once
they're,
all
in
the
done
column,
we're
done
and
a
project
manager
can
come
in
very
easily
see
all
right.
There's
a
bunch!
A
That's
doing
here,
but
a
bunch
of
it
is
being
worked
on.
That's
great
and
let's
just
say
that
out
of
300
issues,
200
earn
the
q
100
in
progress
zero
and
done
well
we're
in
the
beginning
phase.
Right
now.
Let's
say
we
have
300
issues.
All
of
them
are
out
of
here.
100
in
progress,
200
aren't
done.
Well,
then
we're
probably
close
to
being
done
right.
A
A
Yeah
was,
was
that
clear?
If
not,
let
me
know.
C
Yeah,
it
was
clear,
but
you
can
you
do
this
with
gitlab
like
the
in
the
same
way
or
trello
is
just
better
to
organize
or.
A
Yeah,
you
can
totally
do
this
with
git
lab
the
reason
why
so
like
here's
the
issue
and
you
can
create
an
issue
board
and
then
you
can
have
different
columns
like
not
started
yet
assigned
in
progress,
needs
checking
done
at
the
end,
which
is
your
closed
column.
So
you
can
create
a
board
and
then
your
port
can
be
like
a
cam
dam
chart.
So
that's
something
that
we
totally
support.
A
All
right,
so
what
are
the
benefits
right?
We
talked
about
public
collaboration
once
again
that
that
story
about
like
hey,
we
have
five
people
that
are
working
on
this
wedding.
If
we're
doing,
if
I'm
just
communicating
like
by
phone
to
everyone,
then
I
have
to
have
five
conversations.
If
I
have
one
online
tool
for
it,
then
I
can
just
like
at
here
everyone
for
it
right
and
then
they
can
contribute
provide
history.
So
let's
just
say
that
one
wedding
planner,
you
know
like
has
a
family
emergency
has
to
leave.
A
I
have
to
get
a
replacement
as
opposed
to
and
we're
like.
I
have
six
months
before
our
wedding,
so
it's
like.
If
I
got
this
new
wedding
planner,
then
I
got
to
now
have
like
a
four
hour
conversation
about
everything
that
we've
done
so
far,
because
without
a
project
management
tool
with
a
project
management
tool,
I
can
say:
hey.
We
use
gitlab
for
this.
A
Take
a
look
at
these
30
issues.
These
are
the
ones
you're
going
to
be
working
on.
All
of
the
collaboration
that
happened
back
and
forth
is
the
history
of
what
we've
decided
so
far,
and
then
so
I
don't
need.
I
save
myself
a
bunch
of
time
right
and
them
asking
me
a
ton
of
questions,
and
so
that's
how
all
of
that
collaboration
for
our
issues
right
over
here
like
they
can
come
in
and
then
realize
what
the
last
person
was
thinking
about.
A
Has
all
this
history,
as
opposed
to
them,
asking
me
a
million
questions
about
like
all
right.
I
know
that
you
wanted
this
like
flower
vendor
like
why
you
know
so
on
and
so
forth.
So
the
history
over
here
is
super
super
valuable,
provide
accountability,
track
progress.
We
do
that
with
milestones
due
dates,
gift
management,
sense
of
progress.
It's
milestones
helps
to
determine
how
to
optimally
sequence,
work.
We
do
that
with
road
maps.
A
So
what
are
differentiators
burn
down?
Charts
is
a
big
differentiator.
Last
time
I
checked,
github
does
not
have
burn
down
charts.
A
When
I
was
an
engineer
we
had
to
have
someone
spend
like
a
week
on
it
to
build
out
something,
and
it
wasn't
that
good
and
so
like,
like
a
week
of
engineering
time
which
is
worth
to
the
organization
like
a
several
like
two,
maybe
a
thousand
five
hundred
dollars
to
build
something
that
gitlab
has
you
don't
already
right
time,
tracking
road
maps
they're
all
important
and
that
some
of
that
some
of
our
differentiators
honestly,
these
are
the
three
that
we
should
talk
about
road
maps,
time
tracking
burn
down,
charts
all
right,
so
we
gotta
talk
about
our
competitors.
A
Competition
is
really
important
for
this.
We
saw
in
the
beginning
literally,
you
can
pull
up
a
list
of
40
of
the
best
project
management
tools,
but
not
all
of
these
40
competitors
are
equal.
Jira
is
like
by
far
the
biggest
competitor
in
software
management.
They
have
some.
They
have
over
50
percent
the
market,
like
literally
they
have
over
50
percent.
The
market
they've
been
super
successful.
I've
used
their
stuff
before.
A
I
honestly
think
that
our
stuff
is
better
in
a
lot
of
ways
than
jira,
but
it
doesn't
matter
because
they
have
a
lot
of
like
they
just
have
a
lot
of
traction
in
the
market
right.
Other
people
who
do
this
trello
we
saw
trello
github,
does
all
of
this
too
and
then
lesser
competitors.
You
know,
literally
all
of
the
other
30
people
on
that
list.
That
we
saw-
and
one
thing
that's
really
important-
is
that
a
lot
of
people
want
to
keep
their
project
management
tool.
A
So
in
gitlab's
history,
our
first
selling
proposition
was
replace
all
of
your
stuff.
You
can
replace
all
of
your
stuff
with
github
with
gitlab
that
saves
you
in
license
cost
and
what
people
realize
in
our
company
history.
Is
that
like
wait,
no
one
wants
to
replace
jira
and
then,
if
we
position
our
product
like
this,
we
actually
lose
sales.
So
maybe
we
should
stop
doing
that,
so
the
sales
motion
went
from
trying
to
replace
jira
to
how
do
we
integrate
with
things
like
jira?
Why
do
software
companies
not
want
to
move
off
jira?
A
So
if
they
were
to
move
on
to
gitlab,
then
that
now
all
of
a
sudden
they
have
some
of
this
history
in
jira
and
in
some
of
their
history
in
gitlab,
and
that's
really
confusing
for
companies
right,
and
so
it
just
makes
sense
to
have
like
one
tool
if
you
just
imagine
like
like,
if,
like
I
have
a
journal,
if
I
imagine,
if
I
had
two
journals
and
then
I
wrote
in
some
of
the
journals,
if
I
wrote
in
one
journal,
fifty
percent
of
the
time
in
my
other
journal
and
the
other
50
percent
of
time-
and
I'm
sure
I
was
trying
to
make
sense
of
what
happened
and
like
the
story
of
my
life
it'd
be
really
confusing.
A
It's
the
same
thing
about
why.
If
I've
already
been
using
a
journal
for
my
organization,
I
probably
want
to
stick
with
it
right.
So
that's
why
jira
has
a
lot
of
incumbency,
and
this
is
why
we've
moved
from
a
replaced.
Your
emotion
to
an
integrate
with
your
emotion.
B
But
is
it?
Is
it
possible
to
migrate
jira
issues,
jira
project,
the
whole
project
management
thing
to
gitlab
or
does
any
of
the
features
in
jira?
You
know
not
exist
in
gitlab,
so
that
some
things
are,
you
know
irreplaceable.
I
don't
know.
A
There
is
some
stuff
that
jira
can
do
that.
Gitlab
can't
do
in
my
personal
opinion.
Having
worked
with
both
tools
is
that
I
actually
like
gitlab
stuff
more,
because
I
think
it's
simpler.
One
of
the
big
problems
with
jira
is
that
it's
super
complicated
to
use
a
lot
of
that
time,
but
once
again
like,
if
an
organization's
been
using
it
for
five
years,
it's
really
hard
to
convince
them
to
stop
using
it
right
yeah.
B
Okay,
yeah,
actually,
another
reason
that
I
can
think
of
why
you
know
jira
is
sticky
to
most
people
is
that
usually
people
who
use
jira
they
use
confluence
as
well
for
wiki,
so
they've
got
like
more
stuff
in
there
and
then,
if,
if
you
suddenly
move
to
gitlab,
then
you
know
you
might
spend
a
lot
of
time.
A
B
Yeah
because
jira
and
confluence
subscription
are
actually
the
same,
so
you
pay
for
seven
dollars
per
user
per
month
for
jira
and
then
you
get
confluence
as
well.
B
Yeah,
that's
that's
what
I
that's
what
I
know,
but
let
me
check
if
that's,
if
that's
correct,
that's
not.
B
A
Cool
all
right,
so
that's
competitors
how
to
recap
everything
right,
so
gitlab's,
a
very
broad
product.
We
have
five
different
product
categories.
That's
really
great.
If
we
get
into
competit,
like
all
these
conversations
about
wire,
creates
better
blah
blah.
A
Why
this
is
better,
then
it
becomes
a
tool,
a
versus
tool
b
comparison,
and
the
fact
of
the
matter
is
that
we
are
better
in
some
of
these
things,
but
in
other
categories,
we're
not
right,
but
one
of
the
things
that
gitlab
does
do
and
our
biggest
unique
differentiator
is
the
fact
that
gitlab
can
do
all
of
this
stuff.
Really
no
one
else
in
our
industry
can
do
is
as
broad
as
we
are,
and
the
idea
is
that
if
you
get
gitlab,
you
get
those
benefits
of
our
unique
differentiator
right.
A
So
your
engineers
spend
less
time
integrating
things
you
save
on
license
costs
and
you
have
better
organizational
output
because
everything's
consolidated
in
one
tool.
I
was
an
engineer
for
half
a
decade.
This
is
something
that
actually
really
really
does
matter.
It's
not
just
like
what
our
official
sales
mark,
like
stance
is
like
as
an
engineer.
A
This
is
a
powerful
change
and
it's
something
that
really
will
help
out
our
customers,
so
gitlab's
one
shared
table
right
and
what
this
means
is
that,
like
regularly,
what
happens
is
that
your
developers
are
at
one
table?
Your
devops
people
are
at
one
table
your
security
people
are
at
this
other
table
and
no
one's
talking
to
each
other,
but
with
gitlab.
Everyone
is
looking
at
the
same
issues,
the
same,
merge
requests
and
you
have
better
collaboration
across
your
organization
that
could
that
alone
could
improve
your
organization
20
right.
A
So
in
terms
of
like
making
engineering
teams
more
efficient,
the
fact
that
we
have
better
collaboration
because
of
git
lab
it's
a
it's
like
a
huge
output
of
our
product
that
no
one
else
can
say
cool,
so
there's
gonna
be
a
homework
assignment.
That's
gonna
come
out.
If
you
need
help
with
the
homework
assignment.
Let
me
know
it
should
only
take
around
30
minutes.
If
it
doesn't,
let
me
know,
but
my
my
goal
for
homework
is
that
it
only
takes
30
minutes
and
yeah.
A
So
what
do
y'all
think
about
getting
it
in
by
this
friday?
Is
that
fair.
B
D
A
Right
cool
all
right,
so
I'm
happy
to
clarify
anything
else,
and
I
have
two
action
items
for
you
all.
So
one
is
to
investigate
the
burn
up
chart
that
we
saw.
I
owe
that
to
you
ariana
and
then
the
second
one
is
the
investigate
migration
path.
That
jira-
and
I
owe
that
to
you
aletha,
so
I
have
those
as
action
items
I'll
share
the
google
doc
for
homework
with
you
at
the
end
of
the
session.
Is
there
anything
else
that
I
can
clarify?
A
I
don't,
unfortunately,
I
don't
think
we
have
enough
time
to
do
the
little
mini
project
unless
you
all
really
want
to
which
I'm
happy
to.
A
Do
sounds
like
we
don't
want
to
do
it.
Okay
sounds
good,
I
mean
my
feelings,
aren't
hurt
so
yeah
great.
Let
me
know
if
there's
anything
else
I
can
clarify
and
if
not
then.
A
Okay,
so
I
mean,
if
I
hope
you
have
a
great
evening-
and
I
left-
I
know
it's
like
9
p.m-
your
time
so
y'all
can.
I
won't
keep
you.