►
Description
In this video Senior Support Engineer Brie Carranza interviews Senior Support Engineer Manuel Grabowski, with intention of sharing Manu's thoughts and ideas with the world! ✨
Mentioned projects/tools/posts:
- Support dotfiles: https://gitlab.com/gitlab-com/support/toolbox/dotfiles
- PM/TW finder: https://gitlab.com/gitlab-com/support/toolbox/dotfiles/-/merge_requests/31
- Emoji adder: https://gitlab.com/gitlab-com/support/toolbox/dotfiles/-/merge_requests/36
- Copy as Markdown: https://github.com/notlmn/copy-as-markdown
- Format Link: https://github.com/hnakamur/FormatLink-Chrome
- Automating the Support Team Contributions label: https://gitlab.com/manuelgrabowski/log/-/issues/7
- Staff Engineer's Path book club: https://www.youtube.com/playlist?list=PL05JrBw4t0Kp7yMHav5Gwt9_BkOXO90hM
- Team-Tracking project: https://gitlab.com/manuelgrabowski/team-tracking/-/issues/27
- lolcat: https://github.com/busyloop/lolcat
- keychain: https://www.funtoo.org/Funtoo:Keychain
- autossh: https://linux.die.net/man/1/autossh
- diff-so-fancy: https://github.com/so-fancy/diff-so-fancy
- thefuck: https://github.com/nvbn/thefuck
00:00 - Intro
00:57 - What do you do here?
02:03 - How did you get here?
05:33 - Advice that Now-Manu would give Then-Manu
11:05 - What tools or processes would you wish more people knew or used?
14:55 - Any sacrifices you're making that are not visible?
21:00 - How do you make sure that you don't burnout?
23:07 - How do you handle a ticket where you have no idea what to do?
27:34 - What's a change you helped implement that you are excited about?
30:40 - What's a change that was difficult to implement but worth it in the end?
34:40 - Staff Engineer's Path book club – what stuck?
38:33 - What fun projects have you been working on?
43:00 - Team-Tracking learnings
48:05 - Fun Questions: Favorite GitLab feature?
50:08 - Fun Questions: How much do you love Kubernetes?
51:55 - Fun Questions: Favorite CLI tool?
55:35 - Closing remarks
A
Hello
today
is
June
9th
2023.
My
name
is
Bree
Carranza,
and
this
is
the
second
in
a
series
of
interviews
where
support
engineers
at
gitlab
are
taking
a
step
back
from
the
day-to-day
ticket
work
and
asking
questions
and
getting
to
know
one
another
and
sharing
those
conversations
with
everyone,
so
we'll
introduce
ourselves
and
then
dive
into
the
questions
that
we
had
planned.
My
name
is
Bree
Carranza
I'm
a
senior
support
engineer
at
gitlab.
Will
you
please
introduce
yourself.
B
A
B
Hey
I
haven't
timed:
it
I'm,
not
sure.
If
I'll
succeed,
I
decided
to
get
a
little
Fancy
with
the
answer
here
and
I
will
say:
I
copy
create
and
collaborate
and
I
mean
copy
in
the
sense
of
the
infamous
good
artist's
copy.
Gradle
is
still
sense
right
because
so
much
of
what
I
do
comes
from
our
documentation
from
older
tickets
from
workarounds
and
issues
like
I'm,
a
large
language
model
with
actual
intelligence
behind
it,
I'm
just
rearranging
texts
for
a
lot
of
the
time.
That's
not
all,
though
right
I
also
create
a
do.
B
A
B
Absolutely
one
of
my
favorite
stories
to
share
I
will
never
Tire
of
telling
it,
and
it's
amazing
that
we
managed
to
actually
have
that
interview
today,
because
this
whole
story
started
exactly
two
years
ago.
Two
years
ago,
I
wrote
a
support
ticket
as
a
gitlab
customer
I
was
at
my
old
job
back
then,
where
I
started
out
as
a
full
stack,
slash
back
end
developer
over
time.
B
In
that
job,
I
moved
more
and
more
into
a
devops
like
role,
mainly
because
I
was
I,
guess
the
biggest
nerd
on
the
team
like
whenever
something
I
don't
know,
Docker
or
Linux
servers
or
things
came
up.
They
went
there
Mario,
don't
you
know
that
stuff
and
I
usually
did
and
in
that
role.
I
I
also
managed
suggested
and
then
managed
the
move
to
gitlab
so
yeah.
That
left
me
administrating
at
work.
A
gitlab
instance
after
I
had
already
been
administrating
a
personal
one
for
many
years.
B
Let
us
know-
and
it's
so
great
to
see
that
our
efforts
are
seen
and
appreciated
and
I
said
a
bunch
of
funny
things
and
they're
like
oh,
don't
let
the
bean
counters
take
over
and
you
cannot
measure
support
quality
like
that
blah
blah
blah
and
he
was
like
yeah
yeah.
We
know
we
know
and
that
all
happened
during
a
time.
A
time
where
I
had
already
yeah
basically
decided
that
I
would
want
a
change
of
scenery,
myself
and
just
working
with
you
on
the
ticket,
because
it
was
a
pretty
complex
thing.
B
I
a
while
ago,
I
I
read
through
it
again
and
I
struggled
understanding
everything
that
we
understood
back
then
it
was
really
complex,
but
working
with
you
on
that
made
me
realize,
wait
a
second
like
this,
the
work
that
you
are
doing
for
me
here
on
this
ticket.
That's
not
that
far
removed
from
what
I'm
doing
for
my
team.
All
the
time
like
with
a
little
different
focus,
of
course,
but
I
could
be
good
at
that
too.
I
think
I
would
have
fun
with
that
too.
So
I
told
him
like
Hey.
B
A
That's
so
cool,
that's
so
wild
I
used
to
say,
like
thank
you
for
that
feedback.
That
was
very
amazing
and
that
was
circulated
pretty
broadly
within
gitlab.
I
know
that
it
was
I'm
fairly.
Confident
is
aware
of.
It
mentioned
it
in
a
call
that
I'm
not
sure
if
I
can
link,
but
thank
you
for
that
feedback.
That
was
awesome.
A
B
The
first
thing
is:
you
are
further,
along
than
you
think
you
are
fairly
early
on
when
I
started
like
having
pairings
with
with
people
who
have
been
here
longer,
I've
gotten
such
good
feedback
on
my
work
and
my
progress,
and
it
honestly
it
didn't
take
too
long
before
I
heard.
Oh,
you
should
have
been
hired
as
a
senior
right
away
and
I.
Think
most
of
us
in
in
support
at
least
have
some
difficulty,
accepting
compliments
and
so,
as
most
would
do
I
just
kind
of
hand
waved
that
away.
B
But
if
you
hear
it
often
enough,
you
do
think
about
it.
A
little
and
I
understand
why
it
was
sad
and
I
also
understand
why
I
wasn't
hired
as
a
senior
right
away.
I'm
not
like
now
having
a
grudge
or
anything
but
yeah,
I
I.
Don't
think
I
ever
mentioned
this
before.
To
be
honest,
what
in
the
end
finally
made
me
say:
okay,
now,
I
will
go
full
steam
ahead
with
my
promotion
to
senior
was
actually
seeing
someone
else
promoted,
who
started
around
the
same
time
as
myself
and
I
thought
like.
B
B
B
I've
had
a
lot
of
of
little
moments
since
I
joined
here
where
I
understood
oh
wow,
I
I've
read
the
value
before
but
I,
just
it
just
didn't
click
yet
for
this,
like
oh
I,
can
apply
it
here,
of
course,
that
makes
perfect
sense
an
example
very
early
on
so
in
in
the
emea
region.
We
have
a
weekly
call
for
the
whole
team
and
we
have
an
agenda
document
for
that
and
a
whole
process
like
who
is
no
taker.
B
Who
is
moderator
all
that
stuff
and
as
a
new
Joiner,
you
often
see
things
that
others
have
become
blind
to
so
I
saw
a
few
like
the
process
is
kind
of
it's
a
bit
weird.
It's
not
and
touching
that
process
that
a
gender
document
that
felt
like
I'm
just
I'm
new
here
I,
oh
I,
can't
so
I
had
the
values
like
everyone
can
contribute
bias
for
Action.
All
that
I
had
that
deep
enough
internalized
that
I
had
zero
problem,
starting
a
discussion
and
saying
hey,
you
know
what
I've
observed
this
I
would
suggest.
B
We
do
this.
What
do
you
think
and
then
one
of
the
first
comments
on
that
was?
That
sounds
good.
So
is
there
a
reason
you
didn't
just
do
it
like?
Why
didn't
you
just
do
it
and
it
like
clicked
for
me,
oh
yeah,
of
course,
like
it's
a
two-way
door
decision,
it's
so
easy
to
revert.
Why
didn't
I
just
do
it
and
I
think
I've
made
quite
a
lot
of
progress,
but
that
still
happens
all
the
time
and
that's
good
like
that.
Iteration,
that's
what
it's
all
about!
B
A
B
A
B
A
B
A
A
B
A
Helpful
for
yeah
just
buy
extraction
and
do
the
thing
that'll
be
okay,
sweet,
okay,
so
I
don't
know
about
you,
but
I
like
fun,
different
tools
and
processes,
and
things
like
that.
So
I
wanted
to
just
give
you
an
opportunity
to
ask:
are
there
any
tools
or
processes
that
you
wish
more
people
knew
about
just
like
they're,
so
awesome
they're
like
this
would
be
so
cool
if
more
people
knew
about
this.
A
B
Went
through
all
the
cliched
phases
like
I
had
the
I
don't
even
know
how
to
exit
the
eye
thing
and
and
thinking
in
their
right
mind
would
enjoy
you
that
it
doesn't
make
sense
what
is
going
on
and
then
over
time.
You
just
think
oh
wait.
A
second
couldn't
I
just
that
that
would
be
pretty
efficient
if
I
could
have
it
in
front
of
that.
You
start
seeing
that
end
like
nothing,
will
ever
beat
a
good
command
line
tool
in
terms
of
efficiency
and
flexibility.
B
B
A
B
Did
right,
it
just
allows
you
to
select
anything
on
a
web
page
copy
as
markdown,
and
it
will
do
what
it
said
like
that
is
amazingly
useful.
That's
the
one,
the
other
one
is
I,
think
it's
called
just
format
link
it's
very
similar.
Well,
not
necessarily,
but
I
use
it
very.
Similarly,
because
the
way
I
am
letting
it
format,
my
links
is
also
into
markdown.
B
That
saves
so
much
time
when
you
write
a
sentence
like
oh,
could
you
please
check
this
out
in
our
such
and
such
documentation
just
paste
the
link,
and
that
is
not
possible
if
we
copy
as
markdown
extension,
so
I
think
both
of
these
should
be
Essentials
for
everyone
in
support
at
the
very
least
I'm,
using
both
of
them
privately
as
well.
My
blog
is
in
markdown,
like
it's
just
super
useful
yeah.
A
That
sounds
amazing,
I'm.
Definitely
adding
that
second
one
and
we'll
link
to
dot
files
and
all
of
those
things
here
sounds
like
there's
like
room
for
contributions
that
help
with
like
usage
instructions
on
dot
files
and
stuff,
like
that
to
make
it
even
easier,
because
I
think
that
I
think
that
you're
right
about
adoption
for
DOT
files.
So
thank
you
yeah.
A
Convenience-
okay,
so
I
mentioned
at
the
beginning
that
this
is
the
second
in
a
series,
so
I
recently
was
interviewed
by
Bruno,
and
that
was
very
exciting
and
some
of
the
questions
that
he
asked
me
I
wanted
to
ask
you
because
I
think
that
they're
like
important
questions
to
talk
about
so
the
first
one
is
about
visibility
and
what
people
see
and
then
like.
What's
behind
the
screen
behind
swag
all
that
kind
of
a
thing,
so
the
question
I
think
the
way
he
phrase
it
is.
B
That's
tricky
like
I
I
cringe
at
the
idea
of
calling
it
a
sacrifice
and
I
me
like
I,
immediately
want
to
downplay
it
and
say
like
like
your
introduction
to
the
question.
Yeah
everyone
has
that,
like
don't
look
at
me,
I'm,
it's
okay!
It's
okay,
like
this
kind
of
reaction,
but
I'll
try
to
fight
that
urge
and
actually
answer
your
question.
Take
care
so.
B
However,
these
are
my
own
choices
like
that's,
not
something
that's
asked
of
me.
It's
not
like
my
manager
ever
like,
manages
me
and
says:
oh,
can
you
stay
like
that?
Just
doesn't
happen
here
like
at
all.
That's
me
and
it's
it's
also,
usually
not
because,
like
the
work
demands
it
or
anything,
it's
not
that
at
the
planned
end
of
my
shift,
I
see.
Oh
no
I
haven't
met
my
quota
or
anything
and
decide.
I'll
work
two
hours
longer
too,
like.
A
B
I
just
get
lost
in
work
fairly
easily
because
I
enjoy
it.
So
much
and
I
will
say:
that's
I
guess
a
fairly
nice
problem
to
have
about
work,
but
it's
still
a
problem.
I
think
and
it's
It's
tricky
because
I'm
like
a
really
strong
proponent
of
workers,
rights
and
all
that
jazz
are
like
not
to
get
too
much
into
politics,
ignoring
like
the
the
cliched
US
versus
you
comparison
that
our
connection
like
invites,
but
like
I'm,
just
extremely
yeah,
probably
left-wing
in
that
regard.
B
And
we
need
to
get
a
little
personal
here,
because
a
reason
for
that
honestly
is
my
life
is
a
bit
of
a
mess,
or
at
least
it
feels
like
that
to
me
quite
quite
often-
and
that
might
sound
depressing.
But
the
like
the
joy
that
I
get
from
work
and
I
do
get
genuine
Joy
from
work.
Really
that's
one
of
the
better
things
in
my
life
and
it
can
often
feel
like
the
only
thing.
B
Yeah
I,
don't
know
it's
thinking
about
this
reminded
me
about
how
we
all
have
all
this
talk
going
on
about
machines
are
taking
our
jobs
and,
and
we
need
Ubi
and
like
all
these.
These
topics
and
I
always
hate
this
debate,
because
it's
it's
focusing
so
much
on
on
this
social
welfare
and
people
will
be
lazy
and
don't
want
to
work
and,
and
that
stuff
and
I
think
I
just
think.
The
much
much
bigger
problem
is
like
the
collective
depression.
B
The
entire
world
will
fall
into
when
people
won't
be
able
to
derive
meaning
for
their
lives
out
of
their
jobs
anymore,
because
that's
a
thing
you
know,
I
was
I,
was
unemployed
for
a
month
between
University
and
my
first
job
voluntarily.
I
could
have
started
the
month
earlier,
but
I
wanted
to
chill
a
little
bit.
That
was
at
a
time
where
I
had
a
lot
going
on.
That
was
an
amazing
time
like
I
was
in
a
in
a
great
relationship.
I
had
like.
A
B
Right
and
like
that
experience
always
stuck
with
me
so
yeah,
you
know
as
much
as
I
support
the
the
idea
of
of
saying
it's
just
a
job.
You
are
not
your
work,
that's
all
true,
and
that's
yes,
like
I'm
behind
that,
but
I
personally
I'm
having
a
really
hard
time
like
not
defining
myself,
largely
through
my
work.
That's
just
how
it
is.
A
B
Yeah
that
that's
something
and
that's
honestly,
another
reason
why
I
like
being
here
like
this
environment,
makes
it
fairly
easy
like
I
know,
that's
of
course
it's
it's
me
as
well.
Not
everyone
is
like
that,
but
the
environment
plays
a
large
role
and
I
mean
I,
know
that
you
understand
this
and
and
and
will
not
think
I'm
weird
for
for
being
so
open
or
anything,
but
I
know
the
same
thing
about
like
everyone
in
the
company.
Basically-
and
that's
that's
a
pretty
nice
feeling,
yeah.
B
A
B
B
Right,
if
someone
is
wondering
oh,
do
I
have
a
drinking
problem.
The
answer
is
probably
yeah
and
I
have
been
told
or
I've
read
that
for
Burnout.
That
is
actually
not
like
that.
If
you're
still
wondering
do,
I
have
Bernard
you
don't
because
if
you
had,
you
would
know
I,
don't
know
how
true
that
is.
I,
don't
know
if
that's
just
gatekeeping
from
people
with
severe
burner
I,
don't
know
like
probably
semantics
and
exact
clinical
definitions
at
play
here.
I,
don't
know
so.
B
A
B
Yeah,
let's
be
real,
sometimes
I,
just
move
on
to
the
next
ticket.
That's
just
how
it
is
I
mean
lots
of
asterisks
right
if
the
SLA
allows
and
and
I
mean
that's
fine
right,
because
we
there
is
some
need
for
us
to
be
efficient
and
it
can
make
sense
to
leave
a
ticket
for
someone
else.
If
you
know
like
wow,
that's
really
just
not
my
thing,
and
there
is
someone
on
my
team
who
knows
how
to
handle
this,
and
what
I
would
also
say
is.
B
A
B
B
A
B
No
idea
at
all,
not
even
where
to
look
at
but
I
just
spent
two
days
on
this,
that's
harder
now
right,
because
I'm
I'm
much
more
mindful
of
my
time
and
I
there
is
choices.
I
have
to
make
on
where
I
I
spent
my
time
on
which
then
in
turn
has
the
fun
side.
Effects
of
kicking
kicking
off
my
imposter
syndrome
and
making
me
think,
oh,
am
I,
am
I,
avoiding
hard
stuff.
B
B
B
B
B
Know
one
one
thing
I
would
like
to
say
in
in
that
aspect
as
well
is:
when
you
look
at
someone
else's
work
like
especially
in
support
you
look
at
a
soft
ticket.
You
see
the
things
that
worked.
You
focus
on
them
like
you
might.
Even
sometimes
you
see
the
detour.
Oh
this,
this
wasn't
actually
it!
Oh.
Can
you
try
this
instead,
please,
oh
this,
that
was
it
but
like
just
how
you
you
notice,
headwind
all
the
time
versus
Taylor
wind,
just
the
second
it
kicks
in
and
then
forget
about
it
instantly.
B
The
same
effect
is
at
play
here,
like
you
just
see
oh
wow,
they
solve
this
insanely
complex
ticket.
I
could
never
do
that,
but
what
you
don't
see
is
that
other
person
crying
in
front
of
their
desk
because
they
didn't
even
know
what
to
to
respond
like
exaggerated,
of
course,
but
that's
that's
something
to
to
keep
in
mind
like
we
are.
All
none
of
us
is
an
actual
magician
right.
A
A
B
Even
even
things
that
seem
small
or
unimportant
so
I
mentioned
the
the
weekly
agenda
document
thing
earlier
so
fairly
early
on,
like
I
added
automation
there.
Now
you
don't
have
to
manually
copy
and
paste
the
agenda
template
in
there.
It's
a
tiny
thing,
but
I'm
happy
every
time,
I
see
it
being
used.
It's
just
yes,
I
guess
it's
probably
recently
biased,
but
in
the
in
the
past
months,
I've
added
two,
the
new
tools,
slash
scripts
to
The
support.files.
A
B
Time
and
it
just
like
this
tool
cuts
it
down
to
seconds
it,
probably
it
before
it
was
30
to
60
seconds.
It
wasn't
even
that
long
before
I
guess,
but
still
now
it's
like
three
seconds
and
I'm
done
like
I'm
back
where,
where
I
need
it
with
with
tabbing
to
the
terminal,
doing
it
like
it's,
it's
amazing
I,
love
that
the
second
is
to
easily
add
custom.
B
Emoji
reactions
to
to
gitlab
issues,
merge,
requests
comments,
that's
also
in
large
Parts
about
efficiency
like
like
I
did
that
before
using
like
curl
commands
with
the
gitlab
API
manually.
Basically,
but
it
wasn't
efficient
to
go
back
to
my
history
and
look
it
up.
Oh,
what's
command
again,
replace
stuff,
so
I
wrote
a
tool
where
I
just
put
the
parameters
and
I'm
done
with
it,
and
it's
not
so
much
about
efficiency
here.
B
A
B
B
Amazing
right
and
yeah
I,
just
with
the
Emoji
thing,
I
hope
more
people
being
able
to
easily
use
it
will
will
make
it
more
visible
that
we
actually
have
this
functionality,
because
a
lot
of
people
don't
know
about
it
right.
But
when
you
see
wait
a
second,
that's
not
one
of
the
normal
Emoji.
How
did
that
get
there
I'm,
just
hoping
that
the
future
improvements
in
the
product
itself
might
might
happen
because
of
more
awareness.
A
So
cool,
that's
awesome.
I'll!
Definitely
link
to
that
script
in
the
description,
so
people
can
check
that
out
because
custom
emoji
are
very
cool
right.
The
Emoji
are
cool
too
okay.
So,
while
we're
talking
about
changes,
would
you
talk
me
through
a
change
that
you
helped
to
implement?
That
was
like
difficult
but
ultimately
worthwhile.
If
you
have
like
an
example.
B
B
We
want
to
measure
our
impact
on
the
product,
I
guess
so,
whenever
we
do
changes
that
are
outside
of
our
support
internal
stuff,
we
put
a
label
on
that
support
team
contribution,
and
that
was
a
manual
thing
for
a
while
and
at
some
point
I
guess
the
light
bulb
went
on
in
my
head
and
I
thought
wait,
a
second.
Why
are
we
doing
that?
Manchester?
We
have
all
that
information
available
like.
B
A
yaml
file
where
I
can
look
up
that
I,
my
user
account
is
part
of
the
support
team.
So
what
gives-
and
we
already
knew,
of
course
from
from
our
day-to-day
work,
that
a
ton
of
stuff
is
being
done
automatically
that
is
very
similar,
so
I
knew
okay,
that
it
must
be
possible
somehow,
and
it
wasn't
that
tricky
on
a
technical
level
to
figure
out.
How
is
how
do
these
automations
work?
How
do
I
make
one
that
does
this?
B
It
was
a
little
tricky,
it
was
I,
think
more
tricky,
or
how
do
you
say
institutional
wise
like
who
is
maintaining
that
stuff?
Who
do
I?
Ask?
Can
I
add
this?
Can
you
review
my
change
like
that?
That
was
a
little
tricky
right,
I
mean
we
have
the
everyone
can
contribute
Mantra,
but
it
can
still
be
tricky
in
practice,
because
this
is
not
something
I
I
do
a
lot
so
the
project
where
I
had
to
add
this.
B
They
did
have
contribution,
tips
and
and
read
me
and
whatnot,
but
I'm
so
far
removed
from
that
that
it
didn't
help
me
enough
for
it
to
be
really
easy.
But
that's
final
right:
there
is
a
a
line
you
have
to
find
like.
They
can't
explain
to
me
how
our
spec
tests
work,
like
they
just
say:
here's
how
you
run
your
RS
back
test
that
didn't
help
me
much
because
I
don't
know
how
to
write
our
spec
tests
right.
A
B
Giving
it
credit,
because
now
thinking
back
to
it,
I
I
implemented
at
least
two
different
versions
of
it
and
then
found
out
that
the
first
one
was
just
super
inefficient
and
that's
when
I
then
started
doing
it
in
the
way
that
I
described
now.
I
did
write
up
a
a
little
well,
not
really
blog
post,
but
an
issue
about
that
Journey,
but
I
just
found
out
that
that's
only
internally
visible
for
for
team
members.
So
I
wasn't
actually
aware
of
that.
A
That
change
was
really
helpful
because
there's
an
email
that
goes
out
at
the
end
of
each
week,
the
disc
that
says
hey.
This
is
human
support,
added
things
and
I
I,
really
like
being
on
that
email
and
I
definitely
noticed
the
impact
of
your
change,
because
I
as
much
as
I
like
as
much
as
I
like
being
in
that
email
I,
would
miss
things
and
like
yeah,.
B
A
B
B
I'll
say
what
I
said
a
couple
of
times
during
that
book
club
and
I
still
feel
like
an
arrogant
prick
when
I
say
it,
but
not
much.
If
anything
in
that
book
felt
particularly
new
or
insightful
to
me
not
not
saying
anything
in
there
was
wrong
or
bad,
but
I've
all
the
time
thought
yeah
it
isn't
that
obvious.
Isn't
everyone
operating
like
that
and.
A
B
B
If
you
go
to
staff
plus
level,
you
will
need
to
look
for
for
work
that
serves
the
company
to
to
succeed,
and
that
means
a
bit
more
from
the
top
down
than
from
the
bottom
up,
then
I'm
probably
used
to
I,
will
say
that
I'm
not
sure
how
true
that
is
particularly
here
at
gitlab,
because
we're
not
quite
like
a
lot
of
other
places.
I
still
think
it
is
also
true
at
gitlab.
B
A
Yeah
I,
like
that
python,
a
lot
you
mentioned
relationships-
I,
don't
know
if
I
mentioned
this
to
you,
but
I
wound
up.
This
is
just
a
quick
note:
I
went
up
in
a
coffee
chat
with
someone
outside
of
gitlab
who
had
seen
the
staff
Engineers
path,
book,
club
videos
and
read
along
with
the
book
and
I
was
like
oh
my
gosh,
so
we
were
kind
of
in
a
book
club
after
the
book
club.
It
was.
B
A
Yeah
cool
beans,
okay,
morph
I,
so
we
are
like
approaching
the
end,
so
just
have
like
fun
questions.
All
the
questions
are
fun,
but
I
have
even
more
fun
questions
left.
Okay,
so,
and
this
ties
into
sort
of
what
you
were
saying
about
The
Works,
that
you
do
being
important
to
you,
which
to
me
also
sounds
like
fun.
You
talked
about
enjoying
work
and
stuff
like
that
yeah.
So
one
of
the
things
I
like
about
working
at
gitlab
is
it's
fun
and
we
get
to
do
fun
projects
so
I'm
curious.
B
B
B
I
have
to
do
all
that
manually
in
the
config,
and
we
can
automate
that.
That's
that's
the
idea
here
and,
like
that's,
that's
a
whole
thing.
First,
I
myself
had
to
figure
out
like
okay.
How?
How
do
we
do
this
like?
What
would
the
structure
for
that?
Even
look
like
I
had
no
idea
I'm,
not
very
I'm
super
new
to
terraform
right.
B
So
that's
an
exciting
thing
for
me
to
learn
as
well,
but
that
also
makes
it
take
a
while,
because
I
need
3D
I
need
to
dedicate
focused
time
if
I
want
to
to
make
an
impact
there,
as
opposed
to
a
lot
of
things
where,
if
I
just
have
10
minutes
in
between
meetings
or
or
so
I
can
just
knock
out
a
docsmr
like
that's
just
bam
done.
That's
not
this
kind
of
thing.
B
A
You
talked
about
like
time,
investment,
I'm,
gonna,
guess
something,
and
you
tell
me
if
I'm
right
or
not,
but
I,
think
choosing
something
like
terraform
that
you're
not
extremely
comfortable
with
investing
the
time
on
it
for
that
project
with
Ulysses
is
also
for
that
project
with
Ulysses.
But
you
also
have
this
like
residual
benefit
of.
You
have
a
whole
bunch
of
experience
about
terraform
for
tickets
that
we
get
about
terraform.
So
it's
one
less
thing
about
category
of
you.
A
B
B
So
we
have
a
history
of
all
the
meetings
we
had
to
work
on
tickets
together
and
naturally,
at
some
point,
someone
I
think
it
was
Cynthia
created
a
template
with
a
list
of
all
the
sport
engineers
in
the
team
where
you
could
like
make
a
checkbox
when
you
have
had
a
pairing
with
someone
so
like
a
little
gamification
to
to
motivate
you
to
meet
more
people
on
the
team
and
again
you
you'll
probably
start
seeing
a
pattern
here
at
some
point,
I
thought
to
myself:
wait
a
second.
Why
am
I
measuring
this
manually?
B
B
Is
it
played
out
quite
a
bit
differently
than
I
had
originally
thought
it
would
in
the
sense
that,
like
we
learned
that
we
were
really
well
together,
async,
my
my
when
I
pitched
this
we
said
like
we're,
gonna
spend
eight
weeks
on
on
a
project.
We're
gonna
have
like
an
hour-long
meeting
each
week
and
focus
on
this.
B
Pair
programming
or
stuff,
but
that's
kind
of
how
I
envisioned
it,
but
we
were
both
so
motivated
that
most
of
the
work
just
happened,
async
outside
of
that
planned
sync
meeting,
and
we
wound
up
not
really
needing
that
meeting
like
we
used
it
for
project
management
and
and
meta
discussions
in
the
end,
but
we
could
have
done
without
almost
all
these
sync
meetings.
I
think
there
were
those
they
were
probably
necessary
for
a
couple
of
discussions.
B
So
I
think
there
was
some
value
for
sync,
but
that
was
interesting
to
me
like
it
as
I
said
it
really
played
out
differently
than
I
had
imagined
it,
and
then
also
I
mentioned
this.
With
the
with
the
support
team
contributions.
Label
thing
everyone
can
contribute,
I
I
would
also
have
said
everyone
can
contribute
to
this
project
after
I.
Had
this
initial
draft
out
that
we
now
improved
on-
and
that
was
true
like
I-
would
have
been
delighted
for
a
merge
request.
B
B
A
Yep
absolutely
I
that
was
like.
Maybe
the
closest
I've
been
to
a
refactor
like
before
and
after
and
yeah
I.
We
could
probably
go
back
and
look,
but
I
was
able
to
contribute
to
it
much
more
once
the
refactor
was
done
because
I
was
like
okay,
there's
individual
functions
and
Doc
strings
and
I
am
not
worried
about.
What
is
this
massive
line?
Doing
except
lots
of
loops
and
yeah?
It
looks
great
now
so
I
think
I
did
a
great
job:
cool
okay,
so
I
have
a
couple
like
fun,
just
nerding
out
questions.
B
A
B
Right
because
I'm
I
was
coming
from
a
web
dev
background
and
like
even
before
we
switched
to
gitlab,
we
did
have
custom
test
environments
for
each
branch,
but
again
the
integration
like
just
having
the
URL
right
on
the
merch
request.
It's
just
amazingly
useful
and
I
guess:
I!
Guess
why
I
like
CI
and
pipelines
so
much
in
general
is
it's
kind
of
an
extension
of
of
the
command
line
interface
to
go
back
to
my.
A
B
Answer
right,
so
whatever
I
Madness,
I
I
cook
up
in
my
terminal
I,
can
then
put
it
into
a
script
and
in
a
pipeline
and
it's
the
opportunities,
the
possibilities
just
explode.
I
can
do
so
much,
of
course,
for
for
simple
things:
I
could
also
just
put
it
in
a
Cron
job,
I
know
but
like
having
the
job
logs
right
there,
where,
where
I'm
also
then
versioning
the
script.
It's.
A
B
B
A
B
It's
not
zero,
okay,
I
guess
one
I
mean.
Let
me,
let
me
tell
you
a
little
story.
It
took
me
quite
a
while
to
get
docker.
I
will
freely
admit
that
I
was
a
lot
of
it
on
Docker
for
a
long
time.
I
like
I
saw
people
gushing
over
it
and
I
was
thinking
I,
don't
get
it
what
it
sounds
so
dumb?
Why
don't
you
just
spin
up
a
virtual
machine
like
this
doesn't
make
any
sense
this
there
is
this
text
file.
You
know
what
the
heck
is
compose.
A
B
It
on
a
on
some
level,
I
understand,
kinda,
and
it's
probably
harder
for
that
moment
to
happen
because
I'm
not
a
big
Enterprise
right
right,
but
still
oh
yeah,
I,
don't
know
a
lot.
A
lot
of
big
Enterprises
I
think
also
didn't
have
that
moment,
but
are
still
using
kubernetes
for
some
reason.
I
guess
that
adds
to
my
frustration
then,
but
yeah.
A
B
It
is
so
I.
Let
me
begin
with
JQ,
which
is
very
well
known
and
I
would
argue,
is
probably
the
most
important
piece
of
of
glue
of
the
last
decade.
I
mean
everything
is
Json
now
and
JQ
is
what
brings
Jason
in
the
terminal.
Right
I
mean
sure,
there's
Alternatives
then.
But
what
do
you
do
without
check
you?
B
B
It's
amazing
makes
everything
pretty
yes,
the
key
chain
tool
not
to
be
confused
with
the
Apple
keychain
thing,
I
think
the
keychain
command
or
tool
comes
from
fun2
and
it's
it's
basically
a
front
end
to
to
managing
your
SSH
keys
and
adding
them
to
the
SSH
agent,
so
that
you
don't
have
to
type
in
your
passphrase
all
the
time,
I'm
pretty
sure
that
there
is
much
easier
Alternatives,
but
I've
never
really
bothered
understanding
them
because,
15
years
ago,
I
Googled.
How
do
I
do
this
found
keychain?
It's
amazing.
B
It's
been
in
my
DOT
health
ever
since,
and
I
never
have
to
type
in
my
passphrase
more
than
once
after
rebooting
super
useful
Auto
SSH
is
like
a
wrapper
around
SSH
which
just
reconnects
if
the
connection
dies,
which
is
super
useful
if
you're
on
spotty
Wi-Fi
or
something
diff.
So
fancy
is
also
something
that
a
lot
of
people
use.
B
I
will
I
will
get
us
censored
at
the
end
and
I
will
say
the
the
tool
is
also
amazing
when
you
have
a
typo
in
your
command
and
it
gives
an
error
or,
if
you
so,
the
most
com.
Honestly,
the
most
common
use
case
is,
you
have
forgotten
to
add
the
Upstream
Branch
yet,
and
you
want
to
push-
and
it
says:
I
don't
know,
and
it
already
tells
you
did
you
mean
and
yes
I
know.
Git
now
has
added
a
option.
A
B
B
A
Awesome
cool,
thank
you.
So
that
concludes
the
set
of
questions
that
I
had
prepared.
So
like
thank
you
for
the
time
and
for
being
so
open,
like
you
shared
a
lot
that
is
going
to
be
on
the
internet
for
the
foreseeable
future.
So
thank
you
before
we
wrap
do
you
have
any
like
parting
words
that
you
would
like
to
share?