►
From YouTube: 2019 09 30 Memory Team Meeting
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
yeah,
just
going
straight
down
so
Mitya
starts
tomorrow.
I'm
actually
gonna
have
a
meeting
with
him
later
on.
Today
he
had
some
questions
about
getting
started,
got
the
onboarding
issue
already
created
and
everything
so
ok
I'm
going
tomorrow,
once
I
actually
have
a
get
lab,
handle,
there's
a
few
issues
we
can
assign
to
him
or
pink
him.
A
Have
him
pairing
up
with
Alexei
Alexei
is
gonna,
be
his
onboarding
buddy
I
already
talked
about
in
the
memory
team
Channel
about
our
okay,
ours,
we're
doing
well
for
the
quarter
by
the
mid
October,
we
will
hit
our
big
seed
in
our
goal
for
hiring.
We
have
a
couple
more
candidates
in
the
pipeline,
two
of
them
right
now,
I'm
trying
to
finish
up
scheduling,
one
of
them
with
Camille.
So
Camille
you'll
probably
see
someone
your
calendar
here
shortly
or
one
candidate
that
we
have.
A
So
we
need
to
get
a
timeline
on
getting
Puma
out
to
production
because
we
talked
about
trying
to
get
it
out.
The
last
couple
milestones
and
this
milestone
ends
in
just
over
two
weeks.
Are
we
blocked
on
anything
for
getting
Puma
out
to
canary
at
this
point
in
time?
First,
it
was
chronic.
Then
it
was
the
DB
pool
connections
but
I
think
all
of
those
chronic
durations
been
fixed.
The
DB
pool
connections
been
fixed.
Is
there
anything
else
we
need
to
do
to
get
it
out
to
canary.
B
A
B
A
To
take
that
on,
we
just
need
to
figure
out
when
we
can
get
it
on
the
canary
I,
don't
know
of
any
other
blockers
right
now
other
than
like.
You
said,
the
one
last
check
to
see
if
there's
anything
else,
and
is
that
same
thing.
We've
done
in
the
past,
just
ping
jarv
and
ask
him
to
roll
it
out
and
give
him
guidance
on
workers
and
threads
for
canary
I'm.
B
A
B
B
A
B
B
B
My
decision
I'm
closing
effectively.
This
is
my
served
by
this
much
because
I'm
effectively
closing
this
issue,
which
is
like
the
Prairie
twist
and
the
first
step
out
of
this
optimized
pipeline
service,
its
effects
for
in
the
comment
at
the
bottom,
because
there
is
like
elaborated
implementation,
but
the
respective
map.
The
comment
of
nine
about
the
steps
to
implement.
If
you
could
scroll
up,
pedal,
pedal,
pedal.
B
A
A
B
B
A
B
So
so
like
from
my
perspective,
if
I
would
not
have
any
interruptions
and
other
interruptions,
I
would
still
be
able
to
solve
this.
Like
big
issue,
I
just
don't
know
if
I
will
not
have
any
other
interruptions
because,
like
technically
I
have
neuron,
then
around
age
working
days
or
nine
work
in
density
like
the
feature
freeze
the
cam,
it's
quite
risky
for
me
at
this
point,
it's
like
50/50,
I,
guess,
okay,.
A
Okay,
so
this
next
one's
Alexie's,
deduplicating
and
refactoring
the
existing
project
code,
you
made
a
comment
about
focusing
on
project
tree,
restore
first
and
mentioned
that
it
is
actually
a
part
of
the
initial
code
listed
or
I'm.
Sorry,
the
initial
issue
listed
there's
not
a
lot
of
detail
in
there
other
than
he
just
needs
to
focus
on
that
piece
of
it.
So
it's
called
out
as
a
go-ahead
Camille.
Yes,.
B
B
Okay,
so
like
it's,
it
really
depends
how
I
mean
I
met
because
like
in
order
to
make
that
application,
we
have
to
fix
the
tree,
restore
because
it's
gonna
be
broken,
so
maybe
it's
better
to
improve
3-story
to
be
like
less
complex,
because
it's
not
super
complex,
not
have
to
fix
the
box,
because
the
architecture
gonna
be
better
of
that.
So
I,
don't
know
what
is
the
best
approach,
but
I
know
that
project
restoring
that
current
form.
We
not
accepted
the
dead
application
at
fault,
litigating.
A
A
A
All
the
intensive
endpoint
issues
clear
we're
not
gonna
get
to
him
in
12,
for
so
I
moved
them
out
to
12
five
and
mark
them
with
the
low-hanging
fruit
icon,
so
that
will
probably
assign
the
merge
request
one
to
one
of
the
newer
folks
on
the
team
as
they
get
up
to
speed.
That's
the
one
that's
hitting
us
the
hardest
at
the
most
seemed
like
a
good
one
on
board
with
and
then
when
I
was
reviewing
the
backlog.
This
issue
came
up.
A
B
A
B
Right
regardless,
if
this
is
like
I,
don't
know,
Puma
or
and
I
think
answer
this
movie
credit
and
how
many
hey
sauce
unicorn
is
very
bots.
Put
that
button,
because
unicorn
I
design
is
like
a
single
treads
and
by
design
it
can
be
killed
for
equity.
So
maybe
right
for
the
web.
Sockets
application,
like
we
may
be
spun
up
like
a
separate
service,
is
gonna,
be
running
concurrently.