►
From YouTube: 2021-07-14 Create:Code Review Weekly 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
Right,
hi,
everyone.
I
can
take
my
first
point
in
the
agenda
for
the
weekly,
so
some
of
you
might
have
seen
this
already
on
slack,
but
I
wanted
to
capture
here
the
news:
justin
boysen,
our
esteemed
front-end
senior
engineer
has
his
last
day
tomorrow
he
will
be
leaving
the
team.
I've
already
shared
my
thoughts
and
my
thankfulness
for
his
contributions.
On
slack,
please
take
a
look
and
so
yeah
the
the
news
that
hit
us
in
the
past
in
the
past
week,
thomas
you're,
coming
back
to
this.
A
I
think
you've
seen
this
on
the
day,
but
we
can
talk
about
it
separately,
but
I
wanted
to
take
the
opportunity
to
thank
him
again
and
to
wish
him
well
on
the
next
efforts.
Should
he
be
seeing
the
recording
he's
not
here
and
and
yeah.
I
wanted
to
give
a
bit
of
an
insight
about
how
we
plan
to
do
things
in
the
future
in
the
short
term,
so
for
14.2
there
will
be
a
reduced
capacity.
A
We
won't
be
able
to
cover
for
him
right
away,
but
we
are
working
to
publish
the
backfield
position,
so
we
will
be
hiring
someone
to
fill
his
position.
A
It's
not
clear
whether
once
we
open
it
up,
if
we'll
have
internal
candidates
or
not
to
so
that
we
can
consider
them,
but
we
will
be
working
to
make
this
refilling
as
quickly
and
has
and
as
useful
as
possible,
so
we'll
be
looking
for
someone
who's
comfortable
working
in
you
know
a
complex
code
basis,
like
our
merge
requests,
experience
with
view
all
that
stuff.
So
that's
why
we're
looking
for
a
very
senior
and
robust
engineer
such
as
justin
was
and
yeah?
I
I
do.
I
do
plan
on
on.
A
Potentially
tom
tomasz
has
been
kind
enough
to
to
to
agree
to.
If
you
need
to
pick
something
else,
a
little
bit
extra
than
usual
from
the
git
club
work
he's
able
to
do
that.
We
will
still
be
mindful
to
keep
a
large
capacity
for
vs
code
stuff
on
him,
but
but
yeah
that's
what
we're
planning
to
do
for
the
short
term.
And
yes,
I
wanted
to
see
if
you
have
any
questions
about
that
plan.
C
A
Okay,
do
you
have
any
questions,
thomas
tomas,
no,
okay,
so
my
next
one
performance
updates.
I
wanted
to
draw
attention
to
the
slack
update
that
I
dropped.
Those
numbers
are
coming
from
a
test
that
we've
been
running
on
a
merge
request
on
gitlab
fast
project.
It's
not
our
reference,
merge
request,
but
this
has
to
be
said,
so
these
numbers
will
not
be
translating
directly
to
the
numbers
that
we
see
on
the
okr.
A
That's
a
different
merge
request,
tested
in
a
different
environment,
but
that
environment
can
only
test
things
where
the
feature
flag
is
default
on
right
now,
and
I
think
we
want
to
keep
that
so
that
we
track
what's
being
felt
by
users
everywhere,
including
customers.
So
we
don't
want
to.
We
could
hack
it
and
turn
the
feature
flag
on
on
those
tests
from
quality
teams,
but
we
don't.
A
I
don't
think
we
want
to
do
that,
but
we
still
have
this
ability
to
test
the
impact
in
production
on
a
special
on
a
large,
mr
that
we've
been
tracking
over
the
course
of
I
don't
know
months,
so
we've
been
able
to
see
the
the
decrease
and,
proportionately
speaking,
it
is
pretty
impressive,
so
yeah
the
numbers
look
great,
I'm
not
sure
if
this
will
get
us
across
the
line
that
we
need
to
go
for
the
goals
of
the
okr,
but
we
still
have
some
other
things
in
in
flight.
A
B
Yeah,
it's
amazing,
I'm
pretty
impressed
with
the
numbers
and
I'm
I'm
excited
to
get
it
out
in
14
2
and
then
start
to
see
the
reports
of
the
mr.
We
were
measuring
against
because
I
imagine
now
at
this
point
we'll
have
to
like
sort
of
retroactively,
go
back
to
show
progress
or
I
don't
know
how
the
okra
work
in
terms
of
like
showing
the
progress
that
we
made.
But
I
can
I.
A
Can
speak
a
little
bit
about
that,
so
the
the
okr,
as
we
know,
is
tracked
at
the
monthly
level,
and
there
is
that
thing
about,
even
though
the
work
is
being
shipped
to
customers,
it's
not
being
enabled
for
customers
in
self-hosted
instances,
but
as
soon
as
we
have
it
default
on,
I
think
it's
fair
for
us
to
guards
the
the
progress
as
real,
because
we
are
being
very
careful
with
the
rollouts
and
so
yeah
we
will
at
the
end
of
the
july,
we
will
be
able
to
score
the
okr
immediately
because
the
tasks
on
the
quality
team
they
run
on
a
nightly
and
they
run
on
their
own
environment.
A
B
Cool
yeah,
I'm
I'm
excited,
I
think
it's
phil
has
put
in
a
ton
of
hard
work,
as
is
pedro
and
making
sure
that
it
was
a
usable
experience.
So
hats
off
to
both
and.
A
You
too,
kai,
because
I
think
this
is
the
benefit
of
having
this
shadow
kr.
I
think
this
is
one
of
the
cases
where
product
understanding
the
benefit
of
going
deep
on
a
technical
effort
pays
off
on
the
on
the
perspective
perception
from
customers
as
well,
but
I
don't
want
to
take
that
lightly.
We
really
appreciate
your
capacity
to
just
allow
us
to
go
and
play
with
a
little
code
without
shipping
new
features,
so
that
also
plays
into
this
success.
So
thank
you
for
that
too,
cool
too
much.
Do
you
want
to
add
anything?
C
Yeah
I'm
super
excited.
I've
sometimes
said
that
the
metric
west
side
was
just
sad
said,
work
with
what
this
looks
like
it's
going
to
be
a
massive
massive
improvement
and
hats
off
to
everyone
involved.
As
everyone
said
before,.
A
Yeah
and
I
want
to
acknowledge
phil's
contributions
and
and
stubbornness
on,
pushing
the
virtual
scrolling
forward.
Thank
you
profusely
for
those
efforts
and
patients
going
through
the
fixes.
Thank
you
also
for
everyone
who
participated
in
investigations
in
in
scoping
things
out
and
trying
to
clear
out
some
things
that,
even
though
they
didn't
pan
out
they
did
we
kind
of
verified
that
they
wouldn't
work.
A
Just
did
some
some
some,
some
digging
thomas
did
some
investigations
from
the
index
db
as
well,
that
we
haven't
pursued
yet,
but
it's
still
there,
but
yes
and
tim
is
also
shipping,
some
satellite
improvements
on
icons
and
stuff
around
the
around
the
the
mr
that
it's
definitely
appreciated,
even
though
the
big
bulk
of
the
impact
that
definitely
comes
from
this
okr
attention
and
and
feels
shipping
that
stuff
cool
that
takes
care
of
that,
and
my
next
one
is
something
that
pedro
being
me
on
and
since
we're
finalizing
the
planning
for
14.2,
I
thought
I'd
bring
it
up
here.
A
This
is
like
the
next
iteration
of
attention,
requests
or
just
reviews,
I
guess-
and
as
we're
starting
to
consider
the
upcoming
milestones,
because
this
next
one
will
already
be
going
over
to
the
next
quarter.
I
just
wanted
to
check.
Is
this
on
the
right
path?
Is
it
missing
anything?
This
is
this
breakdown
that
I
linked
there
to
be
able
to
implement
this
attention
requests.
Does
anybody
has
feedback
on
that.
B
I
haven't
looked
at
it
yet
I'll.
Just
say
that
I
know
designs
are
all
in
and
done
so
I
think,
like
everything
exists,
so
it's
probably
up
to
you
and
the.
B
Sure
that,
from
a
front-end
perspective
that
you're
good
from
a
back-end
perspective,
I'll
probably
ping
it
it
can
really,
it
can
wait.
We're
not
planning
on
scheduling
any
of
this
for
14
too
just
giving
capacity
sort
of
across
the
board.
We
won't
have
the
space.
So
the
goal
is
to
try
and
figure
out
what
will
it
take
and
then
maybe
we'll
start
trying
to
slot
some
of
it
in
in
14
3..
So
we've
got
some
more
time
if
you
want
to
get
people
to
actually
spend
the
time.
A
There's
a
couple
of
question
marks
around
there,
especially
about
capacity
weights
from
back
end,
and
it
would
be
good
to
do
some
sort
of
validation
so
that
we
go
in
and
so
that
we
don't
end
up
with
forgetting
api
calls
and
stuff
so
yeah.
We
might
drive
this
conversation
alongside
14
2,
but
that
works
for
me
and
I
can
draw
my
attention
to
something
else:
cool.
A
B
You
know
I
will,
I
will
put
this
issue
in
only
because
there's
people
here
that
may
want
to
be
interested.
I
had,
I
have
been.
B
Thinking
about
what
it
would
take
to
build
another
editor
extension.
B
Specifically
in
in
the
jetbrains
ecosystem,
because
we
see
it
come
through
a
lot
for
customers
and
like
it's
tangentially,
mentioned
in
a
lot
of
places,
and
then
it's
also
widely
used
at
gitlab.
Some
of
the
various
editors
here
used
by
engineers
at
gate
lab.
So
I
had
been
pondering
it,
but
I
think
one
of
the
key
things
that
we'd
have
to
figure
out
is
if
we
were
to
go
down
this
path,
sort
of
what
we
would,
what
we
would
need
in
terms
of
staffing
or
people
or
all
those
kinds
of
things.
B
B
So
if
anyone
has
ideas
feel
free
to
share
it
amongst
your
team,
andre
all
the
teams,
I'm
happy
for
anyone
to
sort
of
think
about
what
might
be
valuable,
especially
if
we
have
jetbrains
users
that
have
thoughts
on
what
they
would
want
to
do.
B
A
Yeah
he
can
take
care
of
everything
on
the
pipeline
for
the
vs
code
once
he's
done
just
start
over
start
over
again
in
another
platform,
I
guess
extensions
are
like
websites
they're,
never
really
really
done.
That's
that'll
be
hard,
but
thanks
for
raising
this,
it's
something
definitely
for
thought.
I
I
will
circulate
this
across
some
some
of
the
front-end
folks
as
well,
that
use
jetbrains
products.
They
might
have
some
feedback
on
it
in
terms
of
like
valuableness
of
it
and
stuff.
A
So
yeah
thanks
also,
I
don't
have
any
thoughts
at
this
moment.
I'm
I'm
like
you
wary
of
like
picking
another
platform,
but
definitely
worth
having
a
chat.
B
Yeah,
I
think
for
me,
it's
we'd
have
to
know
where
we
want
to
start
and
then
I'd
probably
still
go.
Do
like
the
product
e
opportunity,
canvas
things
and
get
some
executive
buy-in
just
to
make
sure
that
we
don't
go
in
in
a
direction.
They're
not
interested
in.
I
think
we're
seeing
good
numbers
with
vs
code,
so
it
makes
it
the
growth
there
is
happening
quickly.
B
So
I
think
it's
some
validation
that
if
we
get
into
more
places
where
people
are,
I
think
that's
that's
good,
and
if
we
can
do
it
with
minimal
minimal
effort,
then
that's
okay,
too.
So.