►
Description
GitLab team members discuss how they work, their career history, and answer questions from students at We Think Code_
We Think Code_ : https://www.wethinkcode.co.za/
GitLab: https://about.gitlab.com/
GitLab for Education: https://about.gitlab.com/solutions/education/
A
A
We
have
three
that
we're
going
to
hear
from
specifically,
and
then
we
have
a
q
a
session
after
we
hear
from
those
three
people
so
first
off
to
talk
about
myself
and
what
I
do,
I'm
in
a
space
of
tech,
that's
called
developer
relations
and
developer
relations
is
a
type
of
job
that
involves
working
with
developers
who
are
using
the
product
of
the
company.
So
companies
like
microsoft,
have
developer
relations
because
microsoft
puts
out
a
bunch
of
technology
that
developers
use
things
like
visual
studio
code
or
just
visual
studio.
A
Things
like
xamarin
is
owned
by
microsoft,
and
that's
a
language
that
you
can
write
in
and
when
they
have
these
products
they
want
developers
to
know
how
to
use
them.
So
they
have
this
position
called
developer
relations
or
devrel
for
short,
and
what
our
job
is
is
to
show
developers
and
people
who
want
to
code
and
people
who
want
to
work
in
tech
and
do
things
with
technology
who
want
to
make
apps
and
make
all
these
amazing
things
that
we
see
in
our
lives.
A
We
show
them
how
our
product
can
help
them
now
within
developer
relations
or
devrel.
There's
a
lot
of
different
types
of
debris,
there's
just
I'm
a
devrel
or
I'm
a
developer
evangelist,
which
is
what
we
have
at
gitlab
or
we
have
developer
advocates
or
we
have
developer.
There's,
there's,
there's
community
involvement
and
there's
a
lot
of
different
titles
that
work
under
it.
But
it's
all
under
this
big
umbrella,
deborah
now
I'm
an
education
evangelist,
meaning
I
don't
work
with
developers
who
are
already
at
a
company
and
are
making
apps.
A
I
work
with
people
who
are
learning
how
to
make
apps,
and
so
my
developer
is
usually
a
student
or
a
professor
who's
teaching
students.
So
that's
who
I
focus
on
in
my
job
and
I
have
to
know
a
little
bit
how
to
code.
I'd
certainly
have
to
know
how
gitlab
works,
because
I'm
trying
to
convince
them
that
they
should
be
using
gitlab
and
that's
what
my
job
is.
A
That's
and
that's
part
of
why
I'm
here
with
you
all
is
because
I'm
trying
to
convince
you
all
that
gitlab
is
amazing
and-
and
I
don't
have
to
work
that
hard
with
we
think
code
to
convince
you
that
gitlab
is
amazing.
But
that's
why
I'm
here
and
I'm
here
to
host
a
bunch
of
people
who
actually
do
the
real
work.
B
A
Real
coding
and
the
real
developer
work
and
we're
here
to
hear
from
them
because
they
want
to
talk
about
their
experience
in
their
careers
and
we
have
today
we
have
megan
philo
who's,
a
front-end
engineer.
We
have
steve
as
a
party
who's,
an
sre
and
he'll.
Tell
you
more
about
what
that
means,
and
we
have
hannah
suter
who's,
a
product
manager,
and
these
are
the
three
people
that
I
think
those
are
the
three
people
that
we're
going
to
be
hearing
from
today.
A
I
want
to
double
check
and
make
sure
on
my
list
real
quick,
because
I'm
forgetful,
sometimes
nope
megan,
hannah
and
steve.
So
what
they're
going
to
do
is
they're
just
going
to
take
about
10
minutes
and
they're,
going
to
tell
you
a
little
bit
about
their
work,
what
they
do
they
might
share
their
screen
and
show
you
what
their
workflow
looks
like
a
little
bit.
So
you
can
get
a
sense
of
what
it
is
that
they
do
and
what
it
is
that
you'll
be
doing
once
you
graduate
as
well.
A
C
Sure,
thank
you
pj.
I'm
really
happy
to
be
here
today.
So
thanks
for
having
me,
as
you
said,
I'm
megan,
I'm
a
front-end
engineer
on
the
digital
experience
team
here
at
get
lab
I've.
Actually
I'm
actually
pretty
new
to
the
company
I
joined
not
even
three
months
ago,
and
so
I'm
new
to
the
company
and
I'm
also
fresh
in
my
career
as
a
developer.
C
C
C
We
want
them
to
ultimately
hit
that
buy
button
and
become
a
paid
customer,
and
a
lot
goes
into
that
not
just
developing
right.
This
is
all
coded,
but
every
little
piece
of
content
on
this
site
is
like
meticulously
placed
to
serve
our
our
goal
right,
so
seo
search
engine
optimization
is
super
important.
We
want
people
that
might
google
what
is
devops
to
maybe
land
on
our
page
analytics
we're
constantly.
C
Looking
at
page
views
clicks
all
that
kind
of
stuff
to
see
what's
working,
what's
not
working
where
we're
winning
and
where
we
could
learn
more
from
content.
We
have
a
whole
content
team
dedicated
to
words.
I
am
not
a
wordsmith,
I
just
code,
so
I'm
glad
there's
some
folks
that
just
tell
me
what
to
type-
and
it
sounds
good
brand.
C
Oh
wow
brand
is
so
big.
I
mean
look
at
our
tanooki
everywhere.
Brand
goes
a
long
way.
It's
on
a
t-shirt
that
builds
that
awareness
that
we
need
to
drive
people
down
that
funnel.
So
those
aspects
are
really
important
in
a
front-end
role
when
it
comes
to
marketing
sites
knowing
search
engine
optimization
just
how
to
kind
of
interpret
data
in
analytics
things
like
a
b
testing,
and
not
only
that,
but
when
it
comes
to
our
tech
stack,
we
use
as
a
front-end
engineer.
C
On
top
of
that
is
another
layer
called
next,
which
helps
us
write
gigantic
sites
using
view
it
kind
of
helps
us
streamline
that
and
another
layer.
On
top
of
that,
we
use
typescript,
I'm
not
a
fan
of
it
right
now,
because
I'm
very
new
to
it,
but
everyone.
I
know
that
loves.
It
has
a
lot
of
experience
with
it.
So
I
hope
to
be
a
typescript
evangelist
someday.
C
C
We
actually
empower
all
team
members
at
gitlab
to
edit
the
content
themselves,
so
we
have
what's
called
markdown
files
and
yaml
files
and
they
can
go
right
in
there
and
edit
the
content
themselves
and
it
works
so
that
talk
about
efficiency
and
streamlined.
So,
on
top
of
that,
for
our
stack,
we
use
node
and
yarn
as
package
managers,
it's
developer
choice,
but
that's
extremely
important
to
learn,
as
we
have
node
packages
or
yarn
packages
and,
of
course,
git.
C
C
Before
I
go
more
into
sharing
some
projects.
I've
been
working
on,
I
kind
of
touched
upon
our
stack
and
just
like
what
kind
of
makes
me
successful
in
this
role.
The
stack
and
just
kind
of
knowing
like
seo
analytics
that
kind
of
stuff,
but
soft
skills
are
very
important.
You
can
teach
anyone
how
to
code,
but
soft
skills
are
kind
of
harder
to
learn
if
you're
not
familiar
with
our
git
lab
credit
values.
C
C
You
need
to
be
able
to
iterate
and
be
efficient
and
drive
towards
results
and
yeah.
Just
be
a
good
person
all
around,
I
think,
helps.
So
again
you
can
teach
anyone
to
code,
but
if
you
don't
have
the
soft
skills
you're
not
like
a
pleasure
to
work
with,
and
it
might
be
harder
to
get
a
job,
but
enough
talking
I'll
show
you
a
bit
of
what
I've
been
working
on.
One
of
our
main
initiatives
right
now
on
the
digital
experience
team
is
to
we're
migrating
repositories
and
tech
stacks.
C
I
am
not
familiar
with
ruby
on
rails,
but
I
learned
about
it
here:
it's
pretty
fun
to
use,
but
now
we're
moving
it
all
to
a
new
tech
stack
of
view
and
next
and
I
had
not
known
vue
coming
here.
I
was
a
react
developer
but
because
I
understood
those
fundamentals
of
html
css
javascript,
I
was
able
to
catch
on
really
fast,
so
it's
all
super
fun
to
use
so
we're
migrating
pages
to
our
new
tech
stack
to
make
it
way
more
efficient
and
just
faster
to
get
to
market.
C
C
We
have
so
many
people
here
at
get
lab
and
those
outside
the
company
can
also
contribute
to
our
site.
We
want
to
make
sure
that
with
everyone
touching
this,
it
scales
well
and
the
code
is
still
organized
so
with
that
we
have
all
of
our
guides
and
components,
view
components,
but
so
in
my
day-to-day
every
day
is
different.
This
is
like
just
one
type
of
piece
of
work
that
I
get
to
work
on
every
day,
but
this
is
like
the
stuff
I
love.
C
So
here
is
this
program
called
figma
and
our
designers
are
very,
very
talented
and
they
build
this
stuff
up
for
us.
So
this
is
what
we
want
the
page
to
look
like,
and
this
is
kind
of
like
a
wireframe
with
dummy
text,
because
we
don't
write
content,
there's
a
whole
team
to
write
content
for
us,
so
we
just
want
to
get
this
skeleton
working
so
looks
like
we
have
a
header
type
of
section
and
looks
like
as
you
click
these.
C
C
So
I've
been
working
on
this
since
last
week
and
I've
been
out
on
pto
for
a
few
days.
So
it's
not
quite
done,
but
it's
come
a
long
way
from
this.
I
remember
that
so
this
is
my
local
environment
so
far
and
so
yeah
we
have.
We
actually
got
some
content
too,
so
it's
not
just
dummy
stuff,
but
so
over
the
course
of
the
past
week
and
a
half
worked
on
these
view:
components
that
work
animations
all
that
fun
little
stuff,
that
people
people
love.
C
We
have
our
little
carousel.
That
was
tough
and
then
right.
Now,
I'm
working
on
this
filter
filter
area.
So
I
worked
more
on
functionality
than
how
it
looks
right
now.
So
hence
the
super
ugly
drop
downs,
but
I've
never
made
something
like
this
before
and
it
was
tricky,
but
I
learned
a
lot
in
the
process.
C
So,
let's
filter
by
mid
market
company
sizes,
all
those
are,
let's
do
education.
So
let's
do
one!
That's
like
really
apparent,
there's
so
many
in
here
how
about
just
education?
Okay,
so
they
changed
so
our
filter
works.
So
I've
been
working
on
that
right
now,
very
challenging,
but
the
rest
of
it
looks
good
focus
on
accessibility.
C
Pj.
I
see
your
hand
up.
Do
it
am
I
running
out
of
time?
Oh
you're,
clapping,
okay,
thanks!
Thank
you
as
a
front
end
engineer.
We
can't
just
develop
things
and
forget
about
it.
There's
a
lot
of
things.
You
have
to
focus
on
especially
accessibility,
and
I
think
that
it
encompasses
a
lot.
It's
not
just
folks
that
may
have
to
use
screen
readers,
which
is
super
important
to
cater
your
site
to
anyone
that
uses
assistive
technology,
even
though
you
might
not.
C
Accessibility
goes
for
people
that
might
not
have
great
internet
speeds
or
use
a
different
screen
size
like
a
mobile
device.
Your
site
needs
to
be
accessible
to
anyone
and
any
everyone.
So
I
have
a
very
I'm
very
passionate
about
that.
So
when
I
do
my
work,
I
make
sure
that
I'm
testing
with
a
screen
reader,
I'm
testing
on
an
ipad
on
a
smart
device,
all
different
screen
sizes,
because
just
because
it
looks
good
for
a
desktop
and
I
can
read,
it
doesn't
mean
someone
else
can
right.
C
D
C
A
Sure,
well
really,
this
has
been
a
really
good
overview.
So
far
it's
we
were.
We
were
gonna,
do
just
about
10
minutes,
so
you're
right
at
10
minutes
right
now,
but
I
I
do
want
to
say
it's
really
cool
that
you
showed
us
like
your
local
environment,
like
if
you
all
look
up
at
her.
Her
browser
address
bar,
says
localhost
300
customers
like
this
website
that
we're
looking
at
is
running
on
her
computer
so
that
she
can
see
what
changes
she's
made
like
there.
It
is
in
in
their
node
terminal.
C
No,
thankfully,
there's
many
tutorials
on
the
internet
of
people
doing
similar
things.
So,
while
no
one
has
the
exact
solution
I
need
I
could
pick
and
choose
like.
Oh
that'll
work
really
well
or
oh.
This
is
gonna,
make
things
a
lot
easier
for
me.
So
it's
it's
a
lot
of
that
and
asking
questions
of
my
team
members
that
have
done
similar
things.
So
asking
questions
is
like
you're
not
expected
to
know
everything.
I
would
not
have
a
job.
If
I
had
to
know
everything.
A
Yeah
and
gina
put
a
question
in
zoom
as
well.
What
exactly
goes
into
devising
a
style
guide
and
how
do
you
determine
what
goes
in
it
and
how
many
levels
of
the
company
are
involved
in
those
decisions?
Now
I
know
you
said
earlier
that
you're
not
a
style
you're,
not
a
designer
necessarily,
but
how
many
other
teams
are
involved
in
in
just
getting
to
the
point
where
you've
got
like
an
actual
wireframe
on
figma
to
look
at
and
make
look
like
that.
C
C
We
have
style
guides
but,
most
importantly
for
a
developer.
We
have
design
system
and
we
have
one
called
slippers,
and
if
you
speak
with
someone
that
works
on
the
gitlab
product,
there
is
a
design
system
called
pajamas.
So
hence
the
name,
and
we
have
like
atomic
components
that
we
create
in
this
design
system
that
were
given
to
by
our
designers
and
like
we
have
a
button,
and
these
are
the
props
it
takes
in
and
like
this
is
what
it's
going
to
look
like.
C
So
that
helps,
but
really
it's
the
way
I
like
to
work.
Is
we
get
these
wire
frames
and
they're
pixel
perfect,
like?
I
know
that
when
I
click
on
this,
I
need
the
header
and
this
card
to
be
like
65
pixels
away
from
each
other
like
that
is
so
helpful,
but
I'm
not
a
designer.
So
I
can't
speak
like
beginning
to
end,
but
this
is
from,
like
my
my
cliff
high
overview,
like
what
I
see
goes
on.
A
Even
just
knowing
that
there's
a
brand
team
who
makes
the
decision
about
how
things
are
going
to
look
a
design
team
that
designs
them
to
brand
specifications
and
then
a
front
end
team
that
makes
it
look
correct
down
to
the
very
pixel
distance
between
two
two
objects:
fantastic,
fantastic.
Thank
you.
So
much
megan
stick
around
we're
gonna!
Do
that
q
a
at
the
end
afterwards,
but
up
next
talking
to
everyone,
is
going
to
be
hannah.
A
B
I
asked
if
I
could
switch
to
be
a
software
engineer
after
a
few
years,
so
I
coded
for
a
couple
years
and
then
I
started
asking
a
lot
of
questions
about
you
know.
Why
are
we
doing
this?
Can
I
talk
to
the
customer?
Can
I
understand
why
this
like?
Why
we're
doing
this?
Instead
of
that?
And
then
someone
pulled
me
aside
and
was
like,
if
you're
actually
interested
in
this
stuff,
maybe
product
management
would
be
a
good
fit
for
you.
B
So
that's
where
I've
been
ever
since
I've
been
here
at
get
lab
since
august
of
last
year
and
my
role,
I'm
embedded
with
a
development
team
of
engineers.
So
I
have
front-end
engineers
on
my
team,
back-end
engineers
on
my
team,
a
qa
engineer,
a
tech
writer
and
then
I'm
the
sole
product
manager,
and
then
we
also
have
an
engineering
lead,
so
there's
about
10
or
so
give
or
take
in
my
team,
and
what
my
job
is
is
to
sort
of
set
the
direction
for
the
team.
B
So
how
do
the
developers
know
that
what
we're
working
on
is
the
right
thing
to
be
working
on
right
now
we
have
so
many
conflicting
priorities.
How
do
we?
How
do
we
make
the
decision
on
which
direction
we're
headed
both
short
term
and
long
term
to
help
meet
some
of
our
company
goals?
So
I
interface
both
with
the
engineers
about
half
the
time
and
then
my
other
half
of
my
time
is
spent
interfacing
with
customers
talking
to
them
and
making
sure
we're
on
the
right
track,
doing
validation.
B
So
what
I
like
about
this
role
is
that
I
get
to
kind
of
keep
one
of
one
foot
in
the
technical
and
understand
on
a
technical
level.
What's
going
on,
I'm
sort
of
able
to
like
you
know,
look
at
code
and
understand
what's
going
on,
and
then
I
have
one
foot
more
in
the
business
world.
I
do
a
lot
of
presenting
our
roadmap
doing
discovery
with
customers
and
what
I
like.
B
So
I
like
the
ver,
the
varied
nature
of
my
job
and
that
no
two
days
are
alike
and
that
I
get
to
be
a
little
bit
social
because
I
do
like
talking
to
people.
So
I'm
not
heads
down
coding
all
day
either
which
I
like.
Let
me
go
ahead
and
show
you
a
little
bit
of
what
my
work
looks
like
it
manifests
in
a
lot
of
different
ways.
B
B
I've
talked
to
12
customers
so
far
about
this
and
I've
put
together
what
we
call
an
opportunity
canvas
this
kind
of
summarizes
all
of
the
research
I've
done
and
what
I'll
do
actually
after
this
is
presenting
this
to
product
leadership,
engineering,
leadership
and
before
we
go
ahead
and
put
all
of
our
engineering
resources
into
this
new
feature,
everyone's
going
to
kind
of
sign
off
and
agree
that
they
understand
why
we're
doing
this
and
that
it's
worthwhile
to
do
so.
This
is
taking
a
lot.
B
B
Here's
some
more
mock-ups,
so
I
I
worked
with
our
ux
designer
to
come
up
with
these.
These
are
not
pixel,
perfect
right.
These
are
kind
of
the
phase
before
we
get
to
the
pixel
perfect.
These
are
still
draft
wireframes
that
we
can
show
to
customers.
We
click
through
the
flow
with
them.
We
say:
here's
what
we're
thinking
what's
your
feedback,
because
it
doesn't
make
sense
to
get
something
down
to
that
pixel,
perfect
level
until
we're
really
sure
about
it.
B
Keeping
with
the
same
feature,
this
is
the
epic,
so
this
is
like
the
highest
level
sort
of
requirements
we
have-
and
I
summarized
what
we've
learned
in
our
ux
research
and
kind
of
how
what
we
learned
in
the
research
translates
to
different
requirements
that
our
developers
have
to
implement,
and
this
is
a
very
big
feature.
So
there's
a
whole
lot.
B
It's
my
job
to
break
this
down
into
iterations
at
gitlab.
We
try
to
do
really
small
changes
quickly,
so
I've
suggested
a
few
iterations
here
of
how
we
can
do
this,
get
it
in
front
of
customers
and
get
feedback
on
it
quickly,
and
then
it's
also
my
job
to
take
this
big
feature,
epic
right
and
break
it
down
into
smaller,
consumable
chunks.
So
a
developer
doesn't
pick
up
this
epic.
They
would
pick
up
these
issues
that
are
underneath
the
epic,
and
these
are
something
that
can
be
done
in
a
milestone
or
sprint.
B
However,
you
would
term
that-
and
the
last
thing
I'll
show
is
more
general,
so
I've
talked
a
lot
about
this
new
feature
we're
building,
but
in
general
we
have
a
lot
of
things,
we're
working
on
at
a
given
time
and
it's
my
job
as
the
product
manager
to
carve
out
our
planning,
and
I
don't
it's
a
collaborative
process.
What
I
do
is
I
put
in
priority
order
all
of
the
things
that
I
know
we
need
to
work
on
in
a
given
milestone
and
then
I
work
with
the
engineers
and
they
say
hey.
B
Actually,
I
think
this
is
more
important
or
I
know
we
can't
get
that
done
until
this
is
unblocked
by
another
team.
So
this
is
a
very
fluid
sort
of
conversation
that
happens
before
we
get
ready
to
work
on
a
milestone,
and
at
this
point
we
started
our
milestone
last
week,
so
things
are
pretty
much
pretty
set.
It
won't
change
too
much
from
here,
but
it's
my
job
to
kind
of,
say:
hey
team,
here's
what
I
think
we
should
work
on
and
then
solicit
their
feedback
and
then
we
iterate
on
it
from
there.
A
Awesome
and
like
even
in
your
very
title,
it
says
manager
but
you're,
not
a
manager
of
people,
the
way
that
people
might
think
of
what
a
manager
does
in
a
business,
you're
a
manager
of
product
and
projects
really
you're
like
this
is
this
is
what
we
need
to
focus
on,
and
you
help
people
stay
focused
as
opposed
to
like
people.
Work
like
a
manager
would
do
is
that
is
that.
B
Right
exactly
so,
I
have
manager
in
my
title,
but
I'm
I'm
technically
an
individual
contributor,
I'm
no
one's
manager,
but
where
product
has
kind
of
an
interesting
role,
is
that
we
have
to
influence
without
being
someone's
manager.
So
I
don't
dictate
anything
to
anyone,
but
I
still
have
to
get
my
team
on
board
with
my
vision
right
and
say.
This
is
why
I
think
it's
important
that
we're
working
on
what
we
do.
This
is
the
impact
you're
going
to
have
on
our
customers
and
really
bring
like
a
sense
of
meaning
and
influence
to
the
team.
A
B
I
would
say:
that's
half
of
it
right
as
probably
the
more
external
interaction
with
customers,
competitor
research,
making,
sure
I'm
on
top
of
my
game
in
terms
of
understanding
the
authentication
and
authorization
landscape
and
how
gitlab
plays
into
that.
And
then
the
other
half
is
really
more
internal
facing
and
working
with
my
engineering
team.
B
B
Yeah,
I
think
that's,
I
think,
that's
really
helpful.
I
try
to
be
really
detailed
when
I
write
up
what
we're
supposed
to
be
working
on,
because
I
know
how,
if
something
isn't
defined,
it's
left
open
to
interpretation
and
there
can
be
a
lot
of
miscommunication.
So
that's
probably
my
biggest
takeaway.
A
And
megan
in
the
chat
said
you
know
as
a
developer,
I'm
so
thankful
for
product
managers.
It's
nice
to
grab
issues
that
I
know
I
pri
are
prioritized
it'd,
be
so
hard
as
a
front-end
engineer
or
backend
engineer.
Anyone
doing
any
kind
of
coding
to
have
this
sort
of
if
you're,
looking
at
everything
you
have
to
do
it's
hard
to
get
anything
done,
but
if
someone's
there
to
break
it
down
to
those
chunks
like
hannah,
does
it
makes
it
much
easier
for
you
to
complete
your
task?
A
Working
on
a
website
is
like
one
of
the
top
things
that
comes
to
mind
and
now
we've
got
a
product
manager,
and
this
is
sort
of
like
there's
an
interesting
once
you're
in
it
almost
expands
to
what
other
things
you
can
do,
and
this
is
something
that
not
every
student,
especially
students
at
universities,
don't
often
know
about
these
opportunities.
So
I
just
want
to
again
reiterate
how
excited
I
am
to
be
able
to
bring
this
information
to.
We
think
code,
I
think
it's
awesome
hannah.
A
Thank
you
so
much
for
telling
us
about
what
you
do
and
giving
us
that
insight
we'll
have
that
q
a
at
the
end,
but
now
we're
moving
on
to
steve
as
a
oh.
I
just
I
just
messed
that
last
name
up
as
a
party.
I
nailed
it
that
time,
don't
worry,
I
did
it
and
he's
got
some
infrastructure
engineering
overview.
Some,
some
more
tell
us.
You
work
with
lots
of
code.
Tell
us
what
you
do
steve.
Take
it
away.
Thank
you.
E
Thank
you
so
much
so
yeah.
My
official
title
would
be
senior
site
reliability
engineer,
which
is
a
mouthful.
That
is
why
we
always
say
sorry,
because
it's
much
easier,
so
a
necessary
position
is
usually
part
of
the
infrastructure
department,
which
is
the
department
that
is
responsible.gitlab.com
stays
up.
24
7
for
our
customers
can
handle
all
the
traffic
that
comes
into
place
and,
for
example,
megan
mentioned
that
we
got
a
million
users
on
about.gitlab.com.
E
The
infrastructure
department
is
one
of
the
departments
responsible
for
that
website
to
make
sure
that
it
stays
available
for
our
customers
and
users,
so
I've
been
at
getlab
for
around
four
years
now,
almost
four
years,
so
it's
been,
it's
been
a
while.
I
joined
get
lab
as
a
back-end
engineer,
so
I
used
to
work
on
the
product
team
and
then,
a
few
months
ago
I
changed
departments
from
a
development
to
an
infrastructure.
E
So
that
also
shows
like
gitlab
is
such
I
wouldn't
call
it
a
big
company,
but
there
are
so
many
nooks
and
crannies
at
get
lab,
and
so
many
specializations
that
you
can
move
on
from
one
department
to
another.
So
if
you
are
finding
a
passion-
oh
you're,
more
passionate
about
product
management
for,
for
example,
or
I'm
more
passionate
about
front-
and
I
can
move
on
to
a
front
end
road
or
move
to
a
back
and
roll
or
vice
versa.
E
So
I
really
really
enjoy
that
and
you
don't
get
that
opportunity
anywhere,
not
anywhere
else,
but
you
don't
get
a
lot
of
those
opportunities.
So
what
I
mostly
work
on
nowadays
is
mostly
reliability
issues.
So
what
does
that
mean?
Because
that's
very
very
vague
right
and
it
is
sometimes
it's
debugging,
a
production
issue.
E
So,
for
example,
one
of
ours,
one
of
our
pages
is
not
loading
or
some
of
our
services
are
slow,
like
they're
taking
two
seconds
to
load
instead
of
one
second,
for
example,
right
and
that's
when
we
usually
have
a
alert
which
pages
us
and
says
okay
figure
out,
there's
an
issue
go
figure
it
out
and
that
that
takes
most
of
the
time
for
us
and
we
do
have
an
on-call
rotation
for
that
so
you're
on
a
rotation
for
a
week.
Luckily
we're
we're
such
a
distributed
company.
E
We
follow,
we
call
it
follow
the
sun,
which
is
pretty
much
your
own
call
during
the
day,
not
in
the
evening
and
then
when
you're,
not
in
that
rotation,
you're
working
on
either
maintenance
tasks
or
reliability
issues.
So
an
an
example
of
a
reliability
issue
is
hey.
This
service
is
not
performing
as
expected
during
peak
hours,
so
we'll
we
go
in
figure
out
what
the
problem
is
understand.
E
If
it's
a
feature
that
we
like
a
feature
that
shouldn't
isn't
working
as
expected
or
it
can
be
optimized
in
certain
way
or
we
need
to
re-architect
something
like
that.
So
it's
a
lot.
It's
a
very
high
level
from
time
to
time,
like
it's
more
figuring
out
what
the
problem
is
and
then
sometimes
you
have
to
interact
with
the
product
team,
so
we
interact
with
product
managers
a
lot
and
development
teams.
A
lot
as
well
saying:
hey
we're
seeing
this
problem
in
production.
E
So
these
are
all
the
issues
that
are
assigned
to
me
right
now,
so
I
also
am
quite
passionate
about
interviewing,
so
I
enjoy
doing
technical
interviews
and
we're
at
in
the
middle
of
revamping
technical
interviews
for
dslr
position
here.
So
I'm
working
on
that.
So
I
won't
be
able
to
share
with
that.
But
this
is
one
of
the
issues
that
I
was
talking
about
things
not
performing
as
expected
right.
E
So
this
is
one
of
the
incident.
Someone
got
paged
and
we
can
see
that,
for
example,
some
some
things
for
zone.
So
we
we
deploy
gitlab.com
on
multiple
data
centers.
If
you
want
to
call
them
that
and
on
one
of
our
data
center
on
gcp
as
not
performing
as
expected
right,
we
can
see
this
graph
going
down.
So
we
investigate
why
this
is
happening
and
see
if
we
can
mitigate
this
problem
for
our
users,
so
they're
not
affected
as
much
and
then
digging
into
our
logs.
E
We
have
a
bunch
of
graphs
and
so
on
and
so
forth.
So
we
figure
out
the
problem
right
now
we're
dealing
with
our
cloud
provider,
which
in
this
case
is
gcp
and
we're
in
contact
with
them,
trying
to
figure
out
a
problem.
So
there's
a
lot
of
performance
analysis
and
these
kind
of
issues
like
low-level
code,
understanding
how
the
network
is
passing
by,
and
these
are
the
kind
of
issues
I
really
enjoy,
because
it's
sometimes
like
you're,
a
detective
trying
to
find
the
smoking
gun.
E
So
it's
super
super
nice
and
then
another
one
is
also
an
investigation
issue
which
resulted
into
me
doing
some
development
work.
Actually
we
had
a
production
issue.
Our
monitoring
infrastructure
was
crashing.
We
call
it
crash
loop.
Basically,
so
it
was
starting
up
starting
up
for
five
minutes
and
then
crashing
again,
because
it
was
getting
out
of
memory
basically,
and
we
investigated
the
problem
sometimes
investigating
the
problem
is
just
looking
at
the
code
that
you're
running,
and
sometimes
you
haven't
written
the
code
yourself.
E
So
you
get
really
good
at
just
reading
code
and
assuming
certain
things.
So
luckily
I
I
used
to
be
a
back-end
engineer,
so
I
do
I
I
sometimes
can
get
into
a
mind
of
a
developer,
how
they
think.
So
that's
that's,
really
helpful
and
then
you
end
up
like
for
in
this
case
we
ended
up
opening
up
a
pull
request
on
github
for
a
product
that
we
use,
which
is
prometheus,
which
is
one
of
the
most
popular
monitoring
infrastructure
here
and
we're
talking
to
the
community.
E
How
the
best
way
to
solve
this,
and
this
things
like
that.
So,
unless,
like
I
wanted
to
show
this
because
in
the
story,
sometimes
it's
more
than
just
maintaining
gitlab.com
and
making
sure
it's
reliable.
It's
also
sending
patches
upstream
sending
patches
to
our
developers
as
well
to
fix
certain
performance
problems,
and
also
talking
about
that.
This
is
me
asking
how
for
develop
for
development.
E
So
every
week
we
have
an
incident
review
meeting
where
we
look
at
the
biggest
incident.
We
had
the
past
week
and
look
at
okay.
Why
did
this
happen
and
understand
like
what
the
causes
the
chain
of
actions
that
happened,
that
caused
this
problem
to
our
customers?
Right,
because,
at
the
end
of
the
day,
we
want
to
improve
their
reliability
for
our
customers,
and
then
we
found
out
that
a
sidekick,
which
is
a
queueing
mechanism
that
we
use
at
gitlab,
can
just
create
a
bunch
of
jobs
without
us
limiting
it
right.
E
E
So
now
our
developers
already
are
doing
great,
limiting
on
an
api
level,
but
our
developers
can
create
thousands
of
jobs
without
any
consequences
for
them
anyways,
but
for
infrastructure
it
will
can
crush
the
database
and
so
on
and
so
forth.
So
we
need
to
make
our
system
more
reliable
for
them,
so
they
can
do
whatever
they
want
to
do,
but
not
prevent
users
from
logging
in
or
users
from
using
our
website.
E
So
it's
a
lot
of
works
work
like
architectural
work
like
this
as
well,
and
then
I'm
also
a
maintainer.
What
a
maintainer
means
is,
I'm
I
do
a
bunch
of
code
reviews
on
certain
projects,
so
one
of
them
is
wood
house,
for
example,
and
we
one
of
my
colleagues
is
opening
up
a
new
merch
request
for
adding
continuous
profiling.
So
profiling
is
a
mechanism
that
you
use
to
figure
out
where
cpu
time
is
being
spent
right.
E
It's
a
common
tool
that
we
use
a
lot
here
at
gitlab
just
to
see:
okay,
there's
slow
requests.
Where
is
the
cpu
time
being
spun?
And
here
we're
implementing
a
new
command,
so
you
can
run
a
small
command
locally
and
it
will
give
you
a
profile
for,
like
I
don't
know,
10
days
or
one
day,
for
example,
for
a
specific
service.
So
then
we
can
say:
okay
during
us
time
zone,
we
see
cpu
being
spent
a
lot
on
this
request
and
things
like
that.
E
So
then
we
can
make
data
driven
decisions
and
we're
just
working
on
a
feature
like
that.
So
it's
a
again
it's
a
split
between
development,
work
and
detective
work.
I
guess
I
I
think
skill
wise.
It
is.
Let
me
see
how
I'm
doing
on
time,
yeah
skill
wise.
It's
it's
a
mixture
of
things,
so
gitlab.com
is
mostly
a
ruby
on
race
application.
E
So
it's
a
lot
of
ruby.
We
use
postgres
as
our
database
and
some
of
like
so
the
website
here
that
you
can
see
here.
It's
all
rendered
via
ruby
and
again
we
use
vue.js
here
as
well,
and
then
we
have
some
services
written
in
go
or
sometimes
you
use
golang
when
you
want
to
search
for
in
google
for
help
on
that.
E
So
some
of
our
high
performance
systems
like
low
level
systems
so,
for
example,
a
service
called
gitly,
which
is
what
serves
git
traffic
for
our
users,
that
is
written
in,
go
because
it
it
needs
to
be
a
bit
low
level
and
more
concurrent
things
needs
to
happen
and
ruby
by
default
is
single
threaded.
So
sometimes
it's
not
the
best,
the
right
tool
for
the
job
right.
E
We
always
try
to
pick
the
right
tool
for
the
job
and
our
two
tools
at
the
moment
are
ruby
and
and
go,
and
then
we
do
have
some
c
sharp
and
things
like
that.
But
again,
those
are
for
like
the
security
tools
that
we
have,
that
need
to
run
on
the
windows,
environment,
for
example,
and
then
all
of
our
infrastructure
runs
on
linux.
So
we
do
have
some
in
those
environments.
I
am
probably
the
one
responsible
that
introduced
them.
E
Unfortunately,
I
used
to
work
on
the
ci
team
and
the
ci
team
was
responsible
of
introducing
ci
for
windows,
ci
for
mac,
os
and
ci
for
linux,
so
that
team
was
responsible
for
introducing
those
oss
and
then
we
we
are
in
a
split
architecture.
So
most
of
our
stateful
workloads,
so
our
databases,
for
example,
are
running
our
virtual
machines
in
our
cloud
provider.
But
then
our
web,
like
our
ruby
on
rails
application,
is
running
in
kubernetes.
E
But
that
gives
us
a
a
bunch
of
the
reliability
features
that
we
were
looking
for,
for
example,
if
a
server
dies
it
automatically
restarts
or,
for
example,
a
service
is,
let's
say
a
machine
is
misbehaving
right.
Like
I
don't
know,
these
are
legit
issues,
sometimes
that
we
hit
as
like
simply
cpu
temperature
is
high,
so
it
starts
throttling
right.
What
we
what
kubernetes
gives
us
is.
E
It
just
kills
the
pod
and
moves
it
to
another
server
somewhere
else
and
again,
lo
and
behold,
performance
is
back
to
normal,
so
it
gives
us
that
kind
of
automation
out
of
the
box
and
also
like
rolling
out
new
versions
of
the
application.
So
the
way
we
do
we
do,
it
is
gradual
rollout.
So,
for
example,
you
don't
just
turn
off
the
traffic,
deploy
a
new
version
and
turn
it
back
on,
because
that
will
be
disruptive
to
our
user
right.
So
what
we
do
is
we.
E
A
E
E
Yeah,
it's
it's
a
that's
an
interesting
question
because
I
used
to
study
an
equivalent
of
a
computer
science
degree,
but
I
actually
dropped
out
of
that.
And
the
reason
for
that
I
I
enjoyed
so
the
school
I
was
working
with
studying
at
was
mostly
a
c-sharp.net
school
right.
So
you
learn
a
lot
of
the
microsoft
stuff.
One
evening
like
I
used
to
play
a
lot
of
games
as
well,
and
one
of
the
games
was
world
of
warcraft.
E
E
And
then
I
I
figured
out
oh
there's
php,
to
build
websites,
and
then
I
did
that
during
the
evening
and
I
enjoyed
a
lot
doing
php
but
php.
I
never
got
the
chance
to
learn
php
at
school,
so
I
did
that
during
the
evening
and
then
ended
up
okay.
I
really
want
to
work
in
an
industry
instead
of
continuing
school,
so
I
did
that
so
it
really
depends
on
the
person
itself.
E
E
I
would
suggest
you
not
to
jump
from
one
to
another
when
you're
starting
out
right,
because
that
that
is
one
trap
I
I
fell
for
as
well
like
oh
python
is
really
hot
this
week.
Let's
learn
some
python
or
vue.js
is
really
hot.
This
week,
let's
do
vgs
like
try
and
specialize
as
much
as
possible,
and
that
can
be
a
trap
as
well
and
it
sounds
like
you
are
just
wanting
to
become
really
good
at
one
thing
and
you're,
not
really
good
at
the
other
things.
E
So
I
always
like
follow
the
like
the
t-shaped
model
right
where
you
can
go,
breath-wise
understand
what
people
are
talking
about,
but
then
you're
focusing
focusing
on
one
specific
thing
like,
for
example,
myself,
I'm
focusing
on
infrastructure,
but
I
can
do
development
work.
I
can
do.
I
can
understand,
architecture,
decisions
and
so
on
and
so
forth,
so
that.
A
T-State
model
he
just
talked
about
it.
It
means
you
can
learn
a
lot
of
things
a
little
bit
but
learn
one
thing
really
deep
and
get
really
good
at
it.
So
steve
will
understand
if
someone
shows
him
some
code
in
a
lane
and
like
go,
he
can
understand
if
someone
shows
them
php
if
someone
shows
them
c
sharp,
maybe
even
like
r
and
rus
and
like
these
other
you,
if
you
looked
at
it,
you
could
be
like
I
kind
of
understand,
what's
going
on,
but
you're
really
good
at
infrastructure
steve.
Thank
you.
A
A
A
This
is
good,
okay,
so
yeah.
What
I
I
say
this,
because
I
want
all
of
you
to
know
that
that
hannah
and
steve
and
megan
and
myself
and
taylor
who's
been
in
the
chat
as
well.
We
didn't
go
to
school
and
learn
everything
we
needed
to
work
in
this
job.
We
had
to
learn
some
things
on
our
own
outside
of
our
education
circles
and
for
me,
especially
actually
my
background.
A
I
was
a
high
school
english
teacher
for
10
years
before
I
came
to
get
lab
so
your
path
and
where
you're
learning
and
how
you're
learning
and
it's
gonna
take
you
on
a
path
and
you'll
keep
learning
as
you
go
on,
so
just
because
you
can't
be
an
sre
today,
which
I
wouldn't
recommend
being
an
sre
today,
because
there's
a
lot
that
goes
into
it.
You
can
get
to
that
point
later.
F
So,
just
like
sort
of
a
general
question,
many
of
the
team
have
mentioned
you
know,
learning
things
on
the
job
coming
in
not
knowing
having
to
like
pick
up
a
lot
of
stuff
learning
through
that
experience,
which
can
there
was
sort
of
a
comment
in
our
slack
channel
around
that
being
quite
overwhelming,
like
where
do
you
start?
How
do
you
tackle
everything?
How
do
you?
F
How
do
you
manage
that
sort
of
newness
when
you
enter
sort
of
a
new
job
or
new
team,
and
and
does
the
team
on
the
call
here
have
any
tips
for
sort
of
learning
how
to
learn,
or
you
know
how
to
assimilate
information
quickly
any
tools
or
approaches
that
you
might
use
yourselves.
That
could
be
helpful
to
to
the
audience
here.
Yeah.
A
A
So
knowing
when
you
don't
know
something
and
don't
understand
and
figuring
out
just
what
the
very
next
thing
to
do
is
even
if
it's
as
simple
as
I
have
an
error
in
this
code,
I
don't
know
what's
the
next
step
is
copy.
It
paste
it
into
google
and
see
where
that
error
has
shown
up
for
other
people.
That's
all
you
have
to
worry
about.
Is
that
next
step?
Anyone
else
on
the
panel,
if
you'd
like
to
say
something.
B
I
can
to
echo
sort
of
what
you
said:
pj,
I
think,
being
willing
to
be
humble
and
vulnerable
and
admit
when
you
don't
understand
something
goes
a
long
way
and
it
becomes
obvious
very
quickly
if
someone
doesn't
understand
something
and
are
trying
to
hide
that.
So
it's
better
just
to
be
open
and
admit
that
you
don't
understand-
and
you
know
people
are
not
going
to
blame
you
for
that
right.
B
We've
all
been
there
in
tech,
because
it's
always
so
new
and
another
thing
is
whenever
I
onboarded
a
gitlab
like
I,
I
remember
being
confused
between
a
merge
request
and
an
issue
and
not
really
understanding
the
difference
which
is
like
embarrassing
right.
I
felt
embarrassed
about
that,
but
I
had
an
onboarding
buddy
assigned
to
me
who
I
felt
like
I
could
ask
any.
You
know
stupid
questions
too.
B
C
What
helped
me
because
I
came
in
not
knowing
vue,
but
I
knew
in
the
interview
process.
Gitlab
uses
vue,
so
I'm
going
to
just
read
the
docs
just
understand
the
basics.
So
I
know
why
would
someone
use
view
over
react
and
I
was
scared.
I
was
nervous.
I
wasn't
going
to
get
the
job
that
I
really
really
wanted,
because
I
didn't
know
that
stack,
but
they
looked
at
my
portfolio
and
saw
like
my
react,
work
and
they're
like
oh
yeah,
like
your
skills
will
transfer
over.
C
So
in
that
time,
for
when
I
got
hired
and
actually
started,
I
was
trying
to
build
my
own
view
projects
and
for
me
I
love
self-study,
like
I
I
code
at
night
outside
of
work,
and
I
want
to
build
my
own
project.
So
I
built
like
I
just
got
a
dog
and
I
made
like
a
a
schedule
tracker
for
him
like
anytime.
He
eats
or
needs
his
medication.
C
C
I
was
working
on
the
filter
and
like
hey,
tyler,
a
co-worker
of
mine,
like
I
know
your
review
expert
like
what
am
I
missing
here,
and
he
pointed
me
in
the
direction
of
something
in
the
next
docs
and
he's
like
you
would
never
probably
like
ever
use
this
until
you
need
it,
and
that
just
happens.
Sometimes
you
don't
learn
things
until
you
need
it
and,
like
that's,
okay,
what
hannah
said
like
you
need
that?
Give
yourself
grace
and
you
need
to
have
that
low
level
of
shame.
A
A
E
E
Maybe
I
don't
know
how
to
do
that,
so
I
paired
up
with
megan
and
like
we
set
up
on
a
call,
and
she
showed
me
how
she's
doing
it
or
she
showed
me
how
she
solved
the
problem
and
like
seeing
someone
else
solving
the
problem
that
you
were
facing
is
so
much
more
educational,
sometimes
than
figuring
it
out
on
your
own.
Just
because,
like
you
got
an
understanding,
oh
this
other
person,
like
I
one
thing
that
I
always
always
remember,
is
when
I
was
debugging
a
problem.
E
I
never
used
to
look
at
the
source
code.
Like
the
library
I
used
to
call
or
anything
like
that
when
I
was
starting
out,
but
then
I
I
was
pairing
with
a
senior
engineer
at
my
previous
company,
and
I
just
saw
him
like
digging
into
the
code,
the
class
we
were
calling.
That
was
from
a
library
that
we
imported
and
that
kind
of
blew
my
mind
like.
I
never
thought
of
doing
that
myself
right
like
and
that
unlocked
me
a
new
set
of
debugging
skills.
E
D
E
Logs
or
grabs
for
an
error
message
in
google,
for
example,
and
things
like
that,
so
you
get
tidbits
from
other
people,
so
you
can
say
okay
for
this
situation.
This
might
be
the
best
way
to
do
to
debug
this
problem,
and
things
like
that.
So
even
like
again
having
low
level
of
shame,
saying,
hey,
I
have
no
idea
how
to
solve
this
find
an
expert
pair
with
the
expert
and
then
the
next
time
around.
A
A
I
think
we're
going
to
move
on
to
some
of
those
seed
questions,
while
I'm
addressing
one
of
these
questions,
if
y'all
in
the
chat
have
any
questions
that
you
want
to
ask
feel
free
to
type
in
the
chat,
we're
going
to
try
and
keep
track
of
those
and
we're
going
to
answer
some
of
the
ones
that
we
can
answer
best.
But
one
of
the
seed
questions
was
why
gitlab
over
github-
and
I
love
that
this
is
the
first
question
we
got.
Github-
is
also
a
code
repository.
A
They
also
have
some
things
that
are
similar
to
what
gitlab
does
and
if
and
if
I'm
going
to
be
totally
honest,
you
know
what
my
answer
is:
use
what
works
for
you.
The
reason
I
like
gitlab
is
because
I
think
it
works
best
for
a
lot
of
great
situations,
and
I
think
that
github
has
some
use
cases
that
make
sense
too.
A
So
you
noticed
in
steve's
presentation
at
one
point:
he
went
to
github
and
he
was
on
github
and
he
did
some
work
on
github
because
he
was
putting
a
package
helping
with
a
package
that
existed
on
github,
so
yeah
they're
competitors,
but
in
tech
and
in
work
and
in
business.
It's
about
what
works
best
for
you.
Why
I
like
gitlab,
it's
everything
in
one
place.
It's
a
devops
platform.
You've
got
your
code
repository,
but
you've
also
got
ci
cd,
so
you
can
run
pipelines
right
there,
security.
Once
you
have
to
start
thinking
about
security.
A
You
don't
want
to
have
to
go,
get
a
whole
other
app
for
that.
It's
right
there
in
gitlab.
I
think
gitlab
is
great
because
it's
one
place
for
everything.
There's
taylor
put
this
great
link
in
the
chat,
github
vs
gitlab,
it's
where
we
talk
about
the
differences
and
why
you
would
choose
one
or
the
other.
The
second
part
of
this
question
that
I
got
was
how
did
git
lab
come
to
be
since
there
was
already
github.
A
Well,
you
know
burger
king
got
invented,
even
though
there
was
mcdonald's
ford
cars
got
created,
even
though
there
was
oh
actually,
ford
was
first
technically,
I
suppose
you
know,
but
like
we're
constantly
taking
something
that
already
exists,
and
someone
says
well,
I
like
what
that
is.
But
what,
if
we
did
it
like
this,
so
git
lab
was
created
only
a
few
years
after
github,
I
think
github
was
created
in
2008
and
I
think
gitlab's
first
commit
was
2011.
A
A
So
for
a
time
we
were
doing
different
things.
Similarly,
and
even
then,
we're
not
the
only
two
places
to
be
a
code
repo
on
the
market,
there's
lots
of
places
where
you
can
store
code,
but
the
reason
that
I
choose
gitlab
over
github
is
not
just
because
I
work
here
like
I
said
it's
a
single
place
for
everything.
Even
my
personal
projects,
I
store
my
personal
projects
on
on
gitlab.
I'm
gonna
show
you
on
my
screen
real
quick
for
this
one.
A
A
D
D
It
really
can
feel
like
you've
got
this
massive
instrument,
multiple
task
ahead
of
you
and
you
don't
even
know
where
to
start
and
absolutely
that
becomes
part
of
the
part
of
the
exercise
of
learning
how
to
how
to
develop.
These
applications
is
figuring
out
how
to
break
those
tasks
down
into
more
manageable
aspects
and
figuring
out.
What
are
the
more
achievable
pieces
that
you
can
tackle
in
isolation
and
that's
good
for
both.
D
Just
having
those
miniature
successes
in
the
process
of
your
ongoing
development
helps
a
lot
in
making
you
feel
like
you're,
making
progress,
and
you
are
successfully
building
out
whatever
you,
whatever
you're,
trying
to
build,
as
opposed
to
having
this
massive
tangle
of
here's
a
little
bit
that
doesn't
work,
there's
a
little
bit
of
that
doesn't
work
and
you
kind
of
just
get
lost
in
in
the
weeds.
You
don't
know
you
don't
know
where
you're
going
or
what
you're
trying
to
achieve
next.
A
One
of
the
next
seed
questions
is:
why
is
git
lab
open
source
and,
to
be
honest,
we're
open
source
because
it's
it's
the
best
way
to
get
people
what
they
want
and
to
get
people
involved
in
your
product.
Open
source
is
a
very,
very
important
space
in
tech
and
when
people
think
of
open
source,
a
lot
of
people
tend
to
think
of
github.
A
lot
of
open
source
projects
are
hosted
there,
but
it's
not
an
open
source
product
itself.
A
Git
lab
is
an
open
core
product.
You
can
contribute
to
git
lab
if
you
want
to.
If
you
want
to
go
in,
and
you
want
to
like,
I
think
megan
was
the
first
one
to
say:
if
you
we
want
people
to
be
able
to
change
our
websites
like
we
want
not
just
our
team
members.
We
want
our
community,
our
community
of
users,
to
feel
empowered
to
suggest
changes
and
if
they
can
make
the
changes
themselves
and
open
source
and
open
core
are
it's
our
identity.
A
We
started
as
an
open
source
project,
and
then
we
didn't
become
a
business
until
20
2014.
I
think
it
was
2015..
I
know
this
2014
is
when
we
actually
became
a
business
but
taylor.
Thank
you
drop
that
link
right
there
about
what
an
open
core
model
is.
So
you
can
know
what
the
difference
between
open,
core
and
open
sources,
and
then
you
asked
about
how
to
contribute
and
I've
got
the
link
for
that.
A
We
actually
have
a
hackathon
every
quarter
and
that
hackathon
is
designed
to
point
our
users
in
our
community
to
specific
issues
that
they
can
contribute
to.
Whether
that's
our
documentation,
which
I
have
to
be.
This
is
a
big
secret.
Contributing
to
documentation
is
a
great
way
to
learn,
because
not
only
are
you
making
changes
and
and
fixing
something
that
needs
to
be
fixed,
you're
learning
at
the
same
time
how
something
works
and
you
can
start
implementing
those
docs
and
making
it
work
for
you
better.
A
That's
my
big
secret
for
the
day
guys
y'all
can
y'all
can
take
that
to
the
bank,
but
that
link
contribute
to
gitlab
talks.
All
about
our
hackathon
talks
about
the
tracks
that
we're
looking
for
and
where
we're
looking
for
help
and
if
you
scroll
all
the
way
to
the
bottom,
you'll
see
a
newsletter
you
can
sign
up
for
and
that
will
make
sure
that
you're
always
getting
information
about
the
hackathon
and
when
it's
happening,
let
me
see
how
are
decisions
made
about
new
features?
That
is
a
really
good
question.
A
B
B
Obviously
our
revenue
as
a
newly
public
company,
that's
important
to
us,
so
everything
our
initiatives
from
a
team
perspective
are
aligned
to
our
upper
level
initiatives
and
honestly,
some
of
what
we
work
on
too
is
the
fires
that
come
in
from
a
particular
customer,
who's,
angry
or
something's,
not
working
the
way
they
expect
and
those
get
escalated.
Sometimes
so
it's
not
always
vision
items.
Sometimes
it's.
We
have
to
put
out
this
fire
of
the
day,
so
I'd
say
it's
a
combination
of
those
two
things.
A
Yeah,
so
there's
there's
the
way
that
the
people
who
run
the
company
want
it
to
go
what
we
want
to
implement
and
then
we
hear
from
the
community
either
when
they're
a
little
upset
that
it's
not
working
the
way
it
should
or
when
they
have
an
idea
for
a
new
feature
or
product
that
gitlab
can
can
have
hannah.
Do
you
with
that
process?
Do
you
think
that
your
time
is
kind
of
split?
Equally,
do
you
think
there's
a
focus
more
on
community
measures
than
vision?
B
Yeah,
it's
tough.
You
know
I
try
to.
I
try
on
each
of
my
planning
issues,
which
I
showed
you
to
balance
kind
of,
like
our
vision
items
that
we
know
we
need
to
get
done
with
fires
from
customers
with
security.
That's
another
important
thing,
especially
in
the
authentication
space.
We
have
to
balance
some
of
our
security
issues
that
come
in,
and
so
I
I
really
try
to
balance
it.
We
also
have
targets,
especially
for
certain
priority,
bugs
that
come
in
that
are
high
priority
and
high
priority
security
issues.
B
A
So
you,
you
have
a
system
of
prioritizing
what's
important
at
the
moment,
based
on
like
classifications,
right
yep,
yeah
awesome.
Thank
you
so
much
for
helping
us
answer
that
hannah.
I
really
appreciate
that
the
question
to
chat
taylor
answered
it
really
well,
but
they
asked
working
for
a
company
like
git
lab.
What
do
you
do
if
or
when
you
feel
like
you're
drained
or
not
motivated?
A
Actually,
in
addition
to
that
mental
health
link,
one
of
the
things
I
was
told
early
on
was
you
are
a
manager
of
one,
and
that
means
that
I
decide
what
I
do
with
my
time
because
we're
fully
remote-
and
I
want
to
make
sure
everyone
knows
this-
gitlab's
fully
remote.
Every
single
person
you
see
on
screen
working
for
git
lab
lives
where
they
want
to
live
right.
We
work
from
home
or
if
we
want
to
work
from
a
co-working
space,
we
can't
but
there's
no
offices
for
gitlab,
because
that's
the
case.
A
That
means
there's
not
a
person
here.
Making
sure
hey
are
you
working?
Are
you
working
right
now?
There's
no
one
that
comes
around
to
make
sure
that
you're
working
we
manage
our
own
time,
the
way
that
we
see
fit
to
accomplish
the
goals
we
want
to
accomplish
now.
I
know
what
you're
all
thinking,
what
about
someone
who
just
doesn't
do
their
work
and
just
slacks
off
and
never
gets
their
work
done.
A
They're
not
going
to
be
at
the
company
very
long,
because
they're
going
to
get
caught
very
quickly
because
we
are
focused
on
someone
mentioned
our
credit
values
earlier
the
values
of
the
company,
the
r
stands
for
results.
That
means
we
value
getting
it
done.
Whatever
the
results
are,
what
matters,
whether
it
takes
you
two
hours
or
20
hours.
We
need
those
results,
whether
you
work
in
the
morning
or
whether
you
take
the
whole
day
to
yourself
and
just
work
from
eight
o'clock
at
night
to
one
in
the
morning.
A
A
Take
a
second
and
just
take
the
time
off
that
you
need
to
recharge,
because
we
recognize
that
you're
not
going
to
work
your
best
if
you're
drained
anyone
else
on
the
panel
want
to
speak
to
that
idea
of
like
like
maybe
a
time
when
I'll
tell
you
what
there's
days,
I
don't
feel
motivated
and
there's
days
that
I
just
can't
handle
it,
and
so
I
take
an
hour
and
I
go
stretch
or
I
do
some
yoga
or
I
just
enjoy
coffee.
Anyone
else
on
the
panel
want
to
talk
about
that.
Avoiding
burnout.
E
I
can't
take
tickets
for
avoiding
burnout
like
sometimes
taking
time
off
is
also
important.
We
have
more
of
a
tell
not
ask
policy,
so
in
the
sense
you
tell
people
that
you're
taking
time
off
you
don't
ask
your
manager
anything
like
that.
Hey
can.
I
take
that
time
off
and
I
think
that's
really
really
important
and
to
say
in
this
in
the
sense
like,
oh
this
week,
you're
feeling
really
tired,
really
sluggish
and
you
feel
sometimes
overwhelmed
as
well
with
the
amount
of
work
that
you
have
to
do.
E
Then
maybe
I
should
have
taken
that
on
my
own
time
and
it
sounds
like
I
should
have
taken
that
proactively
and
like
it
makes
you
think
that
taking
day
off
is
also
productive
on
its
own.
It's
not
like
oh
you're
working,
so
your
product
have
no
sometimes
taking
a
day
off,
is
productive
and
I'm
saying
that's
and
I'm
a
big
hypocrite,
because
I
do
struggle
with
this
all
the
time.
E
But
it's
also
nice
like
to
say
it
out
loud
because,
like
taking
care
of
yourself,
like,
I
always
think
like
taking
care
of
yourself
like
as
also
taking
care
of
your
future
yourself
in
this
sense,
like
if
you're
just
burning
yourself
out
right
now,
there's
not
gonna,
be
a
future
you
to
continue
doing
the
work
you
need
to
take
your
current
stuff
take
care
of
your
current
stuff.
So
a
future
you
can
do
better
work
than
you're
doing
right
now,
kind
of
thing.
A
And
we're
fortunate
to
be
at
a
company
that
does
prioritize
that
and
gina.
You
made
an
absolutely
great
point
that
this
is
the
ideal
that
this
is
what
we
hope
for,
but
junior
developers
don't
always
have
that
freedom
organizations
they
work
for
sometimes
organizations
will
push
you
to
burn
out.
And
what
would
you
advise
in
this
case-
and
this
is
this?
Is
I'm
gonna?
A
Tell
you
right
now
is
a
hard
question
to
answer
because
oftentimes
it
feels
like
your
job
and
your
money
and
your
livelihood
and
having
a
roof
over
your
head
and
food
is
going
to
keep
you
in
that
job
and
in
that
place
where,
where
you're
being
burnt
out
and
pushed
to
a
breaking
point,
I
mean
I'm
a
former
teacher.
I
know
that,
as
an
english
teacher,
I
was
constantly
working
on
weekends.
My
day-to-day
was
full
of
teaching
students
and
then
I
would
get
papers
to
grade
and
these
were
like
essays.
A
So
I
had
125
students,
I
had
125
essays
to
grade
and
each
one
takes
me
about
10
minutes.
So
we're
looking
at
1250
minutes
of
grading
that
I
have
to
do
in
a
certain
amount
of
time
I
felt
burned
out
back
then
it's
very
different
from
working
in
tech,
where
you
have
sprints
and
milestones
and
and
the
pressure
to
make
it
right
and
you're
looking
at
an
error
and
it
stays
there
and
it
stays.
A
If
you
notice
that
the
environment
you're
in
is
bad
for
you,
if
at
all
possible,
get
out
of
there,
if
it's
not
possible,
carve
out
time
for
yourself
wherever
you
can
and
recognize
that
taking
care
of
yourself
allows
you
to
take
care
of
the
things
that
that
work
expects
you
to
it's.
It's
such
a
hard
situation.
I
can't
say
well,
this
is
what
I
did
when
I
was
a
junior
developer,
because
I
wasn't
a
junior
developer
but
hannah.
Maybe
you
can
talk
more
about
this.
B
I
have
to
perform
to
this
level,
and
I
have
very
high
expectations
internally,
and
I
think
one
thing
I've
learned
along
the
years
is
that
there
are
certain
areas
in
your
career
where
you
can
focus
and
have
a
bigger
impact,
whereas,
if
you're
trying
to
do
all
the
things,
it
might
not
have
the
impact
that
you
think
it's
it
it
has.
So
I
would
talk
to
your
manager
and
say:
hey.
I
have
these
10
things.
Can
you
help
me
prioritize
them
right
and
have
them
that's
part
of
their
job?
B
D
No
reason
you
wouldn't
want
to
achieve
this
objective
that
you
know,
there's
no
sacrifice
too
great
ended
up
working
like
two
months
to
work
months
worth
of
time
in
a
single
month,
and
actually
hospitalized
myself
and
I'll.
Tell
you
straight.
There
is
no
thing
worth
doing.
That
is
worth
compromising
your
health
for
all
right.
Nobody,
no
matter
how
much
pressure
or
stress
people
are
putting
on
you.
D
Your
health
will
never
ever
be
what
it
once
was.
If
you
ever
break
yourself
to
that
extent,
so
whether
it's
pressure
you're
putting
on
yourself
or
pressure,
someone
else
is
putting
on
you
make
sure
to
just
take
care
of
yourself
and-
and
you
know,
take
care
of
yourself.
Don't
don't
don't
sacrifice
your
long-term
health
for
short-term
gains,
whether
they're
for
yourself
or
someone
else,
it's
it's
not
worth
it.
F
So
I
think
you
know
everything
that's
been
shared
is
super
helpful
in
the
con
sort
of
the
context
I
was
referring
to.
Is
it
may
not
be
that
the
organizations
are
putting
such
pressure?
But
you
know
a
junior
developer
may
not
have
the
freedom
to
just
walk
in
to
say:
hey,
I'm
taking
a
couple
of
days
off
so
the
context
you've
you've
brought
to
the
table
makes
absolute
sense
and
I
think
it
is
about
identifying
you
know:
what's
a
healthy
environment,
what's
a
healthy
workload
and
and
knowing
when
to
step
away
from
that.
F
If
you
have
the
option
to
do
that,
but
at
the
same
time,
in
the
context
of
of
the
students
and
the
graduates
in
our
program,
just
to
sort
of
have
the
tools
to
be
able
to
as
hannah
mentioned
speak
up,
you
may
not,
you
know
just
be
able
to
say
I'm
taking
time
out,
you'll
have
to
request
that
timeout.
You
know
in
whatever
way
that
that
company
requires
you
to
do
so,
but
I
think
it
is
just
about
identifying
I'm
struggling.
I
need
to.
A
I
think
I
think
you're
absolutely
correct
that
as
a
junior.
Sometimes
you
can't
just
like
it's
it's
it's
hard
to
as
a
brand
new
employee
come
in
and
be
like.
Well,
I've
been
here
two
weeks.
You
won't
see
me
next
week,
goodbye
I'm
gone.
A
lot
of
that
does
come
down
to.
Does
the
company
work
hard
to
make
sure
that
the
juniors
understand
what
they
can
do
and
what
is
available
to
them?
A
So
I
think
that
it
it's
true
that,
and
we
have
a
question
from
monique
that
I'm
gonna
that
I'm
gonna
verbalize
in
a
second
it.
It's
true
that
you
can't
always
just
be
like
well,
I
know
I'm
brand
new,
but
here's
what
I'm
doing
guess
what
like
I'm
taking
care
of
myself,
but
there
are
times
where
you
can,
because
sometimes
that
expectation
that
you
can't
do
that
comes
from
within
and
I'm
not
saying
hey
just
like
don't
show
up
it's
fine
you'll
be
okay,
but
often
times
like
gregory
says.
A
Sometimes
we
put
and,
like
hannah
said,
we
put
pressure
on
ourselves.
We
have
to
be
a
certain
way.
We
have
to
do
it
a
certain
way
or
they're
going
to
get
rid
of
me
or
they're
not
going
to
like
the
work.
I
do.
We
need
to
examine
that
and
the
same
way,
I
said
that
metacognition
about
learning
is
important
being
aware
of
yourself
and
where
the
pressure
is
coming
from
can
be
important
as
well
and
so
monique
said.
A
Would
you
say
short
term
pressure
for
a
year
or
two
is
fine,
especially
being
a
junior
needing
to
learn
and
grow
within
any
challenging
environment
and
then
finding
the
ideal
company
environment
thereafter,
as
as
far
as
that
goes
I'd,
say
it's
all
about
knowing
yourself,
we
all
have
different
amounts
of
pressure
that
work
for
us.
I
work
best
under
a
certain
amount
of
external
pressure
and
a
time
crunch,
and
it
will
be
like
yeah.
She
just
said.
Perhaps
the
uncomfortable
challenge
might
be
good
for
your
growth.
A
Yeah
discomfort
can
lead
to
growth
and
change
can
be
difficult,
but
there's
a
difference
between
discomfort
from
change
and
the
struggle
of
something
new
and
the
pressure
that
they
sang
about
and
then
kanto
that
the
one
sister
saying
about
that
was
like
it's.
This
pressure
that
keeps
you
from
going
anywhere
from
doing
anything
and
it
just
it.
It's
like
a
vice
there's
a
difference
between.
I
need
to
push
myself
and
work
hard,
and
I
need
to
push
myself
and
now
I'm
in
a
hospital
and
it's
about
what
works
for
you
individually.
A
B
Yeah,
so
I
think
one
thing
I
didn't
realize
when
I
was
starting
out
in
my
career
is
just
how
many
options
there
are
in
tech
in
terms
of
well.
I
do
this
one
presentation
for
high
school
students
here,
that's
like
I
think
I
have
eight
or
ten
different
roles
in
tech
that
I
talked
about,
so
there's
so
much
out
there.
It's
not
just
code,
but
I
think,
having
that
background
of
knowing
how
to
code
will
take
you
so
far
in
your
career
and
open
so
many
doors.
B
So
I
just
want
to
commend
all
of
you
for
learning
the
skill
that
quite
honestly
like
not
just
anyone
can
pick
up
and
so
it's
challenging,
but
I
think
you'll
find
it
to
be
worth
it
and
just
keep
your
mind
open
to
all
of
the
different
roles
and
opportunities
available
to
you
in
tech
and,
I
think
you're
in
the
driver's
seat
in
your
career
in
tech.
You
have
the
option
to
go.
It's
such
an
in-demand
field.
You
have
in-demand
skills
and
you
can
go
anywhere
you
want.
So
I
think
for
my
younger
self.
A
C
C
You
could
be
years
into
your
journey,
but
still
at
the
very
beginning
I
went
to
school
for
music,
and
so
I'm
a
musician
and,
like
you,
sit
in
a
practice
room
practicing
the
same
thing
over
and
over
and
over
again
to
get
perfect
and
like
I
accidentally
brought
that
mindset
with
me,
like
I
just
have
to
code
so
much
24
7
if
I'm
gonna
get
so
good
and
I
burnt
myself
out,
but
now
I
know
you
don't
have
to
do
that.
So
don't
burn
yourself
out.
C
A
That's
right
because
megan
already
is
the
best
developer
in
the
world,
so
no
one
can
upend
her
right
now.
This
has
been
fantastic.
We
are,
we
are
just
about
at
10
30,
which
is
our
ending
time.
I
know
we
didn't
get
to
answer
all
the
questions
and
I
know
we
didn't
get
to
tell
you
everything
you
wanted
to
know
about
being
a
developer,
but
I
I
do
hope
that
this
was
something
that
you
enjoyed.
That
gave
you
some
insight
or
some
inspiration
and
thank
you
to
megan
and
to
steve
and
to
gregory.
A
Thank
you
for
coming
back
and
taylor.
Thank
you
for
helping
us
out
in
the
chat.
I
appreciate
that
so
much
and
thank
all
of
you
from
we
think
code
for
coming
through
and
helping
us
have
people
to
talk
to,
because
otherwise
it
was
just
going
to
be
like
five
people
and
gina,
and
we
were
just
going
to
tell
gina
everything.
So
y'all,
participating
and
being
here
means
the
world
to
us.
So
thank
you.
F
Thank
you
so
so
much
pj
megan
steve
hannah
who's
dropped
and
and
greg
it's
so
exciting
that
greg's
just
joined
the
team
and
and
happens
to
be
one
of
our
alumni.
I
think
super
inspiring.
You
know
just
to
see
what
sort
of
journey
are
we
think
coders
can
follow
and
so
greg
we're.
Definitely
gonna
have
to
have
you
back
to
talk
more
about
your
your
new
role
in
a
couple
of
months
once
you've
settled
in
and
yeah
so
grateful
to
the
team.
I
know
you
all
have
a
lot
on
your
plate.