►
From YouTube: 2022-12-13 Code Review UX 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
What
do
you
need
me
to
look
at
first
Annabelle,
my
my
to-do's
or
they're,
going
up
by
about
10
to
20
a
day
right
now
and
and
that's
with
me,
working
and
I'm
taking
a
week
off
at
the
end
of
the
year,
I
I
need
some
pointers
at
what
to
do
what
to
do
first,
What's
blocking
you
so
that
I
can
try
to
be
less
of
an
anchor,
but
also
this
is
this
question
is
more
for
Kai
I'm
gonna
bring
this
up
with
my
manager
as
well
on
on
Thursday.
A
B
To
answer
your
question:
what's
most
important
for
me
to
really
respond
to
I,
can't,
remember:
I,
don't
have
it
off
top
of
my
head,
because
I'm
usually
like
Amy.
What
do
you
think
or
Amy
how
about
that
thing,
since
this
is
kind
of
a
short
agenda,
do
you
like?
Do
you
want
to
look
at
your
to-do's
and
go
through
them
and
I
can
just
tell
you
which
ones
are
not
important,
that
I've
painted
you
on
or.
A
A
C
A
B
Okay,
yeah
I'll
just
go
through
them
and
write,
which
ones
are
important
and
one
of
them
that
last
one
is
just
me
thanking
you,
so
you
can
clearly.
B
If
it's
on
emerged
or
closed
call,
request
or
excuse
me,
merge,
request
or
issue,
then
just
clear
it
out,
it's
probably
not
important.
A
Kai
from
a
a
project
tracking
perspective,
do
you
have
any
suggestions
that
I
can
bring
back
to
my
team
to
trap?
How
do
we
track
this?
This
sort
of
work
that
doesn't
appear
in
merge
requests.
C
I,
do
not
it's
probably
a
good
question
for
Andre
or
Matt
that
feels
like
an
engineering
problem
question
of
like
they
are
similarly
I
guess.
Similarly,
I
did
not
know.
Tech
Raiders
were
done
this
way,
but
although
this
online,
we
think
about
things
they're.
Similarly
like
Benchmark
against,
like
merch
request,
throughput
yep.
A
B
C
So
I'm,
assuming
the
engineering
work,
has
a
way
to
deal
with
that
so
I
would
I
would
do
that
I
think
at
least
gives
you
a
place
to
start
I.
Don't
okay
I
mean
the
other
option.
Is
you
start
adding
labels
to
every
issue,
but
that
seems
weird
that
you
would
be
told
to
track
your
work
when,
like
others,.
D
C
It
feels
like
elitist
like
I,
don't
know,
I,
don't
want
to
say
that,
but
like
it
feels
weird
that,
like
you
would
have
to
say,
you
spent
this
much
effort
on
an
issue
and
Annabelle
and
I
would
not,
and
the
engineering
managers
don't
have
to
say
how
much
time
they
spent
talking
about
an
issue,
but,
like
other
people,
do
that
sort
of.
A
A
I've
advocated
in
the
past
to
my
managerial
team
that
I
think
long
term,
the
correct
answer
for
source
code
and
code
review
is
two
people
assigned
to
both,
but
I.
Don't
know
that
I'll
get
that
soon
or
ever,
because
we
can't
split
the
groups
and
I'm
starting
to
think
that
this
is
just
more
there's
more
work
here
than
one
person
can
do.
C
A
E
A
We
review
requests,
okay,.
E
So
when
I
don't
know
if
it
helps,
but
at
least
for
me
it
it
started
helping
at
first
I
thought
it
would
be
just
a
waste
of
time
and
inefficient.
But
after
some
time
it
started
gaining
value,
which
was
to
start
tracking
my
time
and
because
it's
not
so
much
the
number
of
things.
It's
the
time
that
you
spend
on
them.
Because
that's
you
can't
you
can't
break
down
sign
more
it's
just
time.
E
It's
where
everyone
on
the
planet
has
that
nothing
else
and,
and
so
I
started
tracking
time
on,
for
example,
the
the
time
that
I
spent
on
community
contributions
versus
reviewing
merge,
requests
for
the
current
Milestone
versus
attending
to
issues
in
the
Korean
Canal
stone
versus
pains
outside
of
so
every
time.
E
And
but
this
is
part
of
my
workflow,
because
I
I
compartmentalize
responding
to
pings
for
the
current
Milestone
and
responding
to
things
outside
of
the
grid
milestone,
and
so
that
allows
me
to
say
you
know
how
much
time
I'm
spending
outside
of
the
current
Milestone
versus
the
current
Milestone
or
even
between
issues
and
merge
requests
in
the
current
Milestone
and
but.
E
Because
of
the
way
that
I
structured,
my
work
I
have
a
specific
time
just
to
look
at
merge
requests
in
the
current
Milestone
and
then
I
stopped
doing
that
and
look
at
issues
for
example.
Of
course,
sometimes
I
need
to
look
at
both,
but
sometimes
I
can
make
that
separation
and
then
can
go
back
to
Marcel
and
say:
hey
I'm
spending
this
amount
of
time
or
even
saying,
like
I've
allotted
this
amount
of
time
per.
D
E
A
E
Because
the
assignments
don't
always
work
for
issues
right,
sometimes
your
opinions
on
an
issue
that
you
don't
own
like
you're,
just
there
to
give
an
opinion.
But
since
you
spend
a
lot
of
time
there
so
you're
not
going
to
assign
yourself
to
it
or
it's
an
issue
in
the
backlog
and
we're
still
figuring
out.
If
we're
going
to
do
it,
you're
not
going
to
assign
yourself
to
it.
E
So
the
assignments
for
issues
don't
work
as
well
as
review
requests
or
maybe
there's
a
way
for
you
to
to
search
your
Gmail
for
mentions
and
issues
in
a
certain
time
period,
and
you
could
say
this
month:
I
got
this
amount
of
Pinks
in
issues
or
something
like
that.
A
D
C
C
A
D
E
I
think
it
always
has
to
be
in
relation
to
something
you
know,
for
example,
the
Mr
rates
you
were
talking
about,
you're
evaluated
or
decisions
are
made
based
on
the
MRA,
because
you
can
compare
the
Mr
rates
across
teams
or
across
people.
E
If
you
want
to
start
looking
at
issue
beings
either
you
Implement
that
for
the
whole
team
or
of
course,
if
you're
getting
started,
you
just
do
that
for
yourself,
but
it
doesn't
say
a
lot
if
you're
getting
pings
on
10
issues
versus
five
merch
requests,
for
example,
it
just
says
or
you're
getting
paid
more
images
and
merge
requests.
E
A
E
A
E
Have
the
next
points
yeah
just
anything,
yeah
I'm
catching
up
on
two
months
away
from
git
lab,
so
you
can,
if
you
haven't
been
there
for
that
amount
of
time
out,
you
can
imagine
how
that
must
feel
but
yeah
so
far,
so
good.
It
hasn't
been
that
hard
as
I.
Imagine,
but
anything
that
the
people
here
in
the
group
feel
like
I
should
know
or
catch
up
on
as
soon
as
possible
or
even
discuss
right
now.
If
it's,
if
it's
something
urgent.
C
I
put
one
in
there,
I
feel
like
we
should
have
made
like
a
highlights
list
of
like
things
that
happened
in
interest
but
like
this
is
not
that
you
need
to
catch
up
on
immediately,
but
Andre's,
leading
a
new
series
of
like
performance
roundtables
that
they
meet
weekly
at
alternating
times.
But
you
know
worth
checking
out.
D
C
And
seeing
what's
being
discussed,
there
I
think
there's
some
interesting
ideas,
but
you
know
nothing
super
actionable.
Yet.
Okay,.
C
It
is
it's
on
the
code,
review,
calendar
and
I.
Think
it's
open
to
anyone.
I
know
he's
posted
about
it,
a
development
and
other
channels,
but
largely
the
participation
has
been
like
inside
of
the
code
review
group
and
so
we're
looking
for
primarily
opportunities
around
diff
performance
and
like
merchandise,
performance.
D
Yeah
awesome
cool
thanks
for
sharing
that.
E
Anything
else,
Ben
from
research
front
anything
that
I
should
really
know
about
or
I
will
probably
stumble
upon
a
lot
of
things
in
the
agendas.
But
you
know
yeah.
F
F
See
I've
been
working
on
the
report
for
the
Mr
intercepts
survey
that
we
started
and
has
been
running,
awesome
yeah,
it's
looking
really
cool
I,
don't
want
to
give
any
spoilers
yet,
but
good,
good,
yeah,
there's
some
some
good
nuggets
in
there
should
be
dropping
today
or
tomorrow,
I'm
just
waiting
on
a
few
charts
from
you
and.
E
Awesome
yeah
well
I'm,
just
so
well,
regardless
of
of
the
outcome,
I'm
just
so
happy
that
you
you've
been
able
to
to
work
on
that
and
just
to
have
something
you
know,
I
think
that's
that's
the
most
important
thing
for
me.
So
thanks
thanks
for
doing
that,
yep.
F
And
yeah
I
don't
know
if
you
and
Annabelle
have
talked
about
the
the
Mr
redesign
work
but
we're
getting
ready
to
start
sessions.
Unfortunately,
our
reops
team
is
basically
non-existent
right.
Now,
one
person
is
no
longer
a
git
lab.
The
other
is
time
off
right
now,
but
I
will
personally
dive
into
the
recruiting
for
this.
F
Hopefully
we
can
start
sessions
in
the
next
couple
of
days,
otherwise
things
you
might
not
be
aware
of
I'm
doing
like
a
larger,
create
stage
jobs
to
be
done,
effort
at
sort
of
the
request
of
burrit
and
Sarah.
F
So
that's
been
going
on,
I've
been
looking
at
I,
don't
know,
300
some
odd
assess
verbatim
as
one
of
my
inputs,
which
was
really
interesting
as
well
as,
of
course,
the
user
Journey
map
that
we
did
a
while
back
so
happy
to
get
your
input
on
any
of
that
that
stuff,
when
you
have
time,
but
also
not
urgent,
okay,.
E
Cool
yeah-
that's
great
I
was
wondering
where,
when
we
would
have
time
to
get
to
that
to
the
jobs
to
be
done,
so
there's
things
that
I
think
at
least
I
created
one
issue
at
least
a
long
time
ago
about
that
and
just
like
hey
when
we
have
time
in
the
future,
we
have
to
think
about
that.
E
So
I'm
glad
that
we're
looking
into
it
yeah
and
let
me
know
how
I
can
help
I
think
in
terms
of
like
linking
to
like
existing
knowledge,
I
think
you
can
get
most
of
what
we
have
in
the
handbook
and
also
what
we
did
in
the
user.
Journey
mapping
I
think
there's
probably
a
few
other
things,
but
those
two
resources
will
probably
help
you
already
more
than
80
percent
of.
C
F
Yeah
I
mean
if
you,
if
you
like
I,
can
tag
you
on
the
issue.
I'm
collating
a
table
of
all
the
ones
that
I've
found
so
far
and
yeah
we'll
use
those
as
Direction
but
I,
think
yeah
I
think
Sarah
was
looking
for
like
stage
level
jobs
to
be
done,
so
it's
gonna
be
fun.
Yeah
I,
don't
know.
E
Yeah
and
I
and
I.
Imagine
that,
like
to
think
about
stage
level
jobs
to
be
done,
you
naturally
will
have
to
tests
the
boundaries
of
jobs
that
are
that
lower
and
jobs
that
maybe
are
a
bit
higher
so
to
get
the
right
level
of
granularity,
so
yeah.
That
makes
sense
to
me
and
very
excited
about
that
as
well.
You
must
be
filled
with
work,
then
well
so
much
that
you're
doing
I.
F
Have
a
lot
on
my
plate
right
now,
but
it's
all
good
stuff.
C
D
So,
are
you
taking
time
off,
starting
like
from
from
next
week
onwards,.
C
Yeah
I'll
be
off
starting
Tuesday
of
next
week
until
the
new.