►
From YouTube: 2022-10-18 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
Foreign
welcome
to
the
code
review,
uxync,
yeah
I
think
the
first
one
in
the
agenda
was
I
saw.
A
I
saw
the
comment
that
I
guess,
like
some
analysis,
was
done
and
sort
of
the
restructuring.
I
have
not
had
an
opportunity
to
like
actually
detailed
look
into
it,
but
I
was
it
did
sort
of
sound
and
I
guess
your
answer
here,
like
that,
there's
more
more
work
and
so
I
guess
I'm
just
sort
of
curious
like
what
are
we
looking
at
in
terms
of
like
the
next
steps
or
or
what
are
we
doing
here.
B
Well,
yeah
there's
always
more
work
right,
so
we're
done.
It's
perfect.
The
the
overall
sort
of
sense
that
I
got
from
the
interviews
I
conducted
and
the
ones
that
I
watched
were
that
it
was.
B
It
was
relatively
well
received,
but
there
were
so
many
questions
that
came
up,
that
I
didn't
have
answers
to
and
I,
don't
know
how
it
would
work
yet
because
the
the
restructure
was
done
with
such
a
tiny
little
example
merger
class,
with
like
four
pieces
of
activity
it
just
there
are
a
lot
of
not
edge
cases,
just
things
that
happen
in
a
merge
requests
that
were
not
in
this
proposal.
So
I've
got
this
example.
B
Merge
request,
pasted,
I've
expanded
every
you
know,
discussion
on
that
merge,
request
and
went
through
several
rounds
of
review
with
multiple
people.
Labels
were
added
commits,
were
added
changes
were
discussed.
It
went
through
a
lot,
so
that's
more
like
not
typical,
but
it
you
know
it's
an
extreme
example
extreme
example.
So
I'm
gonna
sort
of
group
what's
happening
at
each
stage
of
it
and
then
see
how
we
can
kind
of
fit
that
into
the
the
structure
and
ideally
have
different
versions
of
it.
B
Where,
like
you,
request
or
I'm,
probably
not
going
to
do
all
of
that
stuff.
But
it
questions
like
you
know.
How
is
this
going
to
work
when
I
switch
tabs
so
much
and
weren't
easily
answerable,
because
people
weren't
really
understanding,
in
my
opinion,
the
point
of
the
overview
tab?
They
were
still
viewing
it
like
the
current
overview
tab
where
this
is
where
you
go.
This
is
where
you
do
all
your
things.
B
The
proposal
is
kind
of
Shifting
people
to
the
comments
tab
to
use
that
as
your
like
home
base.
If
you're
going
to
do
any
kind
of
discussion
that
wasn't
really
clear
in
The
Proposal,
so
we're
gonna
make
a
higher
Fidelity
Proposal
with
more
more
actions
in
it,
I
guess
and
then
even
the
little,
the
smaller
things
that
we
thought
we
kind
of
hypothesized,
that
the
filters
on
the
activity
view
would
be
kind
of
an
easy
win
and
something
that
could
be
broken
out
into
an
issue.
B
Maybe
right
away
and
I
think
the
goal
was
to
create
five
issues
or
something
for
the
okr,
so
that
would
have
been
easy.
We
still
could
do
that,
but
I'm
not
sure
about
it,
yet
either
I
I,
really
I,
don't
want
to
you
know,
add
all
these
filters
only
to
realize
that
they
don't
really
work
that
well
and
have
to
you
know
roll
them
back
in
any
way.
C
Yeah
basically,
I
mean
we've.
We've
got
a
positive
enough
signal
on
the
the
low-fi
concept
testing
to
to
proceed
and,
of
course,
some
of
our
time
to
make
it
closer
to
reality
and
then
do
another
round
and
see
if
we're
actually
still
on
the
right
track,
essentially
like
what
we
did.
First
is
basically
like
concept
testing
right
really.
The
Fidelity
is
this
sort
of
a
thing
worthwhile.
C
C
I,
don't
know
at
least
as
many
as
we
did
in
the
world.
You
and
I
can
talk
about
it
about
what
scenarios.
Specifically
we
want
to
craft
as
you
get
closer
with
the
Prototype.
B
Yeah,
that
sounds
good
and
even
though
yeah
well
not
even
though
it
was
a
positive
enough
like
like
Ben,
said
it
was
positive
enough
that
we
should
continue
if
everyone
had
been
like
what
is
this
I
don't
understand
what
this
is,
we
would
have
had
to
step
way
back
and
that
would
have
been
terrible.
So
this
is
a
good
thing,
you're,
crowning,
a
lot
Kai.
A
Oh
I'm
I'm,
trying
to
think
through,
like.
A
I,
don't
know
I'm
I'm,
not
yeah.
Sorry
I
don't
mean
to
frown
like
that.
Wasn't
my
intentionally
I'm
trying
to
understand
how
all
this
like
one
fits
together
in
terms
of
like
okay
I
was
looking
at
like
our
okay.
I
was
pulling
it
up
and
trying
to
figure
out
like
what
did
we
say
we
would
do
which,
like
I,
had
I'm
not
necessarily
concerned.
A
If
we
don't
do
that
and
then
I
was
trying
to
think
like
logistically
about
putting
together
the
mock-ups
and
sort
of
what
that
entails
and
I
think
that
makes
sense,
yeah
I,
think
I'd
say
this
is
consistent
with
what
I
had
been
hearing.
Is
that,
like
generally
well
received
what
we
need
to
hire
Fidelity
test?
So,
like
that's
good,
that
makes
that
makes
sense.
A
I
think
this
is
always
my
question
like
how
do
we
get
to
like
I
always
worry
about
these
tests
that,
like
we
never
get
to
like
a
level
of
confidence
that
makes
us
feel
great
about
anything
because
it's
so
hard
to
get
like
real
sample
sizes
and
it's
sort
of
fake
work
streams
and
they're,
very
they're
very
staged,
or
you
get
people
who,
like
aren't
familiar
at
all
with
gitlab
and
like
then
it's
like
even
weirder,
yeah,
so
I
think
I'm,
just
like
I'm
curious
to
see
how
we
like
approach
the
higher
Fidelity
test
and
like
get
get
some
stuff
that
gives
us
confidence
and
things
I'm
also
sort
of
curious
about
timing.
A
It
feels
like
we
obviously
won't
get
in
I
and
I.
Think
you're
I
think
your
reasoning
for
not
being
in
a
position
where
we
can
create
issues
makes
sense,
so
I
think
I'm.
Fine
with
that
I'm
just
curious
like
what
do?
What
do
we
think
like
given
how
much
time
it
took
to
get
through
Lo-Fi
and
the
testing
I'm
wondering
how
much
time
do
we
expect
like
higher
Fidelity
and
then
testing
to
take
on
that.
B
When
you
say
the
amount
of
time
it
took
to
do
the
little
fine
testing,
do
you
mean
like
everything
up
to
that
low-fi
mock-up
and
all
the
workshops
and
everything.
A
A
A
B
I
don't
know
I
I've
got
them
like
the
merge
request.
All
expanded
and
screenshotted
in
my
figma
file
and
I
was
just
going
to
start
kind
of
Shifting
it
over
into
the
Prototype.
B
Once
I
get
to
a
certain
stage,
though
like
it
it
might,
it
might
be
that
I
don't
need
to
keep
going
like
once
I've.
You
know
done
like
two
reviews
and
subsequent
commits
and
everything
like
that.
I
probably
don't
need
to
keep
going
so
I
don't
know
yet
because
my
answer
I,
don't
it's
not
going
to
take
over
a
milestone
to
finish
the
Prototype,
but
then
I'll
probably
need
to
talk
to
Ben
a
little
bit
about
about
the
scenarios
and
what?
B
What
interactions
we
need
in
that
prototype
to
make
it
worthwhile
and
then
I
agree
about
the
you
know
not
knowing
git
lab
use
users
who
don't
know
gitlab,
probably
aren't
worth
talking
to
at
all
at
this
point.
B
So
maybe
we
could
just
do
some
more
internal
talks
and
then
move
to
external,
with
the
same
prototypes
just
so
that
we
can
maybe
get
quicker
feedback.
I
don't
know
I
don't
want
to
always
stick
to
internal,
but
it's
so
much
quicker.
A
Yeah
yeah
I
think
one
of
the
other
like
pieces
to
keep
in
mind
might
be
and
I
don't
ban.
Maybe
your
thoughts
like
what
is
your
if
I
look
at
a
calendar
like
a
month
from
now,
we
hit
U.S,
Thanksgiving
and
then
sort
of
two
weeks
after
that
we
hit,
everybody
leaves
and
doesn't
come
back
until
January
holidays,
and
so
knowing
that
that's
like
internal
get
left
culture
right
to
be
off
like
I
think
people
will
probably
have
significant
time
off
coming
up.
I.
A
Imagine
that
also
impacts
sort
of
like
our
ability
to
find
people
to
test
with
and
do
things
with
over
that
period
of
time.
Maybe
like
is
that
I
guess
I'm
wondering
like
do.
We
think
we're
sort
of
like
into
January
now
before
we
get
like
test
run
on
this?
Is
that,
like
a
reasonable
thought,
if
we
are
three
weeks
to
a
month
to
like
get
a
prototype
in
a
spot
that
we
feel
good
about,
that
puts
us
in
your
Thanksgiving?
C
I
mean
I
appreciate
the
the
foresight
I,
don't
know
for
sure,
but
the
nice
thing
about
these,
like
usability
testing
in
general,
is
you
don't
need
a
high
number
of
participants
to
uncover
most
of
the
issues
so,
depending
on
how
we
break
it
out,
usually
like
three
to
five
participants
for
whatever
flow
you
want
to
do,
and
you
can
have
them
each
participant.
Do
multiple.
You
know,
interactions
a
few
structure
it
that
way
and
I
think
we
can
get
that
pretty
easily
regardless
of
the
time
of
year.
C
B
Yeah,
it
wasn't
difficult
at
all
to
find
internal
participants.
Everyone
I
mean
we
went
within
like
two
days
for
a
couple
of
them
and
then
everyone
I
asked
said
yes
and
we
have
that
internal
people.
Developers
who
expressed
interest
in
participating
in
these
I
have
that
list
of
of
people,
so
they're
theoretically
always
going
to
be
available
to
talk
to,
and
it
only
takes
45
minutes
of
their
time.
C
Also
I
can
start
the
recruiting
process
like
earlier
than
normal,
okay
and
just
make
sure
that
we
we
have.
Those
folks,
like
I,
think
it's
gotten
easier
over
time
to
to
get
people
one.
Usually
once
we
start
putting
a
springer
out
there,
we'll
it'll
be
pretty
quick.
C
A
D
D
C
Yeah
Mike
Nichols
did
a
huge
effort
on
this,
a
while
back
for,
like
the
specifically
source
code
settings.
I
suspect
this
is
like
the
culmination
of
part
of
that
work.
C
He
went
very
very
detailed
into
that.
Essentially
we
have
a
lot
of
settings
and
it's
really
really
hard
to
organize
them
in
a
way
that
makes
sense
to
everybody
but
yeah
I
I,
guess
that
pain
point
is
known,
I
guess
that's
all
I.
D
A
Yeah,
it's
interesting
I
think
my
only
concern
is
that
that
box
doesn't
work
great
when
you
change
the
branch
name
is
what
happens.
Actually
I'm
sort.
A
Like
slashes
and
other
things
like,
there's
been
some
bugs
with
like
that
box
in
general,
for
creating
a
merge
request,
so
I'm
wondering
like
if
they
template
in
things
that
are
not
I'm
wondering
what
sort
of
like
new
issues.
This
will
create
in
terms
of
like
people
templating
in
branches
that,
like
with
path
names
that
just
for
some
reason,
fail
to
actually
create
the
branch
and
therefore
can't
create
the
merge
request.
C
A
We
fixed
some
of
them,
but
like
I,
that
one
that's
in
the
example
of
like
feature
slash
I'm,
pretty
sure
that
does
not
work
correctly,
and
some
of
it
has
to
do
with
like
what
you
target.
D
D
D
A
Jay
would
know
I,
don't
think.
Jay
is
Source
codes,
software
engineering
test,
I,
don't
I,
think
he's
only
ours,
but
it
might
be
worth
thinking.
Jay
on
that
Mr,
okay,
I
know
Anastasia's
on
it,
but
Jay
will
have
context
on
the
other
side
of
it.
Okay,.
A
Appreciate
it
cool
well,
it
was
good
to
see
everyone
enjoy
the
rest
of
your
week.
Thanks
for
hanging
out
bye.