►
From YouTube: 2023-03-22 Code Review UX Weekly
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
The
only
one
up
here
was
it
I
met
with
Andy
earlier
today,
and
so
it
sounds
like
scope
has
been
defined
amongst
Alex
and
Matthew.
So
that's
exciting,
I
will
put
a
I
will
put
a
link
in
the
agenda
to
where
that
happened.
So
so
this
is
helpful
to
me.
So
I
was
excited
to
see
this
I
know
you
and
Alex
have
both
been
been
ramping.
I
guess,
with
this
in
mind
and
then
Pedro
had
sent
out
some
updates
earlier
and
since
Alex
is
not
gonna
make
it.
A
What
do
you
see
in
terms
of
the
restructuring
like
how's
that
going?
What
do
you
need
help
with?
How
like
what
questions
do
you
have
now
and
then,
how
do
we?
How
do
we
like
keep
the
ball
moving
forward
on
that?
If,
if
that's
sort
of
where
we're
gonna
go.
A
To
that
like,
if
that,
if
that's
going
to
be
your
scope,
like
then
sort
of
what
do
you
have
in
terms
of
questions
and
feedback
on
it
now
or
like
what
can
I
do
to
help
or.
B
I
kind
of
came
out
of
it
not
really
knowing,
yet
where
I'm
needed
on
that,
because
they
have
some
Concepts
and
he
was
kind
of
talking
about
taking
those
Concepts
and
applying
them
to
like
issues
and
Snippets
and
designs.
And
you
know
like
changing
the
way
we
comment
across
all
of
gitlab
for
consistency
and
talking
about
doing
more
robust
user
testing
with
the
concepts
they
have
in
yeah.
It's
interesting
because
it's
just
a
really
big
project
and
I'm
not
really
sure,
like.
B
B
A
Okay,
yeah
I,
that's
interesting
that
you
brought
up
the
scope.
I
also
saw
pager's
updates
to
like
epics
and
reorganization
today
and
left
him
a
comment.
A
A
similar
comment
about
scope
that,
like
this
felt
this
feels
like
it
just
exploded
on
us,
like
if
you're
reframing
it
this
way
and
and
makes
it
hard
to
understand,
like
how
code
review
can
like
do
anything
now
because
like
if
you
want
to
go
and
explore
all
these
things.
Like.
A
That's,
that's
a
huge
project
and
we
already
like
what
I
said
in
there
there's
already
so
much
Divergence,
not
that
that's
necessarily
good
but
like
the
work
items,
sort
of
okrs
UI
has
like
a
totally
different
commenting
field
than
than
issues
do,
and
then
issues
and
epics
are
different
than
merge
requests
because
we
treat
threads
as
like,
very
different,
like
objects
that
well
I
understand
like
wanting
one
unified
experience
like
that
feels
like
a
a
very
lofty
and
ambitious
thing.
A
A
A
We've
been
we've
been
like
talking
about
it
for
a
long
time
and
it
felt
like
we
had
gotten
close
to
designs
that
were
tested
and
validated
and
sort
of
like
knew
pretty
much
what
we
were
looking
at
and
then
you
know
all
of
the
organizational
changes
the
people
being
gone
have
just
sort
of
slowed,
all
that
and
then
now
it
feels
like
we're
we're
almost
starting
over
and
so
I.
Don't
I,
don't
want
to
do
that
so
I
think
yeah.
A
B
A
B
B
One
of
his
concerns
is
that
the
research
that
was
done
was
very,
not
not
naturalistic,
like
it's
just
a
very
narrowly
scoped
usability
test
with
specific
tasks,
but
doesn't
really
test
a
developer's
actual
workflow,
and
so
what
I'm
worried
about
is
getting
caught
up
in
Endless
cycles
of
robust
research,
and
so
what
I'm
wondering
from
my
limited
knowledge
of
the
MRE
structure
is,
if
there's
like
one
minimal
change
that
we
could
put
under
a
feature
flag
or
put
out
as
like
a
beta
to
actual
users
and
say
like
before
we
before
we
tackle
this
entire
restructuring
of
the
Mr.
B
Does
changing
this
one
thing
cause
people
to
complain,
or
do
they
like
it
and
to
me,
like
one
of
the
biggest
changes
that
they're
talking
about?
Is
the
comments
tab
so
having
comments
not
be
on
the
main
page
and
the
main
page
is
just
activity
and
then
having
a
comments,
tab
and
so
in
my
head
I'm
like
well?
What?
B
Or
something
similar,
that's
like
because
moving
moving
comments
to
its
own
tab,
you
know
I
always
just
think
of
GitHub
and
how
simple
their
issues
and
pull
requests
are
and
how
everything's
just
sort
of
right
there
on
that
one
page,
the
description,
the
comments,
and
so
what
you're
doing
is
you're
splitting
all
that
information
up,
and
so
now
you
don't
really
have
just
like
this
one
nice
place
that
you
get
like
your
overview
of
the
Mr.
B
A
I,
don't
one
of
the
things
that
like
I,
have.
A
One
of
the
things
that
like
I,
like
about
the
comments
tab,
is
that
part
of
the
problem
with
merge
requests
is
that
comments
are
divided
into
places
right
like
they
do
exist
on
the
overview
tab,
but
they
also
exist
in
like
the
changes,
tab
and
I.
Don't
know
that
the
comments
tab
solves
that
for
us
because
of
the
nature
of
you
still
go
to
the
diff
to
like
make
comments
on
code,
and
so
there's
still
like
a
version
that
will
exist
in
changes
in
a
version
that
exists
in
comments.
A
But
it
does
make
it
easier
to
know
like
in
Theory,
where
you're
looking
and
I
think
some
of
the
like
grouping.
That
was
happening
in
the
comments
tab.
You
know
filtering
based
on
personas
or
like
people
or
there
had
been
like
talks
of
tying
it
to
like
the
review
rounds
concept
like
make
that,
like
the
central
place.
A
A
B
A
B
I
feel
like
there's,
there's
two
aspects
of
it
right.
There's
things
that
logically,
make
sense
and
I
agree
that
splitting
off
comments
and
making
them
more
robust
and
more
feature-rich
could
be,
could
be
a
great
move
and,
logically,
it
makes
sense
and
then
there's
like
the
actual
workflow
of
a
developer,
doing
a
hundred
things
at
the
same
time
and
spending
eight
hours
a
day
in
the
tool.
B
I
I
like
try
to
balance
between
thinking
about
like
what
logically
makes
sense,
and
does
that
also
apply
to
a
stressed
out,
developer's
actual
workflow:
does
it
make
them
faster?
Does
it
slow
them
down?
Does
it
make
them
click,
because
it's
amazing
like
when
I'm
using
software,
it's
like
some
things.
B
Some
tasks
are
so
annoying
because
just
the
amount
of
clicking
and
navigating
you
have
to
do
to
complete
the
task,
and
then
some
are
just
so
easy
and
I
can't
tell
you
which
one
is
right
and
which
one's
wrong,
but
I
definitely
want
to
try
to
think
as
much
as
possible
about
like
actual
developers,
workflows
and
that's
why
I'm
not
the
biggest
fan
of
usability
testing
with
something
this
important.
You
know
like
that,
has
this
many
eyes
on
it
because
there's
just
like
how
are
you
gonna
find
developers.
A
Yeah,
you
always
have
to
take
the
usability
test
for
things
in
code
review,
like
with
a
grain
of
salt,
because
they're
not
they're
helpful
for
like
glaring
issues
but
yeah.
You
still
ultimately
need
to
get
things
on
with
a
future
flag
and
watch.
You
know
get
Labs
engineering
team.
Give
you
give
you
the
feedback
that
you
you
need
to
hear.
I
suppose
maybe
right.
A
Phrase,
it
I
think
it
is
interesting
that
I
think
you
know
one
of
the
things
that
we
keep
talking
about
like
the
flow
of
a
review
and
we're
working
on
the
new
job
to
be
done.
Canvas
thing
as
well
as
like.
Maybe
it
makes
sense
to
sort
of
like.
A
A
Like
what
are
the
changes
we
need
to
make
to
the
layout
I
think
you
know.
Ultimately,
the
goals
are
very
is
still
that,
like
we've
got
this
problem
with
their
there's
too
much
information
and
no
way
to
tell
you
where
you
need
to
go
to
do
whatever
you
need
to
do
so,
like
largely
that's
where,
like
the
restructuring
stuff
originated,
is
that
like
it's
just?
A
How
do
we
move
things
around
to
make
it
more
coherent?
And
maybe
the
comments
tab
isn't
the
right
answer,
but
yeah
I
think
I.
Think
that
makes
sense.
I
think
you
know
it's
I'm
I'm
optimistic
to
hear
that
you're
you're
thinking
that
way
and
like
have
those
questions
and
I
think
you're
meeting
with
Pedro.
A
So
that's
good,
so,
like
I,
think
I
would
say
it's
fine
to
keep
pushing
in
that
in
that
vein
and
like
let's
just
make
sure
that
we're
you
know
documenting
the
feedback,
we're
providing
it
in
an
issues
and
epic.
A
So
we
can
like
have
that
conversation
and
make
sure
we
engage
appropriately
there,
because
I
think
you
know
there's
an
expectation
that
we
do
something,
because,
because
clearly
the
merge
request
doesn't
work
today
or
works,
but
but
has
some
problems,
and
so
you
know
striking
the
right
balance
of
what
of
what
that
work
is
is
is
important.
A
Cool
well,
I
didn't
have
anything
else,
but
that
that
feels
like
a
good
start
for
I,
don't
know
30
days
in
or
so
yeah
so
yeah
I
would
say
feel
free
to
just
like
keep
keep
looping
me
in
and
bringing
these
things
up
I,
you
know,
I,
definitely
don't
think
anything
that
code
review
has
said
we
want
to
do
is
set
in
stone.