►
From YouTube: 2023-09-12 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
Sorry
all
right
welcome
to
the
September
12th
ux
Inc
I
thought
it'd
be
good
to
get
on
the
same
page
about
this
one
Matthew
I
wasn't
I'm,
not
sure.
If
we're
saying
the
same
thing
and
agree
on
the
same
thing
or
not
so
I
thought
it
would
just
be
easier
to
to
sync
on
it
and
I.
Think.
Let
me
this
might
be
easier.
If
I
do
it
like
this
I.
A
What
ended
up
being
implemented
by
the
third
insights
team
was
sort
of
just
leaving
it
here
where,
like
it
works?
If
you
do
sort
of
merchant
pipeline
succeeds
today
and
so
I
guess,
the
question
is:
is
do
we
need
to
go
forward
with
this
and
I
guess?
What
does
this
end
up?
Looking
like
above
this
maybe
line
here,
if
we
do
do
that,
or
are
we
fine
with
just
let's
leave
it
like
this
for
now
and
we
can
revisit
these
designs
later.
C
C
But
if
you
have
a
setting,
someone
hits
the
button
to
Auto,
merge
and,
and
that
is
set,
then
that
information
is
gonna,
be
visible.
Unless
there's
like
a
failed,
merge
check
right
like
like
when
that
thing
turns
red.
It
hijacks
that
section
to
show
you
that
there's
a
problem
and
you
no
longer
get
to
see
that
there's
an
auto
merge,
so
it
like
comes
and
goes
which
to
me
could
be
a
problem,
which
is
why
I
was
saying
like
yes,
the
screenshot.
C
A
A
I
think
you're,
right
and
I
had
not
it
didn't
dawn
on
me
that
you
could
have
failed
checks,
even
though,
like
there's
literally
a
design
that
shows
stale
checks
right
above
it
like,
then
what
would
happen?
I
guess,
I
hadn't
realized
that
those
were
the
same
plate.
Okay,
then
I
think
you're.
Okay,
so
then
I
think
the
answer
is.
We
do
need
to
move
this
text
to
the
footer.
A
In
the
case
of
failed
checks,
I
guess
the
question
is
like:
if
there
aren't
failed
checks,
though,
what
is
the
whole
I
think?
That's
probably
then,
the
missing
design
yeah
piece
here,
because
that,
because
that
white
bar
acts
as
like
the
header
for
the
widget
right,
then
that
that
feels
like
a
missing
design
piece.
If
we
do
take
things
out,
that's.
C
A
B
A
C
Yeah,
okay,
let
me
let
me
think
about
that
and
see
if
I
can
come
up
with
a
solution
there.
A
A
B
B
B
A
B
A
Cool,
oh
there's
something
else
in
the
internet.
All
right,
Ben's
got
number
two
on
the
agenda.
I
can
type
for
you.
If
you
would
like
cool.
B
Yeah
I've,
just
an
update
from
research
world
we're
still
doing
the
create
stage
jobs
to
be
done.
Analysis
I
know
it's
been
like
six
months.
It
feels
like
we're,
not
the
point
where
I
have
surveys
written
up
for
all
of
create
to
get
an
opportunity
score
for
all
the
outcome,
statements
that
we
were
able
to
synthesize
from
the
jobs
to
be
done.
B
Interviews
I
know,
that's
a
lot
of
jargon,
but
basically
these
are
like
the
jobs,
the
many
jobs
that
people
want
to
do
and
create,
and
we
will,
through
this
survey,
be
able
to
get
an
opportunity
score
which
gives
us
a
prioritized
list
of
the
areas
that
are
most
painful
to
our
users
or
that
are
most
important
and
simultaneously
least
satisfying.
B
Also
I've
been
asked
to
do
another
round
of
benchmarking
usability
benchmarking,
so
we
did
the
first
one
in
the
company
a
while
back.
You
remember
I,
guess
about
a
year
ago,
maybe
two
years,
yeah
I,
don't
know
a
while
ago.
Most
of
the
issues
that
were
brought
up
there
have
been
addressed
in
some
way
or
deemed
too
difficult.
B
So,
just
so
everyone's
aware,
I
will
be
kicking
that
off
again
I'm,
not
sure
that
I
need
anything
yet,
but
your
participation
in
looking
at
the
results
and
coming
up
with
ways
to
interpret
those
or
filter
them
into
current
work
streams
will
be
appreciated.
A
Do
you
have
on
the
first
one
for
jobs
to
be
done,
so
you've
done
all
the
analysis,
and
now
you
have
to
send
out
surveys
that
that's
the
correct.
Do
you
have
an
idea
of
like
when
surveys
go
out
and
then
like
how
long
they're
open
for
like?
When?
Are
you
expecting
to
come
back
and
be
like
here's,
the
score
for
all
the
different
things
and
you
have
it
sounds
like
they're
specific
opportunities?
That's
right!
Do
you
have
a
list
of
the
opportunities
or
do.
B
B
They're
they're
in
the
canvases,
which
were
in
mural
and
they're
now
in
fig
Jam,
because
we
transferred
everything
from
your
office
again
so
I
can
I
will
send
I
will
post
a
link
in
here
to
where
you
can
look
at
them
all.
B
B
Maximize
my
ability
to
examine
you
know,
code.
C
B
Review
for
like
scalability
or
something,
and
so
we
asked
people
how
important
that
is
and
how
satisfied
they
are
with
their
ability
to
do
that
currently
in
gitlab,
and
so
if
people
think
that's
really
important
and
they're
not
satisfied
with
it
that
difference.
Yes,
it's
higher
on
the
sort
of
opportunity
to
improve
this
thing
list.
B
And
if,
for
your
first
question,
the
survey
is
ready,
but
we
are
I
need
to
send
it
out
to
a
small
group
to
Pilot
first,
because
it's
pretty
complex
and
we
want
to
know
if
people
are
actually
going
to
fill
it
out
or
not
we're
going
to
offer
an
incentive,
we're
breaking
it
down
into
50
questions
out
of
the
pool
of
150
I've
been
offering
them
25
bucks,
so
hopefully
they'll
do
it,
but
I'm,
hoping
that
yeah.
We
can
start
to
to
get
results
in
a
couple
of
weeks.
B
Yeah
hopeful
that
we
can
probably
launch
it,
if
not
the
end
of
this
week,
then
the
beginning
of
next
week
and
then
yeah
it'll
run
for
as
long
as
it
needs
to
run.
That
may
be
a
week.
B
A
A
C
I
just
put
in
two
prototypes
that
I've
been
working
on
for
usability
testing.
One
is
for
choosing
reviewers
and
one
is
for
the
funky
code
changes
layout.
That
I
came
up
with,
so
my
plan
is
to
put
those
up
on
usertesting.com
and
just
get
some
feedback
they're
not
done
yet,
but
just
kind
of
FYI.
You
can
check
them
out.
A
C
A
C
C
So
one
thing
one
thing
we
could
do
if
you
want
to
send
it
internally
is
just
say
record
yourself
going
through
this
on
a
zoom
just
do
a
zoom
Thing
by
yourself
and
just
record
it
and
send
it
to
us
and
kind
of
just
talk
your
way
through
it
as
you're
as
you're
going
through
it.
If
you
just
want
to,
like
informally,
send
it
to
internal
people
like
we
can
give
them
some
some
instructions
to
just
think
aloud.
A
Yeah
I,
don't
know
I'm
sure
a
few
people
will
do
it.
I,
don't
know
how
many
people
will
do
that.
We've
tried,
like
sort
of
like
hey
record
yourself,
doing
a
code
review
before
I
think
what
I,
what
I'm
nervous
about
is.
A
I
wouldn't
say:
user
testing
is
necessarily
the
greatest
pool
of
feedback
for
us
right
or
things
like
this
and
I've
heard
that
before
yeah
and
so
I'm
worried
that,
like
we
don't
get
anything
sort
of
like
useful
or
like
the
user
testing,
people
are
like
it's
great,
but
they
don't
actually
like
use
our
product,
anyways
and
so
like
do.
We
learn
anything,
and
so
that's
why
I
was
thinking
like
if
we
had
a
low
friction
internal
way
to
do
this.
A
At
least
it's
people
who
are
in
the
product
every
day
like
guarantees
us
that
they
know
how
to
do
a
code
review
inside
a
good
lab
and
we'll
have
like
opinions,
I
think
about
it
and
whether
or
not
we
we
want
that
I,
don't
know
I
just
didn't
I'm
cautious
about
like
the
quality
that
we'll
get
out
of
user
testing
and
I.
Don't
I.
C
B
There's
a
ux
research
volunteers,
slack
Channel,
which
are
people
that
have
signed
up
to
be
recruited
internally
for
things
like
this
and
I.
What
I
would
do
is
like
post
the
request
there
with
like
a
link
to
the
prototype
in
just
like
a
couple
of
questions
like
as
prompts
just
to
sort
of
make
sure
they
know
what
to
talk
to
like
what
they're
actually
looking
at
what
to
focus
on
and
see.
B
If
you
get
anyone
that
way,
yeah
I
guess
I,
don't
know,
maybe
have
them
post
their
feedback
in
an
issue
in
the
issue
or
somewhere
else,
wherever
it's
most
useful
to
you,.
A
I
was
gonna,
say
I,
like
the
idea
of
having
them
record
it,
assuming
it's
a
little
free
I
think
most
people
are
used
to
like
sort
of
recording
themselves
at
this
point
yeah.
So
maybe
that's
low
enough
friction
if
we
can
like,
especially
if
you
time
like
you're
gonna,
spend
15
minutes
on
it
or
something
right
like
I,
don't
is
it
I
think
people
are
willing
to
sort
of
do
that.
C
Yeah
I
agree:
yeah,
okay,
I'll
I'll,
look
into
that
that
Avenue
and
I'll
also
talk
to
Andy
and
see
if
he
has
any
other
thoughts
around
other
ways
to
do
it.
But
I
agree
that
usertesting.com
might
not
be
very
representative.
A
A
C
A
So
yeah
you've
got
the
the
one
customer
that
you
were
gonna
chat
with
I.
Think
I've
seen
that
thread.
C
Yeah
and
I
just
commented
I
think
yesterday
about
because
they
were
wanting
to
see
something
and
I
tagged.
I
think
I
tagged
Andy
to
see
if
he
had
any
concerns
with
showing
the
customer
designs
because
yeah
it
could.
It
can
open
up
all
kinds
of
issues
if
you
show
them
early
designs,
so
I
guess
what
I'm
saying
is:
I
have
customers
who
I
could
do
that
with,
but
yeah
also
not
sure
if
it's
a
good
idea,
a
good
idea
or
not,
but
I'm
open
to
doing
it.
B
Just
give
a
safe,
Fiverr
statement
for
anything.
Thank
you.
You
know
what
that
is.
It's
like
see,
so
it's
something
that
you
should
do,
which
is
don't
make
any
like
purchasing
or
financial
decisions
on
anything
you're
about
to
witness
these
designs.
We
make
no
promise
that
they'll
ever
make
it
into
the
product
purely.
A
A
Cool
yeah,
thanks
for
sharing
I'm
I,
know
I've
seen
like
bits
and
pieces,
but
I'm
I'm
curious
to
see
like
the
full
prototypes
and
I
think.
Even
if
you
go
like
the
user
testing
or
internal,
it
would
be
good
to
have
a
recording
of
yourself
going
through
it
and
explaining
sort
of
about
stuff
like
Ben
just
mentioned.
Even
if
we
don't
share
that
like
outside
of
a
very
small
group
of
us.