►
From YouTube: Create:Code Review Backend 16.3 Retrospective (2 of 2)
Description
The Create:Code Review backend team met to discuss the 16.3 milestone. We had 2 meetings across timezones. You can find the other video here: https://youtu.be/nh3DlYw-Hjk
A
A
All
right,
this
is
the
code
review
retrospective
for
16
3..
This
meeting
two
of
two
we
had
one
earlier
today
with
Gary
and
I,
which
I
also
recorded
and
I'll
share
both
of
these
with
everyone
later
so
yeah
I,
don't
know
Central
or
Carrie.
If
you
have
anything,
you
wanted
to
to
bring
up
right
away
any
initial
thoughts
or
ideas
about
about
the
Milestone
things
that
you
want
to
talk
about.
C
B
And
there
was
a
so
I
made
a
change,
but
I
shared
my
photo,
but
that
may
not
be
the
best
one
to
do
so.
I
started
conversation
towards
the
end
of
almost
the
end
of
the
Milestone
like
15th
or
something,
and
that
triggered
the
conversation
dragging
long
and
then
it
went
over
that
Milestone
and
then
in
the
end
we
had
a
test,
but
we
got
it
merged.
B
So
in
that
kind
of
scenario,
I
should
have
let
it
just
go
through
the
review
process,
because
that's
the
upgrade
thing
to
do
so
then,
after
that
maybe
I
have
opened
up
another.
You
know
issue
or
something
to
discuss,
but
that
would
have
been
a
better
approach.
So
it'll
be
a
change
of
how
I
approach
things
may
improve
that
you
know
kind
of
the
Liberals
slippage
kind
of
thing,
so
yeah.
B
C
C
C
Do
the
bureaucracy
or
the
process
work
of
making
sure
that
the
labels
are
correct
and
the
assignments
are
correct
for
like
Milestones,
but
then
to
create
an
issue
for
the
deliverable
like
the
investigation,
work
or
I
need
to
have
a
conversation
with
giddly
team.
So
I'll
make
an
issue.
That's
you
know,
have
a
conversations
daily
team
just
so
that
I
can
kind
of
track
it
and
also,
like
you,
know,
kind
of
just
kind
of
show
that
there's
iterative
progress
on
things
I'm,
not
always
good
at
doing
that,
that's
the
that's
the
ideal!
A
Yeah
I
think
yeah
I'm,
trying
to
I'm
struggling
with.
How
do
we
I
feel
like
we
have
a
lot
more
investigation
issues
so
in
general
lately,
which
could
be
contributing
to
this
as
well
yeah?
How
do
we,
how
do
we
kind
of
iterate
an
investigation
and
or
how
do
we
is
an
investigation
issue,
really
a
deliverable?
Maybe
those
aren't
actual
deliverables.
Maybe
that's
just
work
that
we
do
in
a
milestone
that
we
don't.
We
don't
are
we
aside
and
we
work
on,
but
we
don't.
Maybe
we
don't.
A
C
C
Think
I've
got
like
two
I've
got
an
epic
two
children,
ethics,
eight
or
nine
issues
like
it's,
this
whole
thing,
but
it
doesn't
have
to
always
be
like
that,
but
we
can
make
an
investigation
issue
that
blocks
a
deliverable
issue
right
right,
I
mean
at
the
end
of
the
day
like
this.
What's
the
what's
the
goal
at
the.
B
A
That's
a
good
question:
yeah
I,
think
part
of
it
is
and
I
don't
know
that
anyone
is
really
kind
of
tracking
it.
So
I
think
a
year,
maybe
18
months
ago.
It
was
more
of
a
thing
that
people
were
kind
of
monitoring,
deliverables
and,
like
a
say,
do
ratio,
but
that
kind
of
fell
out
of
fashion
I
guess
for
for
better
lack
of
a
better
word
and
then
maybe
it's
because
not
every
team
is
doing
it
the
same
way.
A
C
A
I
looked
a
little
bit,
it
seemed
like
we
were
on
a
decent
kind
of
consistent
track,
and
then
all
this
AI
stuff
happened,
which
threw
us
for
a
loop
understandably
and
threw
us
for
a
loop
like
the
planning-wise
I,
should
say,
and
now
that
that's
kind
of
winding
not
winding
down,
but
getting
a
little
more
stable,
a
little
more
predictable
of
what
what
work
is
coming.
We're.
B
C
Yeah
I
mean
it
might
just
be
because
I'm
taking
on
or
I
get
assign
some
of
the
weirder
stuff
lately,
like
I
I,
I
I
I
feel
like
I've.
Seen
more
like
you've
thrown
me,
the
occasional
I
feel
like
I've,
released,
Matt
you've
thrown
me.
Some
weird,
like
this
bug's
been
around
for
five
or
six
years
and
Nick
left
some
notes
on
it
three
years
ago
and
I'm
like
is
this
even
still
relevant,
like
I,
have
to
go
back
and
almost
reproduce
it
and
start
off
from
scratch.
C
B
I'm
just
wondering
about
those
things
like
just
to
get
an
idea,
he's
saying
it's
about
six
years
old
issue.
Right
like
is,
it
does
came
up
because
people
keep
having
the
issue
or
is
it
just
the
issue
that
created
like
six
years
ago
when
no
one
looked
at
it,
and
then
we
just
suddenly
picked
it
up.
I'm
just
wanted
to
understand
that
that's
the
issue
that
really
needs
to
be
fixed,
or
is
it
something
that
I
don't
know?
We
just
have
nothing
else
to
do
so.
Okay,.
C
C
B
B
B
That
I
was
gonna
say
that
I
was
just
curious
to
know
that
whether
it
was
the
bug
that
consequently
happened
to
me
and
then
it
didn't
have
time
to
eventually
fix
it,
and
now
we
are
mixing
it
or
whether
it
happened
like
long
time
ago,
a
couple
times
and
yeah
like
we
just
think
it
needs
to
be
fixed.
Like
I
said,
there
are
two
different
things
right.
So
that's
what
it's
understand.
A
And
like
that
that
merger
dependency,
one
I
think,
is
one
that
it's
like.
Yes,
we
should
fix
that
and
then
it's
it's
always
complex
and
it's
always
been
complex
and
we
always
find
a
reason
to
push
it
out,
because
it's
complex
and
now
we're
getting
the
point.
It's
like
yeah,
maybe
now's
the
time
to
do
that
and
then
we're
like.
Oh
yeah,
that's
right.
It
is
really
complex
and
like
it
is
going
to
take
a
lot
of
work
and
we
never.
A
B
A
C
I
want
to
not
take
I,
don't
I'm
not
trying
to
take
blame
or
anything
for
this,
but
I.
My
I
wonder
how
much
impact
I'm
having
because
I
will
tag
other
people
into
issues.
Quite
group
only
to
say
you
know:
hey
you've
got
experience
or
expertise
or
you're
more
familiar
with
this
particular
area
and
I.
Don't
know
if
maybe
I'm
contributing
to
some
distraction
with
that.
If
that's
something
I
can
improve
and
I
know,
I
do
this
to
you
since
y'all
a
lot
and
I
do
this
to
Patrick
as
well.
C
B
Yeah
I
think
like
at
least
for
mine.
What
do
you
know?
I,
don't
think
I
mean
like
obviously
it
you
know
by
definition,
is
the
distraction,
but
it's
not
I.
Don't
consider
to
be
a
you
know.
Negative
destruction,
I
think
that's
something
that
we
all
need
to
do
as
a
hard
work,
so
that
never
then
the
you
know
any
issue
for
me.
So
that
was
fine.
C
B
I
think
it's
sort
of
related
to
different
things.
The
other
thing
that
I
was
going
to
mention
in
the
other
issue
that
I
just
commented
is
that
I
think
it
kind
of
feels
more
distracted
about
the
preview
requests
that
are
coming
in
then
these
ones
like
U.S
and
it's
the
ones
that
you
are
commenting
on
at
least
I
touched
on
and
as
I
know
something
about.
So
it's
easier
for
me
to
understand
or
like
try
to
remind
myself
what
I
did
and
stuff
like
that.
B
So
it
seemed
to
make
sense
for
me
to
do
that
then
bunch
of
Mrs
that
I
have
no
idea
what
it's
about.
I
need
to
go
and
figure
it
out
or
what
it
does
and
then
trying
to
you
know
do
stuff,
that's
more
distracting,
but
also
at
the
same
time
we
constant
consider
them
to
be
a
higher
priority
than
our
deliverables
right.
So
by
default
we
wanted
to
let
someone
else's
work
to
go
through
instead
of
focusing
our
work.
So
by
doing
that,
you
delay
your
deliverables,
so
I
guess
that
that
feels
more
distracting.
B
B
A
B
A
B
A
A
B
Yeah,
just
because
I
got
a
little
bit
confused
when
I
looked
at
the
issues
that
made
when
I
clicked
some
of
them.
Quite
a
few
of
them,
are
thrown
in
stuff
and
okay,
like
design
or
whatever
and
stuff
like
that
and
I,
don't
see
them
being
assigned
as
part
of
the
Retro.
So
if,
if
the
focus
of
having
this
retro
is
for,
back-end
may
be
helpful
to
read
out
those
things
and
just
have
the
back-end
stuff,
so
we
have
clearer
understanding
of
what.
A
A
A
Maybe
I
can
talk
to
Andre
and
see
if
we
can
to
get
get
a
little
more
more
activity,
AI
I'm
a
little
overzealous
trying
to
get
get
feedback
so
I
tag
you
and
I,
assign
you
and
try
to
try
to
do
whatever
I
can
to
try
to
squeeze
some
feedback
out
of
everyone
which
I
really
appreciate
the
the
time
that
people
put
into
it.
So
thank
you.
C
C
C
C
C
A
C
I
think
that
here
I
mean
I,
think
Gary
mentioned
called
out
specifically
Patrick
for
collaboration,
but
I
would
want
to
like
expand
that
to
say
that,
yet
again,
everybody
is
seems
to
be
really
helping
out
and
working
together,
so
I
mean
I
would
under
I
would
underline
that
and
not
you
know,
let's
not
lose
Factor
like
that.
That's
actually
a
really
good
thing,
even
though
we
do
it
all
the
time.
It's
still
a
really
valuable
trait,
and
it's
not
it's
not
Universal.
A
C
I
also
see
us
all
getting
pulled
into
other
neighboring
teams
projects
a
lot
of
that
with
security,
giddly
and
AI
work
and
I.
Think
that
we're
you
know
that
that's
one
of
the
causes,
one
of
the
causes,
one
of
the
suspected
complications
around
the
deliverable
thing,
but
also
the
fact
that
we
are
a
team
that
is
going
to
be
doing
that
work
and
I
see
I,
see
us
doing
it
and
that's
that's,
really
super
valuable
react.