►
From YouTube: 2021-07-13 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
All
right,
so
I
have
the
first.
A
I
have
all
of
the
items
in
the
agenda
yeah,
so
the
first
one
is
a
read
only
for
you
to
check
on
interesting
feedback
that
we've
had
in
the
past
and
ux
parodies,
and
I
was
basically
this
morning
looking
at
everything
that
I
have
on
my
plate
at
the
moment
that
I
expect
to
work
on
soon,
also
looking
at
what
we
have
in
that
google
sheet
that
we're
collaborating
on
for
about
the
problem,
areas
of
code,
review,
possible
paths,
issues
and
trying
to
make
some
sense
of
it
all
and
yeah.
A
I
just
want
to
start
looking
at
all
of
the
priorities
that
we
have
for
the
short
term
and
also
to
prepare
the
groundwork
so
that
when
annabelle
starts,
she
is
already
as
onboarded
as
possible
and
ready
to
go.
And
so
I
have
some
suggestions
here
of
what
I
was
thinking
but
I'll.
A
I
mean
I
added
this
because
I
also
want
your
thoughts
and
it
would
be
nice
to
then
share
this
recording
with
annabelle
as
well.
Yeah
I
can
go.
I
can
go
quickly
describing
one
by
one
and
and
if
you
have
questions
you
can
interrupt
me
or
if
you
have
any
questions
right
now,.
B
A
About
this
yeah
yeah,
the
next
quarter
or
two
things
that
we
can
say
that
more
or
less
that
we
will
be
working
on
long
more
in
the
future
than
this.
I
think
it's
it's
difficult
at
the
moment.
A
A
Not
yeah,
not
necessarily
personal,
but
so
I
let
me
highlight
these
in
yellow,
for
example,
so
the
ones
in
yellow
are
the
ones
that
are
yeah
more
personal
to
me
and
don't
have
a
direct
impact
on
the
group.
But
it's
something
that
I'm
that
I
want
to
work
on
outside
of
the
code
review,
milestone,
work.
A
So
yeah
the
first
thing
is
and
then
just
to
to
make
sure
that
is
a
correct
interpretation.
Is
that
for
the
machine
learning
to
suggest
reviewers
we're
still
yeah
we're
still
in
the
engineering
phase,
so
it
will
take
some
time
for
us
to
get
to
a
place
where
we
can
start
thinking
about.
The
experience
is
that
a
correct
assessment.
B
B
I
would
expect
probably
starting
in
another
six
weeks
we
might
start
to
see
stuff
show
up
or
start
to
like
at
least
have
something
we
can
interact
with,
maybe
or
experience
in
a
way
or
need
to
start
having
those
conversations.
So
we're
probably
still
another
like
four
to
six
weeks
away.
B
Yeah
I
haven't
been
to
a
meeting
in
a
couple
weeks,
but
I'll
make
sure
that
we
do.
C
B
The
flip
side
would
be
I
I
actually
think
that's
fine,
I
think
four
to
six
weeks
is
fine,
because
otherwise,
like
the
other
option,
would
be
like
try
and
experience
unreview
in
its
current
form,
and
I
don't.
I
don't
think
that
really
matters,
maybe
it
matters
when
you
start
thinking
about
experience,
but
I
don't
know
that
that
matters
yet
so.
A
But
today
unreview
doesn't
have
any
representation
in
our
ui.
Does
it
correct
it
does
not?
Okay,
okay,
yeah!
So,
okay,
let
me
let
me
know
when
you
think
because
you're,
I
think,
invited
to
those
weekly
or
bi-weekly
meetings.
Let
me
know
how
you're
feeling
about
that
and
when
you
think
might
be
a
productive
time
for
us
to
to
start
talking
about
the
ux,
and
then
we
can
figure
out
how
we're
going
to
support
that
and
who
will
be
supporting
that.
A
Okay,
I
can
do
that.
Okay,
thanks
yeah.
So
for
me,
so
that's
a
point
c
federal
leads-
and
this
is
my
what
I'm
thinking
right
now
is
in
the
next
milestone.
A
I'm
going
to
look
at
consolidating
the
mr
action
so
following
through
with
what
sun
jung
did
trying
to
put
all
of
the
main
actions
of
the
mr
at
the
top,
and
so
that
would
be
doing
a
review
of
what
we
currently
have
to
make
sure
all
of
the
cases
are
covered
and
prepare
solution,
validation
for
that
and
also
do
the
final
design
with
mobile
considerations.
A
So
that
would
take
some
time
during
that
milestone,
but
I'm
confident
if
I
start
doing
that
we
should
have
or
actually
let
me
see
so
next
milestone
starts
next
week
and
yeah
it's
going
to
going
to
be
short,
a
very,
very
short
milestone
for
me,
but
yeah,
I'm
sure
we
will
make
some
progress
there.
A
A
We're
we're
yeah
we're
making
progress
on
it
me
and
ann
the
ux
researcher,
she's
helping
me
out
in
this.
I
don't
know
if
we
will
complete
everything,
but
the
ones
that
I'm
mostly
interested
in,
which
are
predicting
the
task
times
and
trying
to
collect
all
of
the
performance
information
that
we
have
about.
The
merge
request
experience
in
one
place
in
the
handbook
that
should
be
completed
in
by
14
2.
A
And
yeah,
the
other
things
that
I
said
are
more
tangential,
tangential
work,
aligning
the
code
review
direction,
and
that
is,
I
think,
a
bit
dependent
on
the
conversations
that
we've
been
having
another
thing
is
sharing
best
practices,
and
that
is
another
personal
thing.
B
C
A
Okay,
so
that
would
be
based
on
the
conversations
that
we've
been
having
and
what
we're
putting
together
in
the
prioritization
of
problem
areas
and
also
these
surveys
that
we
had
we
sent
out
the
external
and
internal
survey
and
also
what
we
discussed
some
time
ago
about
aligning
our
direction
to
first
and
foremost,
make
gitlab
the
company
as
efficient
as
possible
and
and
align
things
to
our
code
review
practices
is
to
put
all
of
that
together
into
an
updated
direction
where
we
clearly
say
like
these:
are
our
goals
for
or
our
themes
for
the
next
I
don't
know.
A
I
don't
know
if
I
can
say
year,
but
at
least
the
next
two
quarters,
at
least
and
after
that
would
be
recording
a
video
walkthrough
of
that
trying
to
explain
that
as
best
as
possible
and
trying
to
share
that
with
the
group
with
the
whole
team,
so
that
everyone
on
the
team
and
the
engineers
feel
like
they
know
what
the
direction
is
and
know
where
they
can
contribute
ideas
and
start
thinking
about
investigation
work
and
so
on.
Yeah.
That's
how
I'm
thinking
about
it
now,
but
at
least
it's
in
the
end.
A
The
goal
is
to
align
our
plan
and
our
roadmap
to
to
user
needs
and,
and
also
I'm
not
going-
I
I
don't
want
to
say
customer
requests,
but.
B
A
And
this
yeah,
I'm
I'm
putting
this
under
like
federal
leads,
but
in
in
s
in
reality,
this
is
not
a
word
that
I'll
be
doing
alone.
This
is
something
that
I
want
to
work
with
you,
so
that
we
can
build
something
that
is
easy
to
communicate
and
makes
and
aligns
with
what
we've
discovered
through
research.
Basically.
B
Okay,
yeah,
I
think
that
makes
sense.
I
think
this
is.
I
appreciate
you
highlighting
this
is
an
area
that
I
think
I've
not
done
a
great
job
like
setting
a
direction,
because
I
feel
like
we
shifted.
We
shipped
it
out
of
feature
work
and
into
like
sort
of
maintenance
work,
so
yeah
I'm.
I
think
this
will
be
good
to
like
sort
of
revisit
and
figure
out
what
our,
what
the
next
few
quarters
look
like
for
us.
So.
A
Cool
cool
cool,
I'm
glad
you're
you're
positive
about
it,
and
I-
and
I
don't
want
to
like
I
put
this
here
and
and
you're
right.
Thank
you
for
asking
what
this
means,
because
I
I
didn't.
I
don't
want
it
to
look
like
I'm
like
I'm
overstepping
you
or
anything,
it's
it's
a
it's
a
collaboration
and
and
yeah
after
that.
A
Look
at
the
data
that
we
have
through
the
lens
of
which
features
we
can
remove
because
we're
just
looking
at
data
and
say
hey.
This
is
a
lot
of
usage.
This
has
low
level
usage,
but
I
think
it's
different
when
you
say:
let's
intentionally
look
at
things
that
might
indicate
that
very
few
users
use
this
right
or
if
even
if,
there's
a
better
way
for
them
to
do
something.
A
So
we
will
direct
them
to
another
feature,
perhaps
or
something
like
that,
and
also
gather
and
then
kind
of
rally
the
team
to
come
up
with
ideas
for
things
that
we'd
like
to
instrument
to
know.
If
we
can
remove
them
or
not,
and
maybe
at
the
end
we
of
this
exercise,
we
realize
we
can't
remove
anything
or
we're
just
going
to
remove
this
one
feature.
B
B
A
Options
or
ui
elements,
so
so
one
of
the
things
that
we
removed
was
the
jump
to
next
and
resolved
thread
button
from
each
thread,
and
I
was
really
proud
about
that.
It
was
just
a
little
button,
but
I
was
really
proud
that
we
did
that
and-
and
so
it
doesn't
have
to
be,
like
a
huge
feature
that
no
one
uses
it
might
be
small
things
that
we
can
remove.
A
A
B
A
Fourteen
two
okay,
so
let
me
put
that
14-2,
that's
something
that
I'll
be
just
supporting
and
unblocking
and
the
other
things
are
the
merge,
widgets
or
the
ability
as
well,
so
the
both
the
front
end
and
back
end,
because
I
think
those
will
need
my
my
support
and
then
finally,
we
have
the
merge
requests
that
require
my
attention
and
that
right
now,
there's
that
planning
issue
that
I'm
still
waiting
under
for
andre
and
matt
to
yeah
tell
me
how
they
want
to
approach
this
and
who
will
break
down
the
work
necessary
for
that.
A
But
it
will
probably
require
reviews
and
unblocking
and
hey.
We
can't
do
this,
so
what
are
we
going
to
do
instead
and
the
other
things
that
I'll
be
not
doing,
but
supporting
so
delegating
support
is
mike.
Nichols
is
leading
the
framework
for
source
code
rules
and
I'm
pushing
him
to
include
and
look
and
own
the
work
that
not
not
on
the
work
but
own
the
responsibility
of
overseeing
the
work.
That's
secure
that
container
security
is
doing
with
the
advanced
approval
rules,
because
this
framework
is
looking
at
all
of
the
source
code.
A
Rules,
push
rules,
protected
branches,
approval
rules
etc,
and
so
that's
part
of
that,
and
that's
something
that
I
don't
want
our
group
to
be
burdened
with,
and
it
makes
sense
to
see
all
of
this
together,
and
so
it
makes
sense
to
have
another
person
doing
that.
So
I'm
delegating
that
to
him,
but
supporting
him
throughout
that
process.
B
A
Yeah
yeah
and
I
know
you've
you've
been
involved
in
a
lot
of
the
conversations
as
well,
but
I
yeah
I
don't.
I
don't
want
this
to
the
thing
that
the
container
security
is
doing.
I
don't
want
that
to
divert
our
attention
from
other
things
and
and-
and
yours
is
included-
if
you
don't
mind
me
saying
that,
but.
A
Yeah
then
we
have
the
security
tab
in
mr
I'll
have
to
look
at
that
this
week
again
to
figure
out
next
steps,
and-
and
finally,
we
have
the
framework
for
mr
widgets,
which
is
coming
along
very
very,
very
well.
I'm
very
happy
about
the
polish
that
the
polishing
work
that
jeremy,
tim
and
amy
are
doing
for
visual
design
and
the
ui
text
of
the
mr
widgets,
which
does
not
include
the
approvals
widget
or
the
merge
widget.
A
For
example,
it
only
includes
what
we
call
the
report
widgets,
so
it's
coming
along
very
well,
and
then
we
have
another
step
here,
which
is
the
workflow
interviews
that
catherine
did
but
haven't
finished
the
synthesizing
of
those
interviews,
yeah
and
I'm
still
discussing.
Who
would
be
the
most
appropriate
person
to
continue
that
work,
because
my
what
I
would
like
is
to
have
tim
tim
noah
he's
articulating,
facilitating
the
the
short-term
work
for
the
merge
request,
widgets
that
polishing
that
I
was
just
mentioning.
A
It's
something
that
we're
kind
of
taking
the
responsibility
for,
but
in
the
end,
we're
not
building
them
and
we're
not
like
the
primary
advocates
for
those
reports.
So
I
prefer
to
have
someone
else.
Do
this
work
and
we
will
be
there
to
support
them
in
the
same
way
that
we're
not
building
the
security
tab,
but
it
will
affect
the
merge
request
experience.
So
we
will
support
them
in
that
journey.
A
So
yeah,
I'm
still
discussing
how
that
will
continue
any
questions
at
this
point.
A
Yeah
then,
there
are
a
couple
of
smaller
but
still
important
things
that
I'm
still
undecided
on
whether
it
will
be
me
or
annabelle
working
on
them.
One
of
them
is
doing
another
performance
audit
from
a
user
point
of
view.
A
So
that's
something
that
I'm
planning
for
us
to
do
in
the
next
quarter
and
it
won't
take
the
full
quarter.
It
will
be
done
whenever
we
have
some
capacity
so
that
we
can,
if
possible,
highlight
some
small
things
that
we
could
do
to
improve
the
user's
perception
of
performance
without
having
to
yeah
completely
redesign
the
back
end.
A
Does
that
make
sense
yep
all
right
and
the
other
one
is
improving
the
merge,
widget
ui
text,
which
is
something
I
started
doing
with
amy,
but
I
I
would
like
to
see
with
annabelle
if
this
is
something
that
she
has
some
personal
intentions
on
on
on
working
on
it,
and
if
you
white
text
is
something
that
she
wants
to
improve
her
skills
on
or
whatever.
A
So
I
I
have
to
see
how
that
goes
with
her
and
then
I
have
these
things
for
143,
which
is
the
milestone
that
annabelle
will
start
that,
I
think,
could
be
smaller
things
for
her
to
work
on.
So
one
of
them
is
improved,
commenting
loading
states
and
it's
basically
one
of
the
things
that
came
out
of
that.
A
Of
that
audit,
which
is
to
have
a
consistent
experience
when
we're
submitting
comments
and
how
that
looks
like
the
loading
state
and
right
now,
it's
it
seems
like
we
have
different
loading
sites
or
submission
experiences
for
every
kind
of
comments,
and
so
it
would
be
a
nice
thing
for
us
to
standardize
that
and
it
will
would
improve
the
perception
of
performance,
because
right
now
only
one
type
of
comment,
which
is
when
you're
submitting
irregular
comments.
So
I
don't
think
it
even
includes
the
replying
to
a
thread.
A
It's
the
only
case
where
we
show
kind
of
a
ghost
comment
of
what
it
will
look
like,
so
it
might
be
something
small
for
her
to
work
on
and
also
there
are
a
few
other
issues
that
I
found
to
improve
the
approver
visibility,
and
these
are
these
issues
that
you
see
here
so
basically
explaining.
Why,
for
example,
merge
request,
authors
can't
approve
their
merge
requests
or
people
that
have
committed
to
a
merge
request
cannot
approve
their
merge
requests.
Today,
we
don't
ex
explain
that
and
also
improving
the
visibility.
A
Mixes
links
to
edit
in
the
single
file
editor
or
opening
the
web
id,
and
it
mixes
those
links
with
settings
that
you
change
what
you're
seeing
in
the
diff.
A
What
is
going
to
do
what
and
then
there's
the
other
one
which
is
simplifying
usage
of
colors
and
icons
in
the
file
browser,
because
we
have
like
so
many
different
colors
and
indicators
in
the
file
browser
and
there's
also
that
other
issue
that
I
think
you
commented
on
recently
to
add
vertical
lines
to
the
file
browser
to
help
understand
the
indentation
and
the
folders,
so
that
would
be
all
part
of
it.
A
A
What
I
would
like
to
decide
on
is-
and
that
I
marked
in
bold,
is
the
big
theme,
and
then
I
have
a
couple
of
other
things
that
I
think
would
be
interesting
for
her
to
do
in
q3
and
q4
like
validating
our
jobs,
to
be
done
and
doing
a
ux
scorecard
that
we
haven't
done
in
a
very
long
time
for
code
review
and
finally,
delegation
is
something
that
I
from
what
I
gathered
the
cm
s,
so
the
catch
category,
imagery
scorecard
for
the
editor
extension.
B
Yeah
I'm
fine
taking
it
on
because
it
needs
to
get
done
and
not
that,
like
you,
don't
do
things
for
editor
extension,
but
I
do
feel
it's
sort
of
like
a
a
hobby
project
of
mine
in
the
system.
So
I'm
fine
like
having
to
to
shoulder
some
of
that
additional
responsibility
of
the
hobby
project
so.
A
Like
build
a
business
case
to
invest
more
in
it
as
well.
B
Yeah,
I
think
I
think
one
of
the
things
that
I
want
your
guidance
on
and
we
will
discuss
in
the
issue,
is
sort
of
like
I
know
for
like
the
thing.
We
only
have
to
do
one
job
to
be
done,
and
I
could
it
was
very
easy
to
game
the
category
maturity
scorecard
process
as
someone
who
has
gamed
it
previously
like.
B
I
know
this
so
and
we
just
may
need
to
be
cautious
about
how
we
do
it
and
and
test
in
this
instance,
where
we've
never
really
validated
sort
of
anything
in
the
extension
yeah.
But
we'll
have
to
discuss
that
more.
A
Cool
yeah
we're
we're
at
time.
I
don't
know
if
you
have
a
few
more
minutes
or
you
have
to
jump
to
another
call.
B
Yeah,
I
can
do
like
five
more.
I
think
the
only
thing
I
know
you
build,
this
twice
is
like
the
big
theme.
I
think
my
only
question
is
going
to
be.
B
Do
we
need
do
we
need
to
do
feature
work
for
like
the
next
year,
which
would
be
sort
of
like
in
a
big
theme
or.
B
B
B
You
might
do
given
like
all
of
the
opportunity
we
have
to
sort
of
just
make
that
experience
better,
and
so
I've
been
like
it
was
sort
of
nice
to
like
do
the
large
mr
work
and
like
see
the
team
rally
behind
that
I'm
sort
of
excited
to
get
into
the
mergeability
and
like
the
merge,
widget
work,
because
I
feel,
like
those
things,
are
just
sort
of
like
the
long
overdue
refactoring
and
efforts
that
we
need,
and
so
I'm
I'm
conflicted
about
more
feature,
work
sort
of
in
general
as
it
stands
and
so,
like
I
don't
know
like
q3,
based
on
the
way
things
are
like
we're,
focused
on
merge
ability
and
the
merge
widget
right.
B
B
B
As
much
as
you
have
and
so
like
I
just
I
haven't
gotten
there
yet!
That's
that's!
That's!
That's!
Okay!
Thanks
for
the.
A
Transparency
yeah
so.
A
Yeah,
what
I
would
like
to
do
with
the
big
themes
is
more
or
less
what
you
saw
with
the
request
attention.
Although
the
request
attention
was
something
that
was
very
narrow
or
or
narrower
than
what
I
I
was
I
would
like,
but
it
yeah.
It
was
just
all
of
that
exploration
and
all
of
that
validation
to
come
to
something
that
we
can
now
break
down
into
whatever
steps
we
want
and
implement
things
iteratively
and
also
decide
on
what
is
the
ideal
iteration
path
based
on
what
we
want
to
learn?
A
A
So
let
me
I'll
so
we
can
postpone
this
conversation
about
deciding
hey.
What
is
the
big
theme
that
peter
is
going
to
be
working
on
in
q3
or
or
annabelle
or
yeah
for
for
the
next
months?
We
can
postpone
that
because
I
completely
understand
that
neither
you
and
I
probably
have
the
time
or
the
mindset
right
now
to
decide
that,
but
but
coming
back
to
your
point
about
usability
and
future
work,
I
added
this
column
right
now
about
type
of
work
and
I'm
adding.
A
What
I
think
is
the
kind
of
work
that
or
the
majority
of
the
work
that
we
would
be
doing
what
it
would
be
and,
for
example,
extending
code
intelligence
or
not
allowing
you
to
navigate
the
whole
repo
inside
of
a
merge
request
or
commenting
on
other
files.
That
would
be
feature
edition
or
mr
exclusions.
That
would
be
a
future
edition.
A
But
then
all
of
this
is
just
usability
and
it's
the
foundation
to
improve
the
merge
requests
ui
as
a
whole,
navigating
commits
navigating
files
navigating
threads,
and
it's
basically
the
work
that
I
feel
we
need
to
do
to
continue
the
work
that
sanjong
started,
because
she
was
hitting
a
lot
of
walls
with
that
work
of
the
sticky
header
because
yeah
she
said.
A
Okay,
we
will
add
these
buttons,
but
then
we
still
have
those
other
buttons
and
that
other
bar
and
that
other
bar
and
it's
just
a
mess,
and
it
looks
like
we
have
too
many
buttons
for
different
things,
and
it's
just
leads
to
a
more
cluttered
ui.
So
this
would
be
mostly
usability,
and
then
we
have
these
ones,
which
are
just
templates,
options,
configurations
and
settings
which
would
be
feature
editions,
finding
appropriate
reviewers
featured
edition.
A
A
A
Feature
edition
commit
by
commit
co-review
and
cross
project,
mrs
and
then
this
one,
which
is
to
add
value
to
our
batch
comments,
feature
with
other
options
and
things
that
people
could
do
feature
edition
and
then
finally
reducing
confusion
on
comments
and
threads
and
yeah.
There
are
many
small
but
important
issues
here.
That
would
be
just
usability.
B
I
think
that,
in
your
framing
of
like
saying
more
about
like
the
research
and
design
work
and
less
about
the
delivering
of
that
work
helps
too.
I
think
that
takes
some
of
maybe
the
pressure
off
that
I
was
feeling
about
how
we
were
thinking
about
this
so
yeah
I
I
agree.
We
need
to
figure
out
where
to
invest
with
that
lens.
It
makes
more
sense
to
think
about
this.
Where
do
we
invest
your
time
and
my
time
and
thinking,
and
not
necessarily
like
engineering
time
and
doing,
and
so
that's,
oh
yeah
yeah.
B
That
piece
than
the
the
like
the
doing
piece
because
I
was
like
I
was
trying
to
figure
out:
how
do
we
balance
these
in,
like
the
doing
of
the
other
things
we're
doing
but
you're
right?
These
are
good
times
to
do
these
things,
because
I
don't
know
if
you
felt
this
way.
I
felt
during
q2
that,
like
I
didn't,
have
not
a
lot
like
because
they
were
focused
on
performance.
It
did
free
me
up
to
sort
of
like
do
other
things
and
go
spend
more
time.
B
Looking
at
what
other
groups
and
stages
were
doing-
and
I
imagine
q3
will
be
a
little
bit
less
like
that,
because
you'll
have
to
be
more
involved
and
think
I'm
very
terrified
about
the
merge
button
and
all
the
work
we're
going
to
do
there
so
lots
of
review
time,
but
like
yeah,
we
might
have
more
of
that
time
just
to
like
yeah
trying
to
get
ahead
of
milestone,
which
is
something
we've
talked
about
before
I've
never
been
able
to
do
so.
B
I
think
trying
to
get
ahead
of
quarters
is
a
good,
a
good
path
to
that,
so
that
that
that's
helpful
to
me.
So
I
appreciate
you
you're
reframing
now.
A
Yeah,
that's
that's
yeah,
thanks
for
for
also
summarizing
my
attention,
because
that's
that's
exactly
it.
It's
just
staying
ahead
and
breaking
up
down
these
problems
and
validating
them
and
the
solutions.
A
So
that
engineering
has
prediction
and
we
all
have
predictability
of
what
we
will
be
working
on
and
what
problems
we
will
be
solving
and
so
that
people
can
be
in
a
problem
space
for
like
a
quarter
like
three
milestones,
for
example
like
working
on
a
specific
feature,
while
shipping
iterative
things
each
month,
but
always
in
the
same
problem
space,
because
that's
what
I
feel
we've
been
lacking
is
focusing
on
one
thing:
for
a
certain
time
period,
we've
always.
A
Epics
yeah
yeah.
A
Yeah
that
yeah,
that's,
if
you
want
to
look
it
that
way,
it
would
be
closing
epics,
yeah
and
so
yeah.
Take
your
time
to
to
look
at
this.
I
I
have
I
have
my
favorites.
If,
if
you
want
I
can,
I
can
mark
them
of
what
I
think
we
should
do,
but
at
this
time
I'm
not
going
to
put
any
biases
on
you
so
I'll.
Let
you
look
into
that
and
and
and
we
can
discuss
it
later-
okay,
awesome.
B
This
picture
this
makes
sense
in
terms
of,
I
think,
what
the
next
at
least
quarter
looks
like
and
sort
of
how
you're
you're
allocating
your
time.
I'm
excited
that
annabelle
will
be
on
board
as
well
to
help
as
we
enter
14
3,
so
that'll
be.
That
would
be
awesome
too.
So.
A
Yeah
yeah,
my
idea,
is
to
have
both
of
us
since
we're
you
now
are
going
to
have
two
designers
is
to
have
each
one
of
us
working
on
a
separate
theme,
which
should
probably
give
enough
work
for
then
engineering
to
to
work
on
after
that
yep
cool,
okay,
awesome
thanks.
I.