►
From YouTube: 2021-01-26 Create: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
Yeah
for
all
the
work
on
the
survey
and
taking
all
the
feedback
and
edits,
I
know
language
is
super
nit
picky
and
I
wording
questions
is
hard,
and
so
I
feel
like
that
is
not
fun
to
have
to
deal
with
that.
So
I
appreciate
you
you're
doing
that
and
taking
the
feedback.
I
left
a
comment
which
I
don't
know
if
you've
seen
it
like
after
retrying
it
in
the
single
question
mode.
It
was
with
like
the
dots
like
it
just
doesn't
work
well
either.
So
exactly
yeah,
I
I
will.
A
I
will
go
with
whatever
you
want
to
go
with
on
that
one.
At
this
point
like
I
think
I
think
the
language
piece
being
hash
out
is
was
probably
more
important
than
in
the
format.
So
I
think
whatever
we
think
on
the
format
will
be
fine.
B
Yeah,
I
think
yeah.
For
me
it
was
the
same
like
looking
at
it
without
using
it
it.
For
me,
it
also
felt
this
might
work,
but
then
I
started
using
it
and
experimenting
with
it,
and
I
just
I
lost
track
of
where
the
radio
button
was
selected
and
unselected.
B
A
The
arrows
ends
up
in
that
sort
of
ambiguous.
I
think
place
too,
where,
like
you,
move
something
up
and
it
pushes
stuff
down,
but
then
like
you've,
got
to
go
refine
the
one
that
maybe
push
down,
because
you
want
to
move
it
like
it
doesn't
feel
like
it
doesn't
have
like
clear
numbering
to
it
like.
I
think
you
realize
your
stack
ranking,
but
not.
A
A
A
B
B
Yeah
and
yeah
I
mean,
on
the
other
end
of
the
spectrum
yeah
thanks
for
taking
on
some
of
the
milestone
work
for
me
and
and
being
also
more
involved
in
the
merge
requests.
That
has
been
helpful.
I
mean,
like
you,
see
that
I
still
comment
on
the
merge
requests,
but
I'm.
B
Like
I
feel
more
supported
and
less
pressured
to
make
a
decision
yeah
and
just
I
don't-
I
know
that
some
things
will
be
seen
by
someone
you
know
so
that
has
been
helpful
both
from
a
time
perspective.
A
Reviewing
multiple
people's,
mrs
is
actually
super
frustrating
because
it
was
like
you
check
out
their
branch
in
your
gdk,
and
then
you
just
need
to
like
destroy
that.
So
you
can
check
out
someone
else's
branch
and,
like
phil's,
has
database
migrations
in
it,
and
I'm
just
like.
I
don't
like
any
of
this
like
this
is
the
worst
system.
B
A
But
yeah
it's
been
interesting.
It's
definitely
like
I
mean.
I
think
it's
clear
to
me
that
we
we
don't
do
enough
planning
and
reviews,
I
think
suck
more
for
us
because
of
that
because,
like
some
of
these
questions
sometimes
I
feel
like
should
have
been
answered
ahead
of
time.
So
I
think
it's
good
to
like
experience
that
pain
from
both
sides,
because
now
you
know
if
engineers
were
in
there
looking
at
things,
first
we'd
have
some
of
our
questions
that
we
sort
of
come
up
with
on
the
fly.
A
Lopsided
ratio
right
now
with
I
don't
know,
I
think
we've
got
nine
engineers
or
something
insane.
It's
just
not
a
it's
too
many
people
working
on
things
to
be
able
to
know
so.
B
Yeah
and
and
the
fact
that
we're
not
doing
that
investigative
work
from
the
technical
side
earlier
you've
noticed
like
in,
I
think
in
a
couple
of
mrs
those
questions,
are
now
leading
or
could
lead
to
rework
unnecessary
lost
effort
and
and
yeah
that
compounds
over
time,
of
course,
but
I
think
it's
it's
good,
not
only
from
from
my
side
that
you're
doing
this,
but
as
you're
now
sharing
it,
it
seems
like
it's
also
has
been
a
good
experience
for
you
to
be
on
that
end
as
well
and
understand
how
things
happen:
yeah
yeah,
it's
fun,
so.
A
I
use
my
local
gdk
because
it's
set
up
and
is
generally
there
and
so
I'm
fairly
comfortable
in
moving
around
in
it,
because
I
haven't
been
using
gitbug
and
like
I,
I
have
a
macbook
that
can
like
run
it.
I
think,
for
whatever
reason,
I
made
a
good
decision
when
I
started
and
got
like
the
the
macbook
with
32
gigs
of
ram
and
like
the
i9
pro
so
like.
Oh.
A
So
like
I
just
let
it
go
and
it's
fine
like
I
think
my
gdk's
been
on
for
like
a
week
and
a
half
at
this
point
like
and
just
up
and
I'm
sure
it's
up
right
now,
actually
yeah
kidding
and
like
it
doesn't
doesn't
faze
the
laptop.
So,
like
I
don't
mind,
that's
incredible.
B
Oh
okay,
so
never
mind
my
question.
Yeah!
You
have
double
the
ram
that
I
have
and
yeah.
For
me,
the
gdk.
It
was
always
a
bit
slow
so
but
not
like
freezing
the
computer,
but
using
the
g
git
pod
for
me
is
much
faster
and
yeah.
Everything
is
much
faster.
The
database
migrations
reconfiguring
updating
everything,
so
I
I
just.
I
only
use
the
git
bot
integration
now
and
it's
pretty
cool.
A
B
A
All
right,
so
this
is
the
allow
add,
comment
to
review
mr
and.
A
I
think,
like
we
probably
all
agree
that,
like
commenting
on
non-code
is
good.
I
think
the
question
is
is
like.
Is
this
the
experience
that
we
want
to
do
that?
Like?
Is
this
the
first
way
we
want
to
do
that
versus
like
something
more
aligned
with
what
we're
working
on
or
something
in
the
flow
of
a
review
is
sort
of
where
my
concerns
are.
B
Yeah
thanks
for
bringing
this
up
so
yeah,
I
think
we
agree
that
and
as
you've
also
experienced
recently
when
you're
reviewing
those
merge
requests
like.
Sometimes
there
are
comments
that
you
want
to
make
that
don't
relate
to
code,
it's
either
a
behavior
or
I
don't
know
something
like
it
could
be.
Even
like
asking
hey.
Can
you
link
to
the
issue
that
this
mr
relates
to,
or
can
you
add
screenshots
to?
I
don't
know
so
things
that
just
are
not
in
the
changes
or
even
commit
messages.
B
I
don't
know
crazy
things
and
right
now
the
experience
is
just
if
I.
B
B
B
You
mentioned
two
things,
so
one
of
them
is
okay.
So
if
we
add
this
ability
now
like
should,
why
are
we
adding
this
instead
of
focusing
on
maybe
making
this
experience
better
of
when
you're
submitting
a
review,
allowing
you
to
add
a
comment
and
and
have
a
better
experience
in
that
moment,
instead
of
having
to
go
back
to
the
overview
tab
and
then
to
this
comment
box,
and
then
you
add
the
comment
that
you
want
and
I
think
it's
they're
not
like
exclusive.
B
I
mean
we
could
do
this
first,
but
we
would
still
need
to
solve
this
right.
We
would
still
need
to
add
the
ability
for
people
to
add
non-code
comments
to
their
reviews.
So
this
feels
like.
B
If
we
solve
this,
we
would
be
solving
one
problem
while
also
making
way
for
people
to
add
comments
to
wrap
their
reviews
at
the
same
time,
and
it
could
buy
us
some
time
into
looking
more
into
the
submit
review
button
which
ties
into
the
other
thing
that
you
mentioned
like
the
handoff
and
then
perhaps
the
approve
as
well.
So
as
we've
seen-
and
I
don't
think,
there's
a
screenshot
here
but
maybe
yeah.
B
B
It's
in
a
different
way:
yeah
exactly
yeah,
so
but
I
mean
extending
this
interface
or
this
action
of
submitting
to
added
comments
or
adding
in
check
checkboxes
or
options
for
you
to
approve-
or
I
don't
know,
request
a
re-review
or
re-request
a
review
from
someone.
We
could
then
bake
that
into
this
functionality,
but
that
will
take
more
time
and
and
one
major
yeah.
So
that
would
take
more
time
basically
because
we
would
have
to
research
how
this
would
be
done.
We
have
to
design
it
properly,
yeah.
A
A
A
Sort
of
just
like
really
broken
to
me
like
and
not
one
that
I
think
like
if
we
thought
about
it
that
we
would
want
permanently,
I
think
like
if,
in
an
ideal
world
what
you'd
rather
do
is
like.
If
you
go
to
the
changes
tab
to
start
your
review,
because
that's
the
only
place
you
can
start
a
review
like
somehow
maybe
down
on
the
bottom,
where
we
say
like
pending
comments,
submit
review.
We
would
just
add
another
button.
B
A
And
put
it
back
into
the
page
right
to
me
like
you'd,
I
feel
like
you
as
a
user
when
you're
reviewing
that's
the
experience
you
want.
You
want
the
review
experience
and
like
working
in
that
other
one
feels
to
me.
It
just
doesn't
feel
like
the
experience
we'd
ever
want
to
support
right,
like
I
think
I
just
don't.
A
If
you
were
reviewing-
and
there
was
a
button
down
at
the
bottom
said
like
leave
a
general
comment
or
leave
comment,
and
it
wasn't
tied
to
a
line
of
code
then
like
that
would
be
sort
of
maybe
more
natural
or
you
know
we
think
about
potentially
like
how
to
leave
a
general
comment,
which
is
what
that
wants
to
solve,
and
I
would
say
we
haven't
thought
about.
How
would
you
want
that
flow
to
work,
but
to
me
it's
not
not
what
the
mr
is
doing.
So
if
the
mr's.
B
Yeah,
so
the
there's
a
disconnect
like
that,
you
have
to
jump
to
many
different
places
to
do
your
review
and
the
review
should
be
at
the
center
of
everything
and
adding
comments
replying
to
other
people,
commenting
on
the
changes
that
should
be
front
and
center
and,
like
you,
shouldn't,
have
to
move
to
the
other
corner
of
the
house
to
do
something
right
and
then
back.
B
It
but
I
think,
that's
another
problem
we
need
to
solve
because,
like
let's,
let's
just
focus
on
the
codes
at
the
moment
like
if
no
one
wants
to
or
needs
to
leave
a
general
comment.
B
They
still
need.
I
mean
unless
you're
here
in
the
changes
tab
but
sometimes
like
like
when,
when
things
change,
we
invalidate
the
comments
and
you
have
to
go
back
in
versions
if
you
want
to
find
the
outdated
threads.
That
happened
in
code
like
in
two
commits
ago,
or
something
like
that,
so
you
still
need
to
go
to
the
overview,
tab
and
leave
comments.
I
don't
know,
I
don't
think
I
have
one
here
now.
A
B
B
So
this
is
just
to
say
that
with
that
problem
already
existing,
the
only
thing
we're
just
saying
is
like
should
we
support
these
kinds
of
new
comments
to
be
added
to
review,
because
if
I
reply
to
paul
here,
it's
not
a
it's,
not
a
diff
comment,
but
I
can
add
to
my
review
a
reply,
but
a
new
one.
I
can't.
B
A
Adding
them,
I
think,
it's
having
to
navigate
to
the
overview
tab,
which
is
already
a
thing
that
we
have
as
debt
right,
where
you
can
go
and
comment
on
an
existing
thread.
But
that's
because
we
sort
of
and
like
let's
take
that
like
back
one
right.
The
reason
we
invalidate
in
the
diff
view
is
because
we're
now
showing
you
against
the
latest
version
and
that's
why
it's
not
there,
but
we
save
those
discussions
on
the
discussions.
A
And
all
of
it
being
one
thing,
I
don't
know
that
we'd
ever
do
that,
but,
like
I
guess
mike,
would
you
say
that,
like
the
ability
to
are
there
a
user
having
to
go
the
second
time
they're
reviewing
so
like
they've,
already
done
a
review
pass
once
the
second
time
they're
going
and
doing
a
review,
I
mean:
do
you
think
the
right
experience
is
the
one
we
have
today
where
you
have
to
bounce
back
and
forth
between
the
changes
in
overview
tab?
A
A
A
I
mean
that
means
just
bouncing
back
and
forth
between
tabs
would
sort
of
go
away
at
some
point
but
like
if
users
are
now
like
using
this.
This
path,
like
we've,
got
we've
got
to
deal
with
that
as
part
of
that
you've
got
to
like
take
into
account
all
of
the
workflow
like
problems
that
you've
built
when
you
like
go
to
build
the
new
one
right
so,
except
like
I
to
me,
it
feels
like
we
would
do
it.
A
A
You
have
to
go
back
and
forth
between
the
two,
but,
like
we
added
this
feature
to
support
you
going
back
and
forth
between
the
two
and
like
yes,
one
already
exists,
but
one
already
existing
doesn't
mean
it's
right
and
that
we
should
like
continue
with
that
pattern.
It
right
we
should
maybe
think
like.
Is
that
the
pattern
we
want
to
continue
with.
B
Okay,
okay,
so
let's
let's
go
back
a
little
bit
and
let's
imagine
that
today
the
only
comments
that
you
can
add
to
review.
You
always
need
to
add
them
in
the
changes
tab
so
replying
to
comments
here
in
the
overview,
tab
or
adding
them
here.
It's
not
supported
at
all
right,
so
reviews
always
always
happen
here.
B
It's
something
that
we
should
support
and
that
the
way
that
you
add
them
and
the
way
that
you
navigate
to
them
it's
something
that
we
could
improve
for
sure.
But
I
don't
see
that
as
exclusive.
I
don't
I
don't
foresee
us
cornering
ourselves
and
not
being
able
to
get
out
of
a
certain
approach,
because
we
did
it
because
the
intention
is
there
like.
What
we're
saying
is
is:
is
the
intention
to
add
a
non-code
comment
to
a
review
valid?
Yes.
B
A
A
A
We
don't
think
is
the
right
pattern
and
like
you'll,
build
user
habit
and
other
things
like
for
that
pattern,
whereas
if
we
think
commenting
on,
if
we
think
a
non-code
comment
is
part
of
the
review
is
like
useful,
then
like,
we
should
figure
out
how
to
do
non-code
comments
as
part
of
the
review
from
the
place
where,
like
the
reviews,
predominantly
take
place
and
like
otherwise
like
well
like,
and
I
would
say
inevitably
based
on
the
way
we've
all
seen,
gitlab
work.
A
What
would
happen
is
we
would
just
build
a
new
method
like
let's
say
we
decide
that
like
we
just
want
to
add
a
button
to
the
bottom
of
this
bar.
That
says
like
comment,
and
we
do
that
and
it
pops
up
a
comment
box,
and
we
do
that
like.
A
Inevitably,
that
will
exist
and
it
will
coexist
with
that
other
one
that
we
don't
like,
because
we
won't
take
it
away
unless
we're
like
very
explicit
and
thoughtful
and
saying
like
we
don't
want
that
one
to
be
the
thing
anymore,
because
this
is
the
workflow
we
want
and
like.
We
need
to
be
that
thoughtful
and
explicit,
and
I
would
say
historically
gitlab
is
not,
and
you
end
up
with,
like
sort
of
all
of
these
workflows
right.
B
I
would
say
that
if
that
were
like,
if
we
didn't
do
this-
and
this
would
still
be
the
experience
starting
a
thread
or
closing
so
you
wouldn't
be
able
to
add
the
review
and
let's
imagine
we
then
do
what
you
were
suggesting.
I
mean
it
doesn't
need
to
be
exactly
what
you
suggested,
but
let's
imagine.
A
B
For
a
second,
so
we
would
add
a
comment
here
and
it
would
be
in
the
review
and
it's
not
attached
to
a
diff.
We
would
still
need
to
think
how
this
path
of
adding
a
comment
through
this
area.
B
A
Well,
I
mean,
but
that's
like
the
yeah.
It
will
be
published
there
until
one
day
if
we
decide
that,
like
the
fact
that
there's
an
overview
and
a
changes,
tab
and
like
those
comments
exist
in
sort
of
both
places
depending
on
a
random
group
of
settings,
is
like
not
correct
either,
and
we
go
and
fix
like
that
larger
problem.
Right
like
we
go
and.
B
A
Like
that's,
probably
not
a
good
experience
right,
like
I
think
to
me
like
there's
a
lot
of
like
layered
experiences
here
and
like.
Ultimately,
if
you
go
all
the
way
to
the
top
I'd
say
the
fact
that,
like
the
overview
and
the
changes
tab
can
show
different
content,
depending
on,
like
which
version
you're
looking
at
at
any
given
point
in
time,
is
like
probably
not
good,
and
we
probably
agree
that
that,
like,
ultimately,
that's
like
the
real
problem.
A
B
Okay,
okay,
so
my
question
is
so
we
agree
both
agree
that
it's
the
navigation
of
comments
and
having
to
go
back
and
forth
is
broken.
How
how
much
of
a
priority
is
it
like?
Is
it
something
that
we
will
prioritize
and
work
on
soon,
because
that
to
me
is
what
that's
the
only
thing
here
like
if
you
tell
me
we're
gonna
start
working
on
it
like
next
milestone
or
two
milestones
from
now.
B
But
if
we're
not
going
to
do
that
soon,
we're
basically
saying
hey
we're
not
going
to
do
this,
so
you're
going
to
still
live,
live
with
this
inconsistency
and
having
to
jump
back
and
forth
and
having
to
add
your
comments
here
until
we
work
on
that.
A
Do
you
like?
Do
we
think
that
piece
of
it
is
involved
in
that
in
a
way
that
like
in
order
to
communicate
the
status
of
the
mr,
we
need
to
rethink
how
we
like
deal
with
versions
and
deal
with
like
comments
and
all
of
these
things
and
like
would
that
lead
us
down
a
path
that
like
we
would
do
that,
and
I
don't
know
that
I
think
there's
the
one
path
where
we
would
be
fairly.
A
B
A
B
Yeah,
I
think,
to
be
honest,
we're
very
well
I'll,
remove
the
very
we're
far
away
from
having
the
ideal
experience
that
solves
the
tracking
problem
and
this
publishing
problem
and
adding
to
a
review
properly,
because
those
things,
as
you
said
like
we
could
go
down
a
path
and
solve
both
things.
At
the
same
time,
because.
A
B
B
While
looking
at
the
code
for
example,
so
you
could
always
have
a
list
of
more
or
less
your
to-do's
inside
of
the
merge
request
and
you
could
jump
back
and
forth
through
them
without
having
to
know
if
they're,
in
the
overview
tab
if
they're
in
the
changes
tab,
if
they're
in
version
one
in
version
two
and
version
three,
it
doesn't
matter
and
that
experience
or
something
else
that
solves
it.
I
think
we're
far
away
from
that,
because
it
will
be
to
solve
this
properly.
B
I
imagine
that
it
would
probably
be
a
departure
from
the
current
experience,
significant
departure,
so
we'll
probably
have
to
test
it
as
well.
We'll
have
small,
iterations
refactorings
blah
blah
blah
blah
blah.
So
that's
yeah,
I'm
more
concerned
about
like
delaying
this,
and
even
if
we
prioritize
it,
it
will
take
some
time
us
to
get
there.
B
A
A
B
A
Yeah
yeah,
I
will
do
it
I'll
take
care
of
it
later
today.
Okay,
cool.
A
The
the
chat
about
it
and
yeah
enjoy
enjoy
the
rest
of
your
day.
I'm
gonna
jump
since
I'm
late
for
my
next
one,
but
I
will
yeah.
We
will
chat
and
enjoy
enjoy
your
your
kid
day
tomorrow.
Hopefully
it
it's
fun,
I
don't
know.
Sometimes
they
can
be
yeah.
B
Cool
yeah,
good
luck
with
the
rest
of
your
day,
yeah.