►
From YouTube: 2019 11 06 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
Cool
first
thing
up:
is
you
have
a
ideation
theory?
There's
lots
to
be
fun,
I
mean
I,
think
you've
paid
attention
to
the
EMR
that
there's
been
no
consensus,
no
progress.
Actually,
since
the
last
round
of
revisions
that
I
made
there
was,
there
hasn't
been
any
feedback
either.
So
Eric
and
I
have
talked
about
this
a
bit
and.
A
What
we're
thinking
over
the
next
year
is
that
we
look
at
what
we
have
talked
about
to
you,
like
quality
of
life
performance
improvements,
those
types
of
things
that
we
knew
we
wanted
to
do
anyways
but
weren't
sure
where
they
fit
in
with
kind
of
the
other
strategy
that
we
were
thinking
about
anyway.
So
now
this
puts
the
pressure
on
the
goal.
A
Fine,
if
these
things
a
little
bit
sooner
so
I
think
there's
two
things
is
one:
we
kind
of
need
to
start
thinking
about
those
things
and
go
finding
issues
and
I
know
you've
linked
to
one
that
you
think
would
be
good
in
twelve.
Six
I
actually
have
no
idea
what
capacity
for
twelve
six
looks
like
with,
like
the
bleed
over
of
search
and
other
stuff,
but
I
agree.
The
other
thing
is:
is
I'm
gonna
have
to
rewrite
the
strategy
again
to
capture
what
we
think
the
next
twelve
months
of
work
looks
like,
which
is
fine.
A
A
My
ask
is
like
what
are
your
thoughts
on
rationalizing
this
in
a
go-forward
way?
We're
like
this
is
the
wippid.
Also,
I
guess
the
the
additional
context
would
be
that
there
is
going
to
be.
There
is
a
static
site,
editor
group,
so
maybe
we
don't
have
to
talk
about
that
persona
news
case.
Maybe
we
leave
like
the
same
stuff
in
there
that
we
had
before
about
like
we're,
not
solving
for
them,
but
I,
don't
know
what
your
thoughts
are
on
this,
because.
B
B
A
A
Would
they
use
the
single
file
like
Monaco,
component
and
I?
Think
my
answer
is
probably
no
right,
because
if
the
single
file
Monaco
components
written
around
like
editing
and
markdown
and
their
experience
isn't
editing
and
markdown
they're-
probably
unlikely
to
use
it
yeah.
So
I,
don't
I,
don't
think.
There's
a
lot
of
overlap
in,
like
the
tech
pieces
of
this
I,
also
think
they're
trying
to
solve
a
different
problem
than
we
want
to
solve.
The
only.
A
Yeah
I,
don't
think,
there's
a
lot
of
overlap.
I
also
think
because
they're
focused
on
handbook
first,
like
we
probably
don't,
have
to
be
as
concerned
with
that
persona
like
dealing
with
the
internal
pressures
that
we
have
been
dealing
with
it
like
making
that
better.
So
I'm
I'm
comfortable,
still
saying
like
we're
not
focused
on
those
users,
but
that
we're
also
not
really
like
focused
on
solving.
We
focus
on,
like
20%
of
our
technical
users,
use
cases
and
not
even
like
solving
more
of
those
either.
A
I,
don't
I
think
it
depends
so
like
I
think.
The
first
thing
they
want
to
do
out
of
the
gate
is:
do
like
a
technical
sprint
to
see
so,
like
engineers
already
exists,
my
understanding,
because
they're
coming
out
of
growth
for
like
full-stack
engineers,
so
they're,
not
even
like
Effie,
Becky,
front-end
and
back-end
engineers,
they're
full
stack
from
from
growth
and
I.
A
Think,
like
the
thought,
the
initial
thought
is
like
upgrading
the
version
of
middleman
so
like
that's,
which
is
like
low
user
impact
that
allows
us
to
like
do
some
other
features
and
I
think
the
other
thing
they
want
to
do
is
like.
Could
they
layer
in
I
think
the
other
thing
they
want
to?
Try
really
fast
is:
could
they
use
net
with
ICMS,
because
if
they
could
use
that,
then
they're
basically
like
solved
for
the
handler.
B
A
B
A
We
have
so
that
there
they're
operating
under
two
different
categories,
so
they're
operating
under
one
thing
that
will
get
built.
That
may
or
may
not
be
a
part
of
the
gait
lab
application
that
is
purely
focused
on
the
handbook
and
then
longer
term.
They
will
focus
on
static
site
editing
for
not
the
handbook
as
two.
A
I
am
yeah,
I
mean
that
was
Matthew
I.
Think
I
am
inclined
to
say
that
we
I,
like
the
target
persona
pieces
of
the
new
strategy
that
did
that
isn't
gonna
get
merged
I
like
that
more
in
terms
of
thinking
about
it
from
technical
use
cases,
I
think
that
helps
simplify
the
scope
and
helps
us
focus
on
things.
A
A
Ide
UI
and
you
don't
have
to
go
anywhere
else
like
maybe
that's
a
thing
that
we
go
solve,
that
we
weren't
planning
on
solving
originally
because
we
were
looking
at
like
runtime
environments
and
other
things.
But
maybe
we
just
use
the
web
ideas
like
this
tool
to
enable
these
other
things
versus
thinking.
People
will
do
engineering,
work
on
them
and
all.
C
A
Added
it
only
because
you
were
here
is
like
oh,
he
wants
patches,
we
should
just
but
like
that
I
mean
I,
think
like
if
we
think
about
the
web
ID.
In
that
sense,
it
makes
sense
to
think
about
those
kinds
of
things
that
are
different
than
the
kinds
of
things
that
we
were
gonna
go
do,
but
that
I
think
are
achievable
in
our
existing
text.
Back
to
the
web,
ID
yeah.
C
A
I
also
think
it's
like
there
was
at
least
my
perspective
was
is
there's
like
noticeable
excitement
in
the
engineering
team
like
when
we
would
talk
about
it
like
the
things
we
could
go,
do
with
it
and
like
I'm,
worried
that,
like
resetting
expectations
now
and
like
getting
people
excited
about
the
stuff
we
want
to
go,
do
is
like
harder,
I
get
like
I'm
back
it
like
this,
like
like,
there's
like
well,
you
say
patches.
A
C
A
B
And
I
think
I
can
actually
see
some
design
ideas
how
to
keep
the
flow
very
but
also
branch
off
in
a
couple
of
more
complex
cases
like
Thatcher's
like
other
stuff
but
I.
Think
really.
If
we
can
put
this
issue
where
we
talked
about
like
staging
and
making
that
flow
easier,
that
would
already
be
a
great
first
step,
making
the
flow
like
easy
to
understand
and
could
give
us
a
big
boost
for
non-technical
users,
and
then
we
can
see
where
we
can
progress,
making
the
happy
path.
B
B
Yes,
I,
don't
think
we
came
to
a
solution
here,
because
I'm
still
I
posted
the
video
and
I,
don't
know
whether
you
saw
it,
but
it
seems
to
me
like.
We
now
have
two
bucks.
First
of
all
that
the
button
is
not
on
the
project
page,
yes,
but
if
I
go
into
the
web
IDE
from
the
file
page.
In
this
case
it
will
bring
up
multi
levels
and
again
we
have
to
solve
both
bugs
and
I'm,
not
sure
if
we
have
to
solve
them,
both
at
the
same
time
or
one
before
the
other
one
I.
A
B
C
A
A
So
then,
once
you,
but
if
you
had
a
file
view
you
can
get
into
the
web
IDE
and
when
you
get
into
the
web
ID
it
tries
to
load
the
merge
request:
tab
cuz,
it's
like!
Oh,
let
me
go
see
what
merge
request
exists
or
let
me
see
like
all
the
stuff,
that's
related
to
merge
request,
but
because
merge
request,
don't
aren't
turned
on
for
the
project.
None
of
that
exists
so,
like
there's,
no
error.
Checking.
There's.
B
B
A
C
A
So
I
think
we
get
the
web
ie
button
back
and
then
we
kind
of
address
these
other
ones.
It's
like
individual,
like
I,
would
address
each
of
them
as
like
individually
issues
and
maybe
like
we
just
relate
them
all
I'm
like
if
someone
fixes
them
on
one
patch,
then
that's
fine
or
one
like
merge
across
that's
fine
but
like
I,
might
think
they're
like
sort
of
two
or
three
separate
problems
like
the
merge
request.
Tab,
not
loading
if
merge
requests
are
disabled
is
like
different
than
the
merge
request.
A
Not
working
is
in
my
mind
that
get
the
merge
request,
checkbox
doesn't
work
then
like
maybe
we
should
offer
a
for
crop.
Maybe
there's
like
a
different
thing
that
we
do
there.
That
says,
like.
Maybe
you
need
to
fork
this
to
your
own
project
or
I,
don't
know,
what's
probably
not
correct,
that,
like
I
feel
like,
we
should
think
about
some
of
these
pieces
a
little
bit
yeah.
C
C
Yes,
so
have
an
awesome
community
contribution
adding.
So
let
me
let
me
open
this
for
some
context
where's.
So
this
adds
in
your
dot
get
lab
project
directory.
I
could
specify
a
completely
custom
template
file.
So
right
now
it's
kind
of
pasta.
You
only
will
we
pretty
have
we
have
mostly
hard-coded
like
there's
four
types
of
templates.
Docker
file
get
ignore
good
lab
CI
emmalin
like
license
for
something,
but
this
one
is
saying
hey
now
we
can
have
you
know
I
just
want
to
create
template
of
files
for
any.
C
Well,
we
have
two
editors.
We
have
the
ACE
editor
which
adding
this
extra
drop-down
was.
You
know
not
fairly
trivial,
because
if
I'm
creating
a
new
file,
I
can
rename
the
file
right
here,
and
so
you
see
these
two
drop
downs.
His
first
drop
downs
like
what
is
the
type
of
template
you're
doing
and
the
second
one
is
like.
What's
the
file
look
like
so
for
this
new
Lamar?
What
it
does
is,
one
of
the
types
is
gonna,
be
custom
or
something
like
that.
C
We're
still
ux2
sites,
and
this
one
would
be
like
a
list
of
all
those
custom
files
that
they
found
on
the
project
here.
So
it's
possible.
This
whole
workflow
works
nicely,
and
you
know
you
can
imagine
like
hey.
I
want
to
start
a
blog
post
and
I
could
do
that
from
here.
It
does
not
any
part
of
the
web.
Id
does
not
support
this
word
slow
it'll,
because
the
web
ID
templating
is
pretty
coupled
to
no
that's,
not
the
right
one
or
was
I
here.
I
am
the
web.
Id
is
pretty
couple.
C
These
are
the
four
things
you
can
select
and
the
name
of
the
file
is
tied
to
this
drop-down
here
so
and
there's
not
really
any
way
for
me
to
rename
a
file
from
this
from
the
web.
Ide
editor.
So
some
suggestions
that
came
up
on,
let
me
these
are
some.
These
are
some
mantasy
suggestions,
so
just
in
the
spirit
of
brainstorming
like
here
when
we're
creating
a
new
file,
we
have
you
know
different
templates.
C
You
hit
this
custom
template
here,
but
it's
not
ideal
because
that's
not
really
supposed
to
be
the
file
name.
The
other
idea
would
be
when
I
when
I
want
to
talk
to
myself.
Well,
it's
not
really
quite
right,
because
all
these
other
the
file
names
like
we
could
just
keep
adding
to
this
list.
I
know
mark
I
should
get
a
set.
Yeah
Marcel
doesn't
like
this
either.
He
didn't
suggest
this
inside
twisted
his
arm
behind
his
back
to
about
it.
C
Basically,
we
don't
support
templating
with
files
in
a
nice
way
in
the
web,
IDE
and
I
thought
about
this
too,
where
yeah,
let
me
open
up
the
web
way
like
if
I
have
like
need
to
add
a
docker
file
in
a
folder
or
something
I'm,
not
sure.
If
we
do
that
nicely
or
not.
Let
me
just
let
me
see
if
we
do
next
here
I'm
in
playground,
MIDI
file,
oh
yeah,
it
looks
like
oh
no
I,
can't
well
he'll,
never
mind,
then.
C
Didn't
touch
them:
okay,
Venus
by
rename
at
the
docker
file.
Yeah,
so
check
this
out.
All
of
it
to
say
like
there's.
This
tight
coupling
of
the
name
of
the
file
to
the
temple
yeah
introducing
custom
templates,
I'm
gonna
pick
I
want
to
start
one
of
my
blog
posts,
but
that's
not
gonna,
be
the
name
of
a
fire.
My
name
can
be
something
specific,
and
so
the
editor
supports
this.
But
we
don't
necessarily
support
this
and
Brian
from
a
UX
perspective.
C
A
A
time
like,
is
there
like
an
expectation
of
like
time
to
come
back
to
the
web
IDE
and
like
solve
this
cuz
like
like
I,
guess
my
my
point
would
be
right
like
if
we're
in
12:6
thinking
about
this,
like
we
have
to
go
through
and
think
about
the
like.
What
would
it
take
to
make
single
file
Monaco
and
like
what
are
the
things
that
the
single
file
editor
could
do
that
like
single
file?
Monaco
needs
to
do
like
this
feels
like
one
of
those
things
that
the
single
file
Monaco
needs
to
do.
A
C
Doesn't
need
to
be
right
now,
but
it's
good
I
do
want
to
waste
awareness
on
and
yes,
cuz.
It
is
related
to
that
as
well.
But-
and
it's
also
to
keep
in
mind,
so
we
do
have
a
community
contribution.
That's
really
only
gonna
be
effective
on
the
single
file
editor.
So
you
know
this
new
feature
that
the
community
triggers
working
on
is
he
doesn't
if
he
or
she
me
and
I,
really
be
aware
that
the
single
file
editor
is
a
dead
man
walking?
C
A
A
A
C
Know
and
the
other
one
and
the
other
the
same,
the
way
it's
handled
in
single
file
editor.
It
didn't
on
that
to
pick
up
on
it,
but
it
was
relatively
simple.
Just
add
relatively
simple,
but
this
one
is
problems,
because
when
I
look,
what
happened
when
I
change
the
drop-down,
it
changed
the
name.
Look
right!
If
I
go
and
change
this
name,
I
no
longer
like
if
items
like
oh
well,
this
is
actually
my
license.
Well,
what
just
happened
I
would
actually
put
on
the
root
directory.
It.
C
A
Perfect
yeah,
okay,
yeah
I,
think
no
more
so
your
thoughts
are
I.
Think
maybe
we
just
think
about
this.
Well,
maybe
it's
too
cool.
Maybe
we
need
to
think
about
this,
like
entire
temp
living
thing
inside
of
the
web
ID
in
general,
because
it
looks
broken,
it
looks
like
it
has
the
same
behavior
bugs
that
the
that
were
recently
introduced
into
single
file.
I,
don't
know
he's
the
single
file.
Editor
got
new
bugs
where.
A
A
B
C
A
C
That
issue
then
I
linked
when
there
would
be
really
awesome
assigned
it
to
you
more
so
so,
and
it
doesn't
need
to
be
handled
in
this
milestone,
but
if
we
can
maybe
have
a
decision
on
it
on
12.6,
maybe
we
could
start
in
a
12-1
that'll
be
great,
because
the
community
contributor
said
he
was
interested
in
actually
actually
do
what
needed
to
be
done.
Their
heads,
okay,
cool,
hey.
We
can
take
a
look
at
it.
Awesome
I
appreciate
it.