►
From YouTube: 2019-10-17 Weekly Knowledge Sync
Description
Weekly Knowledge Team Meeting
A
B
A
B
C
C
I've
been
going
through
a
lot
of
the
issues
and
coming
up
with
some
vision,
ideas
and
like
might
be
a
slightly
different
direction
than
what's
going,
but
that's
kind
of
my
high
level
and
then
I'm
just
curious
to
hear
where
you
guys
are
at
with
this
12
for
release
and
moving
into
12
five,
because
I'm
kind
of
in
the
dark
on
12
4
I'm
like
watching,
but
it's
still
on
kind
of
all
in
Chi.
For
that.
So.
B
B
B
A
D
B
D
B
B
D
B
A
B
D
B
B
Alright,
well
Kristen
still
isn't
here,
but
I
was
I
was
just
asking
you
about
your
knowledge
intern.
So
we
have
young
early,
AB
and
Alex
was
saying
that
he's
gonna
just
give
her
small
tasks
for
this
release.
Very
small
test
like
make
this
change
very
small
changes
just
so
she
can
kind
of
get
the
hang
of
graph
QL
and
then
maybe
and
twelve
six
give
her
an
actual
assignment
related
to
maybe
something
in
her
group
and
I
was
just
curious,
Andre
what
you
are
doing
for
your
intern.
D
B
B
C
B
Town
I'm
not
sure
how
much
you
caught
before
you
were
disconnected,
but
I
was
saying
that
there's
a
I
added
a
link
to
the
document
and
to
the
chat.
This
is
an
issue
that
I
use
to
kind
of
track.
The
sprint
planning
and
I
updated
that
issue
with
the
current
status
and
I
was
saying
that
we're
slipping
a
little
bit.
C
B
B
C
D
So
I
know
that
the
development
is
happens
and
now
the
bigger
the
bigger
we
have
right
now
is
we're
trying
to
reuse
component
that
is
used
on
merge
requests,
which
is
not
exactly
what
we
have
in
design
management.
So
we
are
trying
to
grab
the
design
management
components
and
move
them
to
the
discussion,
which
is
tricky
because
it
doesn't
use
graph
QL
so
you're
having
to
just
make
rewrite
a
bit
a
bunch
of
things.
So
that's
like
a
little
longer,
but
that's
already
set
for
the
development
and
it
kind
of
follows
a
set
pattern.
D
C
Yeah
and
I
did
see
it
and
I
was
looking
through
it,
and
I
was
going
through
some
use
cases
in
my
own
head
around
how
that
would
actually
play
out
in
design
projects.
I
do
think
that
merge
requests
view
is
really
interesting,
but
I'm
just
wondering
if
we
thought
through
projects
where
you
might
have
like
50
design
comments
in
the
feed
and
then
the
fact
that
they
go
stale
so
like
essentially
as
soon
as
the
next
versions
up
you're
gonna
have
all
these
huge
images
like
that
are
stale
and
I
know.
C
C
Some
real-world
kind
of
situations
and
just
make
sure
because
the
stale,
screenshots
and
I
know
Jarek.
You
had
mentioned
that
in
a
comment
too
you're
saying
that
they
go
stale
and
we're
suggesting
a
more
like
simple
implementation
initially
and
the
issue
I
actually
agree
a
lot
with
what
you
were
saying,
like
your
first
hunch
on
it
and
just
from
using
and
vision
and
other
tools
like
none
of
them
take
the
actual
change
or
the
image
and
put
that
in
the
feed.
A
So
we
can
definitely
pick
up
on
this
later.
I
would
say
this
was
sort
of
a
quick
and
dirty.
You
know
it
was
like
we're
gonna
ship
it
in
this
milestone,
we're
just
going
based
on
a
an
assumption
of
the
best
scenario
in
this
case
and
what
to
do
for
an
MVC,
so
I
think
it's
useful
and
I
think
the
initial
proposal,
but
yeah.
We
need
to
definitely
think
out
some
more
scenarios
like
you're
talking
about,
and
we
can
certainly
continue
to
iterate
on
it.
Yeah.
D
I'll
just
add
sorry,
there's
no
ahead
and
go
ahead.
Oleg
I
was
going
to
mention
the
case
that
we
have
on
the
merge
request
that
might
be
used
for
consistency,
this
this
kind
of
intersected
with
resolve
the
ability
of
disruption
but
requests
when
we
have
an
outdated
discussion,
they
just
like
show
up
as
a
very
fine
like
security
when
one
line
of
text,
and
then
you
can
expand
it
to
something
like
that,
could
be
useful
for
this
scenario:
religious,
like
Faden,
compact
them
into
just
one
line.
D
They
there
was
a
common
on
an
outdated
design,
markup
or
something
yeah.
Definitely
out
I
see
that
there
would
be
a
interesting
iteration
on
what
we
have
right
now,
but
for
now
there's
so
much
technical
challenges
that
we
would
definitely
welcome
to
get
an
invis
out
as
soon
as
possible
and
then
iterate
on
it
its
place
quickly
as
well,
so
yeah,
but
in
some
sense
what
you're
saying
I
totally.
D
C
C
The
kickoff
video
they've
decided
that
the
PM's
need
to
do
a
video,
even
if
you
don't
have
new
features,
even
if
your
you
have
slipped
features
that
were
talked
about
from
a
previous
release
and
so
I'll
do
up
like
a
tent
like
a
one-minute
video,
mostly
just
talking
about
moving
the
design
discussion
out
into
the
the
main
feed
and
that'll.
Be
the
one
thing
that
we're
highlighting
that
goes
up
just
said
for
this
next
release
and.
A
Just
to
clarify
we're
not
andre
we're
not
doing
the
discussion
around
the
system.
Note
remember
when
we
brought
up
they,
those
thumbnails,
those
mock-ups
that
you
posted
with
the
thumbnails
and
then
there
was
discussion
around
the
actual
system.
Note
of
somebody
update
uploaded
five
designs
and
there
was
conversation,
or
did
we
mixed
that
right?
We
were
not
doing
that
right.
D
That's
interesting
question
because
last
time
I
chatted,
so
there
there
are
two
issues
right
away
being
like
in
flight.
One
is
the
system
notes
and
one
is
the
activity
trying
to
recover.
So
one
is
activity
in
design
to
create
system
notes,
and
the
other
is
design.
Notes
should
also
be
available
in
the
discussions.
Tab,
so
they're
two
separate
issues
on
the
design
not
being
in
the
discussions.
Tab
I
was
under
the
impression
that
it
would
be
showing
the
in-place
comments.
Yes,.
A
This,
for
this
is
for
the
pin
comment
thread
so,
like
you
pin
a
comment
and
then
yeah
it
goes
in
here,
but
in
the
mock-ups
in
the
issue
there
was
an
original
mock-up
with
what
is
now.
What
we're
saying
is
system
notes,
which
is
what
Alex
chipped,
Cowen's
no
uploaded
three
designs
and
in
the
mock-up
for.
A
C
A
C
A
A
B
A
D
Yeah
so
I
think
that
the
movie
ended
up
going,
which
is
just
basically
grabbing
the
componentry
tabs
for
comments
on
images
and
applying
that
components
that
we
have
in
design
management,
which
is
simple
like
showing
the
comment
there.
But
I
would
have
to
check
the
Miss
Holly
on
the
actual
version
that
she
went.
Oh
god.
D
Not
what
we're
having
on
this
first
screen,
shot
like
that
was
just
like
something
that
came
from
the
product
discovery
and
we're
not
using
that
for
sure
100%,
but
I'm,
not
I.
Don't
have
anything
in
front
of
me
right
now
with
the
actual
version
that
we're
going
with,
but
the
goal
is
to
reuse
the
design
management,
so
that
next
time,
when
we
add,
for
example,
all
pins
that
also
reflects
on
that
component
as
well.
So
the
IDS
have
consistency
between
those
two
things.
C
They'll
be
a
lot
on
design
specific
issues,
but
I'm
just
I'm
still
like
getting
up
to
speed
with
the
team,
but
I
would
like
moving
forward
if
we
can
for
wrapping
UX
like
a
month
or
an
iteration
ahead
that
we
really
are
clearly
saying
these
are
the
user
stories.
The
UX
person
wants
to
quickly
see
that
there's
six
things
and
then
go
address
them
and
have
them
clear
and
go
away
and
like
really
get
specific
on,
why
we've
chosen
these
definitely
specific
solutions.
The
validation
part
of
the
solution.
D
Yeah
totally
on
that,
the
only
thing
I
would
add
is
that
sometimes
it's
not
possible
to
do
that.
Eggar
design
in
one
iteration
and
development
in
our
nutrition
like
that,
doesn't
stop
us
from
yet
that
doesn't
stop
us
from
addressing
the
user
stories
until
tonight.
I'm
100%
on
that.
So
that
makes
perfect
sense.
A
Goal
is
always
to
try
and
do
UX
one
milestone
ahead
and
I
know
kind
of
talk
about
this,
because
we
were
running
into
my
confusion
of
oh.
This
is
action.
The
build
milestone,
so
I
would
quickly
put
something
together
in
the
first
week
and
then
everyone's
like
alright
is
Jarek.
Is
this
ready
to
go
what's
up
yeah.
C
C
C
Jarek
like
surfacing
your
process
as
well
as
tying
that
to
story
so
when
I
go
and
do
shoot
like
I
have
to
do
a
video
today
and
talk
about
it
for
a
minute
about
why
these
choices
were
made
and
I
just
really
want
to
tie
them
back
to
behavior
and
yeah
goals
of
the
user
versus
just
it
looked
cool
and
merged
requests,
and
so
we
duplicated
it
over
here,
but
so
yeah.
It's
kind
of
that.
The
end
game
and
well
it'll,
probably
take
us
a
few
rounds
to
get
it.
C
C
A
D
So
I
can
add
some
insight
there.
It
kind
of
depends.
Usually
what
we
do
is
like
really
scheduling
an
issue
that
has
both
back
and
front
end
after
the
weighing
and
after
the
planning
usually
break
those
off
into
separate
issues.
The
ENFP
and
keep
the
one
main
one
canonical
for
like
product
like
the
main
suture.
C
D
D
Issues
will
be
moved
like
if
the
movie
is
still
open
when
the
milestone
expires
in
22nd,
there's
a
bot
that
moves
them
to
the
next
milestone,
that's
one,
but
it's
up
to
us
to
decide
what
to
do
with
the
wax
issue
that
was
worked
on
but
hasn't
been
implemented.
We
can
close
that
and
decide
and
take
it
as
a
product
discovery
or
something
completed,
and
then
we
create
further
issues
for
the
development
or
we
can
keep
that
issue
open
and
just
track
it
on
the
next
milestone.
C
D
D
C
C
C
C
C
So
that's
like
just
kind
of
it's
like
a
piece
of
functionality.
I,
don't
think
anyone's
really
doing
yet
a
design
hand
off
where
you're
actually
like
looking
at
with
the
front-end
built
and
comparing
it
directly
to
the
design
and
so
I
think
it's
kind
of
exciting,
because
that
could
be
a
huge
niche
that
hand
off
when
you
give
something
to
the
developers
and
then
they
implement
it.
It's
not
what
you
envisioned.
This
would
actually
allow
you
to
do
like
side
by
side
and
none
of.
D
C
Because
they
don't
have
the
developer
base
that
we
do
envision,
they
can
go
as
far
as
like
a
design
system,
local
on
your
Mac,
but
they
don't
have
the
code
base
to
do
that
hand
off
so
I
think
I'm
going
to
investigate
that
more
and
hopefully
get
some
research
tickets
open
around
it.
But
I
think
that
could
be
huge
in
terms
of
differentiating
our
design
review
stock
from
our
competitors.
C
Video
yeah
for
that
one
I'll
post,
that
into
the
group
but
yeah,
it's
it's
so
hard
to
even
find
it
they're
literally
an
NBC
they've
done
one
release
of
work
on
it.
It's
so
basic
and
it's
a
line
of
JavaScript
embed.
You
have
to
pull
it
into
your
project
for
it
to
work
for
their
MVC,
but
eventually
that
would
be
a
setting.
C
You
could
just
turn
on
and
get,
and
that
would
allow
you
to
do
the
overlays
on
front-end
reviews,
but
I
was
telling
them
I
want
you
to
be
able
to
visually,
draw
pegs
on
it
or
attach
a
comment
to
a
Dom
element,
essentially
so
that
it
could
be
very
like
if
you
have
it
in
mobile
view
versus
like
the
design.
You
could
get
very
specific,
like
this
button
is
wrong.
Yeah.
A
C
D
C
D
Just
it's
a
dumb
bear
way
but
say
that
Jarek
is
reviewing
so
many
more
if
you
just
like
click
the
button
on
the
tool
on
the
comment
box,
and
they
would
show
the
hut
the
overlay
of
all
designs
and
that
each
to
you
just
like
that
yeah.
It's
super
straight
for
including
implementation.
As
long
as
we
have
the
associations
in
the
issue
and
emergency
bus
and
pulling
the
designs
yeah.
D
C
Think
that
kind
of,
like
referencing
the
designs
throughout
this
whole
process
of
going
live,
is
gonna,
be
so
good
for
our
users
and
to
integrate
UX
through
the
whole
process
to
check
go
like
Jarek.
You
come
up
with
these
designs
now
go
check
as
they
get
implemented,
so
just
I
find
it
really
exciting.
So
I
want.