►
From YouTube: CEO Shadow learning recap from Shane Rice 2021-02-19
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hey
everybody
shane
rice
here
and
I'm
just
wrapping
up
my
ceo
shadow
rotation
and
my
three-year-old
is
in
the
office
with
me,
so
she
may
interrupt
here
in
a
second,
but
I
just
want
to
do
a
quick
recap
on
some
of
the
things
I
learned
and
the
highlights
for
meme
and
so
I'll
get
right
into
it.
A
A
It's
easy
to
zero
in
on
that
and
kind
of
not
have
the
zoomed
out
view
on
just
how
ambitious
what
gitlab
is
trying
to
accomplish
is,
and
so,
as
a
shadow
I
sat
in
so
many
calls
that
reminded
me.
You
know,
while
we
focus
on
small
changes
today
we
focus
on
iteration
today.
You
know
our
goal
as
a
company
is
still
to
make
something.
A
Everyone
in
the
world
can
use
to
do
their
work
far
into
the
future,
not
just
developers,
not
just
ops,
not
just
security,
but
you
know
make
it
as
usable
for
everybody
as
possible,
so
every
organization
can
use
gitlab
to
get
as
much
done
as
we
get
done,
and,
and
so
that
was
really
inspiring-
and
I
think
a
corollary
to
that
is
being
in
meeting
after
meeting
with
sid.
A
One
of
the
things
that
I
come
away
with
is
just
how
ambitious
he
is
personally,
both
in
his
role
as
ceo
of
gitlab
and
the
mission
of
get
lab,
but
also
the
things
that
he's
excited
about.
You
know,
charter
cities,
you
know
considerate,
the
game
that
he's,
you
know
been.
You
know
contributing
towards
and
and
working
on
with
a
team
that
is
outside
of
get
lab
and
his
other
areas
of
interest
and
other
investments.
A
It's
just
been
really
great
to
see
where
he
puts
his
interest
outside
of
gitlab,
as
well
as
to
our
core
mission.
So
you
know.
For
me
this
is
a
remote
rotation.
Obviously,
and
so
I
hesitated
to
sign
up
during
the
remote
rotations
just
because
I
really
wanted
to
spend
time
in
san
francisco,
I
wanted
to
have
those
face-to-face
interactions
with
you
know
everyone
that
was
involved
in
those
meetings
as
much
as
possible,
and
you
know
to
visit
san
francisco.
A
You
know
it's
a
really
neat
city,
there's
lots
to
see
and
explore,
and
you
know
every
time
I
go,
I
experienced
something
new,
so
you
know
I
was.
I
was
kind
of
looking
forward
to
being
able
to
do
that.
Maybe
one
day,
but
you
know
looking
at
it
now
being
remote,
was
a
big
benefit
for
me
because
it
built
in
time
for
me
to
process
things.
So
I
am
naturally
talkative.
You
know
extrovert,
and
so
I
tend
to
fill
space
with
conversation.
A
So
you
know
if,
if
I
have
down
time,
you
know
I'd
probably
find
something
to
talk
about
whether
it
was
it
might
not
be
the
last
meeting
it
might
be.
You
know
some
other
meeting
or
some
other
topic
that
came
up
in
the
meeting.
You
know
just
there's
no
telling
so
for
me
to
be
able
to.
You
know
go
into
a
call,
you
know,
maybe
even
a
block
of
calls
and
then
come
out
of
that
with
30
minutes
in
my
office.
A
It
helped
me
to
focus
on
processing
what
I
just
heard
and
kind
of
you
know
incorporating
that
into
my
understanding
of
gitlab
our
mission,
those
things
so
I
think
that's
been.
You
know
something
that
I
thought
I
wouldn't
enjoy
as
much
as
really
been
a
big
benefit
for
me.
I
think
you
know
another
aspect
of
the
remote
program.
For
me,
that
was
a
little
challenging
is
family
time.
You
know
I'm
in
the
central
time
zone
so
yeah
I
made
the
shirt
made
sure
to
start
my
days.
A
At
the
same
time,
sid
did
so
that
gave
me
a
couple
extra
hours
in
the
morning
with
the
family,
but
you
know
some
of
sid's
calls.
Some
of
that
schedule
does
kind
of
bump
up
against
bedtime
for
a
three-year-old,
and
so
we
had
to
kind
of
navigate
that
my
partner
and
I
and
everything
worked
out.
Fine,
it
wasn't
anything
where
family
suffered.
I
did
keep
family
first,
the
entire
time,
but
even
keeping
family
first.
There
are
stressful
moments
in
that,
and
so
just
something
to
think
about.
A
If
you're
thinking
about
the
program
is
just
making
sure
you
can
communicate
clearly
those
expectations
and
and
what's
happening,
you
know
when
I
you
know
the
sunday
before
I
was
going
into
the
program.
I
reminded
my
partner.
I
was
doing
the
ceo
shout
out
and
she
was
like
okay,
I
was
like
well,
you
know,
I'm
gonna
be
working
like
from
10
to
seven.
Instead
of,
like
you
know,
8
30
to
5
and
she's
like
what
and
so
that's
kind
of
on
me,
I
didn't
communicate
the
the
time
difference
with
her.
A
But
again
we
were
flexible,
everything
worked
out
and
then
finally
yeah.
I
think
one
of
the
things
you
know
when
I
was
looking
at
the
handbook
page
and
going
into
the
week
I'm
a
little
competitive,
and
I
try
not
to
let
that
drive
me
too
much,
but
it's
there,
and
so
I
want
to
crush
the
number
of
merge
requests
during
my
rotation
and
I
don't
think
we'll
be
close
on
on
either
week
to
highs.
A
But
part
of
me
wonders
if
this
is
probably
a
function
of
you
know
taking
in
a
part
of
a
program,
that's
kind
of
matured
and
iterated
a
lot
from
its
early
beginnings
and
so
yeah.
So
I
you
know,
we've
made
lots
of
merge,
requests
lots
of
great
changes.
You
know,
probably
the
most
exciting
bit
for
me
yesterday
was
being
on
a
learning
and
development
call.
A
Q
a
was
sid
and
the
learning
and
development
team,
and
at
you
know
after
we
finished
the
q,
a
said
turned
around
and
asked
lauren
my
co-shadow
and
I
to
write
a
blog
post
about
you
know
giving
and
receiving
feedback
and
then
including
the
video
from
that
session,
and
it
was.
It
was
really
cool
because
we
got
to
use
the
netlify
cms.
That
lauren's
been
working
on
and
the
digital
experience
teams
been
working
on
and
my
keyboard's
right
here.
Oh
you
mean
the
keyboard.
A
You
play
music
on
it's,
it's
put
up
I'll,
get
it
out
later.
Okay!
Well,
because
I
didn't
have
room
for
it
on
my
desk,
so
those
are
just
you
know.
Looking
back
over
the
two
week
period.
Oh
also,
one
of
the
things
happened
for
me
was
my
rotation
was
split,
so
I
had
one
week
and
then
there
was
sales
kickoff
and
then
my
second
week
was
this
week
and
I
wonder
if
it
might
not
be
helpful
to
to
build
in
an
opportunity
to
have
that
kind
of
break.
A
Just
because
you
know
you
still
get
to
teach
someone
you're
still
learning
from
someone
that
first
week,
but
that
week
in
between
gives
you
an
opportunity
to
come
back
to
one
week
of
work
at
a
time
instead
of
coming
back
to
two
weeks
of
you
know,
issues
to
dig
through
and
things
to
catch
up
on.
So
it
gives
you
a
little
bit
of
a
you
still
have
you
know
things
to
kind
of
catch
up
on
and
it's
not.
A
You
know
yeah,
my
team's
taking
care
of
a
lot
of
things
that
we
would
normally
work
on
together,
but
you
know
anytime
you're.
You
know
out
of
the
loop
of
your
regular
job.
You
just
have
those
things
that
kind
of
pile
up.
So
I
think
that
you
know
that
week
off
in
the
middle
is
actually
kind
of
helpful.
So
I'm
going
to
make
a
I
don't
know.
A
I
don't
know
if
it's
a
suggestion,
but
I'm
going
to
at
least
point
that
out
to
sherry
and
and
to
sit
as
well
that
you
know
it's
something.
It
might
be
something
to
consider
as
far
as
how
we
build
the
program
to
maybe
add
that
in
because
I
know
some
people
that
I've
talked
to
about
doing
the
program
are
really
concerned
about
the
just
the
amount
of
work
that
would
be
missed
if
they
were
out
for
two
weeks,
especially
if
you're
on
a
smaller
team
and
you're
a
critical
part
of
that
team.
A
So
so
yeah.
So
that's
my
impressions,
the
highlights,
I'm,
you
know
happy
to
answer
any
questions
and
I'm
going
to
finish
up
my
off-boarding
issue
now.
So
thanks
and
talk
to
you
soon.