►
From YouTube: 2021-03-31 Create:Code Review Weekly Sync
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
First,
one
up
is
just
two,
mrs,
and
the
only
reason
I
put
them
here
is,
I
think
the
first
one,
andre
and
pedro
is
on
your
plate
to
review,
and
just
so
we
can
get
that
merged
or
if
there's
contention,
I
think
otherwise,
michelle's
already
looked
at
it,
and
then
we
can
get
that
moving.
The
second
one
is
mostly
for
pedro,
although
I
think
it's
helpful
to
the
rest
of
the
group
we're
trying
to
build
out
and
I've.
A
It's
still
called,
I
think
the
ownership
model
stuff,
but
it
might
like
be
more
loosely
a
cross-stage
features
and
just
sort
of
a
different
way
of
thinking
about
them.
But
we're
trying
to
build
out
how.
A
Other
groups
can
work
with
code
review
to
contribute
features
into
code
review.
So
if
you
have
thoughts
on
the
second,
one
feel
free
to
drop
them
in
the
goal.
Is
that,
like
you
know,
groups
who
want
to
add
a
widget
to
the
merge
request?
We
sort
of
have
like
a
process
for
what
that
looks
like
and
how
much
product
or
our
engineering
or
our
design
needs
to
be
involved
or
sort
of
pay
attention
to
those
things
versus.
A
You
know
other
features
that
might
be
more
complicated
where
we're
not
informed
or
we're
not
well
consulted
that
we
just
want
to
be
ahead
of,
and
so
we're
just
trying
to
build
out
a
way
to
think
about
that.
So,
if
you
have
thoughts
on
that,
one
feel
free
to
add
them
there.
While
we
continue
to
build
that
one
out.
A
B
Yeah,
thank
you
guy
for
pushing
for
these
yeah
on
on
the
first
one,
the
exploration,
experimentation.
What
do
you
anticipate
any
pushback
from
leadership
or
any.
B
Moving
not
not
completely
losing
focus,
but
not
being
so
focused
on
on
shipping
and
throughput.
A
In
reference
to
the
first
one,
the
like
the
yes,
no,
I
think
my
understanding
and
michelle
and
pedro
can
correct,
or
michelle
and
andre
can
correct.
Is
engineers
are
sort
of
benchmarked
to
do
x
number
of
mrs
per
milestone
and
it
it
actually
doesn't
say
like
what
those
mrs
have
to
be
or
that
they're
designed
to
be
deliverable
work.
I
think
it
does
say,
like
engineering
is
technically
responsible
for
delivering
planned
work.
A
But
as
a
group,
I
think
if
we
all
decide
that
there's
this
is
the
planned
work
we
care
about,
and
this
is
other
work
engineers
will
still
hit
their
mr
goal.
It
just
might
not
be
in
what
product
and
design
or
you
know
wants
to
focus
on.
The
goal
is
that
we
want
our
engineers
to
go
and
explore
and
try
things
and
come
up
with
something
new
in
an
effort
to
like
make
the
product
better.
So
I
don't.
A
I
don't
think
so.
It's
not
a
concern
that
I
have.
I
feel
like
this
group
we're
in
a
better
spot
in
our
planning
and
we've
cycled.
It
we've
dialed
it
back
to
like
what
we
think
we
can
achieve,
and
this
will
take
a
small
fraction
of
that
off
the
top
just
to
to
give
this
extra
space,
and
I
think
engineers
will
still
have
sort
of
all
of
the
space
they
need.
But
yeah.
I
think
that's
really
a
question
for
andre
and
michelle.
C
Yeah,
I
think,
you're
right.
I
think
if,
if
anything,
we
do
have
an
okr
around
the
say
do
ratio
you
want
to
keep
that
at
a
certain
level,
but
the
10
exploration
work
doesn't
mean
that
it's
not
scheduled,
they
can
reserve
it,
but
we
can
still
make
those
explorations
deliverable
like
we
have
the
spike
around
index.
To
be
this.
This
milestone
is
kind
of
like
what
those
10
would
cover.
C
Naturally,
and
I
do
think
in
the
end,
the
explorations
of
the
engineers
will
result
in
a
better
delivery
of
product
features,
so
I
think
we're
all
in
the
same
boat,
all
the
same
direction,
and
I
don't
anticipate
leadership
either
product
or
engineering
to
even
resent
any
of
this,
because
it's
it's
all
for
the
same
goal:
we're
just
giving
more
autonomy
to
ics
to
go
out
and
explore
and
go
out
and
experiment.
So
the
biggest
question
right
now
that
I
still
haven't
gone
through
that
in
mri
and
I
apologize
for
the
delay-
is
exactly.
C
Should
we
formalize
that
in
do
they
just
do
it
and
just
let
us
know
later,
do
we
somehow
prepare
a
pile
of
work
for
them
to
work?
On
do
sorry,
do
we
agree
upon
the
explorations
that
they
should
take
that
sort
of
thing,
but
that
comes
naturally
organically
on
the
team
anyway,
so
maybe
we
couldn't
let
it
loose
but
I'll
I'll
sit
down
and
take
a
read
and
update
the
mr
but
yeah
sounds
good.
A
It
says
in
the
mr
that
we
won't
pick
the
work
it
gives
suggestions
and
people
don't
know
what
to
work
on
like
things
that
we
would
naturally
care
about,
like
the
list
of
like
pre-filtered
searches
of
labels,.
C
Change
but
they're
so
invested
in
the
products
like
the
tackling
of
technical
debt
in
any
way
that
it
will
naturally
go
around
what
we
already
want
to
work
on
anyway.
So
I
think
it's
not
an
issue
yeah.
I
agree
michelle
anything
to
add.
C
C
This
is
one
of
those
cases
that
we
have
been
operating
under
the
learnings
already,
but
for
the
sake
of
completion
and
wrapping
it
all
up,
I
did
capture
a
little
bit
the
thoughts
that
were
through
that
were
shared
on
that
retrospective,
about
the
the
highlighting
of
collapse
files.
It
was
already
dissected
on
the
iteration
retrospective
with
sid,
but
I
captured
here
the
the
learnings
and
the
conclusions
that
we're
kind
of
extracting
from
that
exploration.
C
It's
a
bit
thin
in
terms
of
collaboration,
but
I
do
think
we,
as
a
team,
already
discussed
this
on
multiple
forums,
but
I
try
to
make
it
capture
like
that.
Those
learnings,
if
I,
if
I
missed
anything,
please
feel
free
to
just
fill
it
in
post
closing
but
yeah.
Just
sharing
those
conclusions
there
any
questions
there,
no
iteration
respective.
E
C
Yeah
and
I
think
the
it's
like
capturing
the-
I
think
we
already
captured
a
lot
of
the
learnings
from
the
reviewers,
but
capturing
them
in
comments
will
will
be
worthwhile
for
the
future,
so
yeah
thanks
michelle.
I
will
also
bring
my
ics
to
take
a
look
at
the
reviewers
for
the
last
stretch.
Okay,.
B
Yeah,
thank
you
andre
this.
This
was
very
helpful
and
thank
you
for
sharing
these
conclusions.
I
agree.
I
think
I
think
it
was
mostly
just
the
lack
of
more
preparation,
perhaps
and
then
early
involvement
that
could
avoid
these
surprises
and
even
if
there
is
nothing
actionable
for
us
to
take
from
this,
like,
I
don't
know,
update
something
in
the
handbook
or
change
something
today.
B
I
think
just
the
fact
that
we
did
this
and
the
whole
team
is
sharing
the
same
story
and
they
have
heard
each
person's
perspectives
on
what
happened
and
what
each
side
was
seeing
as
a
good
thing
and
a
bad
thing.
I
think
that's
already
worth
it
because
it
it
keeps
the
team
closer
together
and
stronger.
So
I
I
appreciated
that
at
least
that's
my
feeling.
For
me,
I
don't
know
if
thomas
is
on
the
call
he's-
I
don't
think
not
today,
but.
C
Yeah
yeah
he
shared
his
views
there,
so
we
were
we're
good
thanks,
peter
moving
on
just
an
fyi,
so
that
everybody's
aware,
we've
already
shipped
the
code
review
process
update
for
dog
fooding
reviewers
thanks
so
much
michelle
amazing
help
and
collaboration.
C
Now
is
the
time
to
see
this
coming
to
fruition.
I've
already
caught
a
couple
of
mrs
that
are
not
following
the
new
process
and
I've
kind
of
like
gently,
nudged
them
and
corrected
the
signees
and
reviewers.
I'm
experimenting
to
see
the
people
reaction
to
it.
I
think
it's
going
well
from
what
I've
heard.
They
all
welcome
a
more
consistent
approach,
but
there's
going
to
be
people
that
misuse
it
or
haven't
heard
about
it.
So
I
think
we
can
all
help
out
in
broadcasting
even
further
I'll
keep
posting
reminders
on
slack
every
night
again,
cool.
A
Yeah
I'll
just
say
amazing,
I
think
it's
awesome
to
see
it
there
and
a
huge
thanks
to
david.
I
think
for
starting
it
and
getting
the
ball
rolling
on
that.
I
think
he
did
an
incredible
job
and
he
was
a
spark
gracefully
trying
to
handle
all
of
the
overwhelming
feedback,
but
I
appreciate
andre
michelle
you
stepping
in
to
get
it
across
the
line.
I
think
it
was
a
great
method
and
I'm
excited
to
see
it
there,
despite
despite
the
early
challenges,
I
think
I
think
it's
great.
C
Yeah,
thanks
guy,
I
I
definitely
appreciate
david,
taking
the
first
step
that
that
helped
us
make
this
across
the
line.
So
thanks
david,
if
you're
watching
right
mid,
milestone
check
in
very
quickly
I'm
sorry,
I
didn't
align
these
things,
but
it
looks
like
we're
not
on
on
track,
even
though,
with
the
current
assigned
issues,
sorry
scheduled
issues,
the
ones
that
have
been
moved
already
because
of
the
database
work
has
already
been
moved
out.
I
believe
so.
With
the
current
plan,
it
looks
like
we're:
okay,
we're
at
45
progress.
C
We
do
have
a
couple
of
spikes
on
on
progress,
not
only
the
one
that
thomas
is
exploring
but
indexeddb
and
for
clarity.
What
we're
trying
to
do
is
having
a
more
aggressive,
client-side
caching
for
immediate
data
loading
instead
of
coming
to
the
server
to
get
the
data
from
the
diffs
if
they
have
been
unchanged
since
the
last
visit,
we
have
some
theories.
C
Some
challenges
about
cash,
invalidation
security
as
well,
but
thomas
is
exploring
that
phil
is
taking
care
of
some
explorations
and
fixes
for
the
total
blocking
time
that
is
plaguing
the
large
mercury
quest
experience
and
he's
doing
some
uncovering.
That
will
materialize
themselves
into
issues
for
the
future,
but
I
think
that
would
might
delay
us
a
little
bit,
but
so
far
it
looks
like
we're.
Okay,
michelle
yeah.
C
I
I
can
totally
understand
that,
and
I
commend
you
for
all
your
efforts.
You've
been
amazing.
The
whole
company
owes
a
tremendous
debt
to
you.
So
thanks.
E
Very
dramatic,
but
I
appreciate
it
so
I
forgot
that
it
was
the
mid
milestone.
I
could
give
you
an
update,
but
it'll
probably
be
wrong,
so
I
think
yesterday
I
did
drop
four
issues
from
the
release,
I'm
keeping
the
planning
issue
as
the
single
source
of
truth,
but
I
don't
think
that
math
really
added
up,
because
I
think
we
added
like
nine
or
ten
database
issues
and
we
only
dropped
four.
E
The
reason
is
because
there
were
so
much
work
already
in
flight
with
the
workflow
labels
that
I
didn't
want
to
drop
it,
and
so
I'm
talking
to
people
throughout
the
week
yesterday
I
talked
about
this
waiting
for
filter
and
touch
base
with
david
on
that,
so
the
team
will
be
updating
their
labels
and
I'm
going
to
start
dropping
more
stuff.
Here's
the
good
news,
though
we
have
four
database
issues
left
still
that
need
to
be
started
and
one
other
issue
that
is
very,
very
bad.
E
So
if
we
can
figure
out,
maybe
like
a
thing
that
we
can
do
to
bring
all
five
of
those
issues
down
this
week,
then
we
can
create
a
follow-up
to
make
that
more
scalable
in
the
future.
But
we
can
close
all
five-
I
I
don't
know
if
that
will
happen,
but
that
is
an
option
that
we
have
right
now.
E
A
No
just
echo
andres.
Thank
you.
I've
seen
all
the
updates
in
the
planning
issue
and
all
the
other
work,
and
I
know
this
was
a
a
wrench
thrown
into
the
plans.
I've
I've
actually
appreciated
the
break
sort
of
it
felt
like
not.
A
lot
was
going
on,
so
I
was
able
to
look
into
and
do
some
other
things.
A
You
know
all
the
dvd
work
was
going
on,
so
I
it's
felt
like
it's
been
covered,
so
well
that
I
just
I
don't
even
worry,
and
I
it's
been
a
nice
stress
reliever
for
me,
I'm
sure
it's
not
feeling
that
way
on
your
side,
but
it
thanks
for
me
for
that.
E
Thank
you
also,
I'm
I'm
super
optimistic
about
this.
It
seems
like
really
bad
news,
but
I
think
we'll
be
fine,
and
so
I'm
really
optimistic
about
this
being
a
wrap-up
week.
We
have
a
huge
epic,
but
the
other
groups
have
picked
up
our
issues
and
so
yeah,
I'm
feeling
good.
C
And
great
things
will
come
out
of
this
too
for
the
future.
From
what
I
can
see,
I
already
see
some
movements
gary
discussing
some
things,
an
architecture
perspective,
so
looking
forward
to
see
that
too
cool
so
moving
on
a
bit
of
announcement.
So
in
efforts
to
make
people
more
collaborative,
seen,
synchronizing
defeat
the
barrier
of
remote
and
time
zones,
the
front
end
team
is
experimenting
with
something
next
week
or
starting
an
experiment.
C
Next
week,
this
comes
from
the
engagement
survey
that
we're
trying
to
get
a
bigger
sense
of
a
team
but
I'll
be
making
I'll
be
putting
a
slot
on
the
calendar
of
code
review
that
will
be
making
me
and
my
team
available
for
just
anything,
really
it's
optional
attendance,
but
the
idea
is
that
I'll
be
doing
backlog,
refinement
there.
It's
just
going
through
issues.
C
Ics
can
join
me
in
that
to
help
planning
more
synchronous,
tough
issues
we'll
do
it
we'll
use
it
for
more
informal
discussion
as
well
hanging
out
just
be
seen
a
little
bit.
I
don't
know
about
the
time
zones.
If
that
works,
it's
just
an
experiment.
I
just
want
to
let
you
know
you're
all
welcome
to
stop
by
and
say
hi
it's
in
the
calendar.
I
hope
that
I
added
a
zoom
link,
so
let
me
know
if
it's
not
there,
but
you're
all
welcome
okay,
cool
and
with
that
pedro.
B
Yeah
thanks
for
for
that
initiative,
I
hope
it
goes
well.
Yesterday
I
was
talking
with
austin
the
product
designer
for
compliance
and
he
has
a
an
office
hours
for
ux
and
now
he's
turned
that
into
an
async
thing.
So
I'm
keeping
an
eye
for
these
office
hours
initiatives
to
see
if
it's
something
valuable
for
me
and
for
our
group.
So
let
us
know
how
it
goes
and
how
you
use
that
time
and
if
it's
helpful,
but
thank.
B
Cool
yeah,
an
fyi
about
the
external
survey,
so
we
closed
it.
There
are
more.
This
is
like
a
preliminary
view
of
this
survey.
There
are
more
comments
that
I
made
on
yesterday's
ux,
sync
that
you
can
see
in
the
agenda
below,
but
to
build
it
really
quickly.
We
got
a
lot
of
responses
more
than
we
were
hoping
for.
So
that's
great.
The
top
problem
is
the
same.
B
That
was
identified
in
the
internal
survey
dealing
with
large,
merge
requests
and
furthermore,
that
was
reinforced,
or
at
least
the
performance
theme
was
reinforced
in
the
open
text
responses.
So
I
think
we're
making
the
right
call
in
shifting
some
gears
and
prioritizing
that
work.
Not
everything
is
bad.
We
had
a
lot
of
praises
for
multi-line
comments,
marking
his
view,
suggestions
and
reviewers.
B
There
were
even,
although
I
didn't
write
here,
there
were
a
couple
of
people
that
actually
praised
the
performance
and
said
like
this
is
really
fast.
I
I
love
you,
but
it's
not
slow
at
all.
I
yeah
they're
the
minority,
so
I
didn't
highlight
them
here,
but
it
did
happen
and
yeah.
So
we
had
a
lot
of
prices.
It
was
good
that
we
had
prices
for
the
reviewers
and
that
people
are
finding
it
valuable
as
well
in
their
own
teams
and
and
yeah.
C
No,
this
is
great
thanks
for
highlighting
these
things
and
the
performance.
As
we
know,
it's
an
ongoing
battle,
some
things
get
better,
but
that
is
code
review
in
a
nutshell,
our
audience
is
so
great
and
so
large
and
so
widespread
that
we
have
polarizing
experiences
everywhere.
We
touch
so
that's
that's
part
of
the
game
and
that's
why
we
love
it.
C
C
B
Awesome
yeah
and
then
I
added
another
point
just
now
that
I
remember
something
that
I've
been
thinking
about
more
is
we
had
a
discussion
in
that
issue
about
the
shared
key
results
for
code
review
for
the
next
quarter,
so
that
all
the
quad
product
group,
product
management,
engineering,
ux
and
quality
would
align
on
certain
key
results,
but
yeah,
I'm
thinking
if
we
should
have
performance
as
a
key
result.
Anything
like
you
know,
targets
to
beat
so
to
speak.
C
I
would
I
would
actually
say
that
performance
has
been
part
of
of
key
results
for
front
end,
at
least,
and
I
think
back
into,
I
think
what
we're
trying.
I
think
what
we're
dealing
with
right
now
is
that
some
some
kinds
of
mrs
are
faster
while
others
are
slower,
and
I
think
we
as
a
group
need
to
start
drilling
down
more
on
the
large,
mrs,
as
we've
seen
from
the
usability
from
the
feedback,
new
hacker
news
and
all
that
stuff.
C
So
I
think
that's
a
prime
example
for
a
shadow
kr,
because
there's
tooling
improvements
that
we
can
do
on
the
quality
side.
There's
security
as
well.
I
guess,
but
I
feel
like
this
is
great
so
definitely
goes
in
line
with
what
we
were
thinking.
E
No
just
what
I
wrote
here,
we
definitely
include
quality,
but
I
I
will
say
I
I
didn't
know
you
added
a
comment.
You
said
to
double
down
on
performance
optimizations.
Last
week
michelle
suggested
reduced
load
time
on
large,
mrs
by
a
percentage
totally
agree
with
that.
Let's
circle
back
to
this
thread
async
and
see
if
we
can
come
up
with
a
percent-
and
maybe
it's
arbitrary,
but
that's
something
for
us
to
like
rally
behind.
B
Yeah
exactly
yeah,
I'm
not
sure
what
it
would
be.
I
defer
that
to
you,
but
I
also
don't
yeah.
I
I
this
is
not.
This
is
like.
D
B
Open
question
because
I
also
don't
want
to
put
too
much
pressure
on
on
on
everyone,
because
we
already
have
other
key
results
and
there
are
other
things
that
we're
doing.
But
since
we
it's
a
recurring
theme
and
yeah,
we
all
know
that
we
need
to
do
better
work
on
performance.
D
B
D
B
Awesome,
thank
you
for
for
for
sharing
yeah
from
the
comments
and
and
from
myself
I'll
also
be
away
on
friday.
It's
I
think
it's
a
public
holiday
in
many
countries
around
the
globe,
so
so
yeah.
E
A
Thanks,
everyone
have
a
good
rest
your
week
and
rest
your
day
enjoy
the
time
off
youtube,
bye,.