►
From YouTube: Node.js User Feedback Initiative Meeting - July 30
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).
B
Great
alright,
thank
you
Michael,
alright.
So
today
this
is
the
no
dis
user
feedback
team
and
today
is
an
internal
team
meeting.
We're
gonna
be
looking
at
some
of
the
programs
we
have
in
flight
and
preparing
for
the
enterprise
use
case,
a
user
feedback
session
that
we'll
be
hosting
here
on
the
16th
of
August.
So
we've
shifted.
B
B
B
B
So
today's
agenda
is
hold
this
up.
Has
that
in
front
of
them
everybody.
B
B
Purpose
for
meeting
that
we've
had
and
even
has
been
working
through
some
of
the
the
potential
issues
there
and
you
know,
let's
go
ahead
and
have
a
look
together
today
and
have
see
where
they're
at
it's
a
primary
role
in
the
workplace,
not
debugging
issues.
I
am
the
person
that
debugs
issues
and
evolves.
Ops,
I,
debug
issues,
I,
don't
debug
issues
all
right,
so
this
is
a
strong
bent
towards.
Are
you
debugging
issues.
A
B
That
makes
sense,
you
know,
I'm,
not
seeing
you
know,
sort
of
some
of
the
categorization
of
folks
like
site,
reliability,
engineer.
You
know,
I
assume
that
that
fits
in
DevOps
operations,
it's
kind
of
a
modern
operations
role
with
a
little
bit
more
of
a
a
programming
bin.
Is
there
anything
else
that
we're
missing
in
terms
of
you
know,
gaining
understanding
of
of
this
you
know
I
might
I,
might
I
think
it
might
be
interesting
to
engage
not
just
yeah.
A
B
B
B
C
C
B
A
B
Right
right-
and
you
know,
I-
think
that
that
you
interrupt
between
streams
since,
since
you
know
node,
you
know
evolved
with
streams.
As
being
you
know,
the
kind
of
higher
order
callback,
you
know
data
flow,
you
know
having
this
new
paradigm
that
we
can,
you
know
use,
but
you
know
do
they
Interop
well.
Now
that
makes
sense
all
right
next,
one
which
of
the
following
used
tools.
B
At
least
once
a
week
is
too
aggressive,
yeah
I
mean
you
know
this
is
this
is
a
little
bit
of
spearfishing
looking
for
folks
that
are
really
really
interested,
and
you
know
that
that's
good,
but
you
know
this
also
impacts,
folks
that
you
know
hey
it's
been
a
year
since
we've
had
a
major
production
issue
and
holy
heck.
There's
there's
one
now
now
what.
A
B
B
A
Right
and
because
he
hears
that
from
people,
even
though
he's
been
trying
to
send
the
message
that
you
know
the
ones
in
core
are
are
actually
quite
good
right
and
also
I
guess,
maybe
maybe
you're
suggesting
breaking
this
out
into
two
questions.
But
the
other
one
is
like.
The
trade-off
of
you
know
am
I
willing
for
them
to
be
a
bit
slower.
If
I
could
better
have
better
debug
ability
right.
B
B
Gonna
put
their
their
just
yeah
state
that
hi
Gary.
A
B
B
C
C
A
Think
there's
any
fixed
limits
in
terms
of
that.
The
the
main
feedback
we
got
was
to
make
the
questions
as
specific
and
is
closed,
as
is
reasonable.
Otherwise
you
know
so
like
this
is.
This
is
I,
think
some
good
feedback
in
terms
of
like
how
do
you
debug
for
getting
more
specific
information
about
how
that's
done?
A
How
frequently
so
yeah
I
mean
it
was
mostly
about
trying
to
get
make
things
which
are
quantifiable,
obviously
leaving
some
open-ended
questions,
because
you
know
sometimes
you
you
want
to
find
things
that
you
don't
have
the
preconceived
preconceived
notions
of,
but
I,
don't
think,
there's
anything
you
know,
they're,
not
gonna
tell
us
25
questions
or
too
many
and
20
or
enough.
So.
C
A
B
B
A
baseline
of
sort
of
technical
questions
and
I
I
think
there's
a
little
bit
more
context
outside
of.
If
someone
with
this
deep
context
of
an
understanding
of
promises,
as
Benjamin
has-
and
you
know,
we
need
to
connect
the
dots
to
you
know.
Folks,
who
are
you
know,
leveraging
promises
passionate
about
promises,
but
not
necessarily
you
know
in
the
weeds
debugging.
B
A
B
Right,
generous,
so
adjacent
concepts
like
generators
and
observables,
that's
a
good
one.
You
know
rxjs
style
things
and
and
koa
I
know:
PayPal
is
using
Co
a
lot
more
lately
and
Netflix
makes
extensive
use
of
rx.
Yes,
so
some
of
the
adjacent
abstractions,
interesting
I,
don't
know
if
we
want
to
go
down
that
path
or
not,
but
you
know
I
think
at
least
gathering
some
signal.
You
know
for
additional
exploration
right.
You
know,
probably
there
there.
Other
topics
like
generators,
observables
that
are
causing
you
pain,
might
be
a
good
addition
to
this.
B
A
A
So
I
think
really
on
this
one,
like
that.
The
ending
discussion
is
that
it's
gonna
be
moved
out
to
a
Google
Doc,
which
I
think
will
make
it
easier
to
refine
and
edit
the
questions
mm-hmm
into
a
forum
where
people
can
comment
and,
like
you
know,
type,
here's
what
we
think
it
should
be
as
opposed
to
having
to
read
through
the
whole
issue
right,
Brent
and
I
think
that'll
make
it
easy
to
look
at
here's
the
pictures
as
a
holistic,
and
so
if
we
can
go,
if
we
can,
you
know
it
sounded
like.
A
A
B
B
You
know
what
what
is
an
end
user
experience?
What
is
the
expected
end
user
experience
and
how
can
we
use
that
to
you
know
to
capture
here,
because
you
know
above
me
on
you
know,
providing
a
good
debugging
experience.
I
think
we
need
to
help
the
the
folks
involved
in
promises
capture
more
signal
around
end-user
expectation,
four
promises
to
help
advocate.
B
A
B
A
B
So
I'm
gonna
just
put
something
on
my
calendar
and
I'll
invite
you
all
to,
but
it
won't
be
a
meeting
meeting
to
just
review,
review
the
the
document
and
invite
in
Greg's
like
Greg,
to
have
a
look
yeah.
That
way
we
can
be
prepared
for
the
31st
to
sit
down,
and
maybe
you
know
when
we
invite
Greg
we're
gonna.
Ask
him
to
say:
hey.
Would
you
mind
plugging
this
into
Survey
Monkey?
So
we
can
review
that
content
and
authority
for
us
together,
yep
great.
B
A
B
B
B
C
C
I'm
seeing
something
looks
kind
of
old,
so
under
the
project's
the
last
bullet
item,
it's
manage
no
I'm,
sorry
that
the
above
one
we
are
currently
preparing
the
define,
teen
benchmarking
workgroup
survey,
that's
kind
of
all
I
know
we
are
not
going
to
modify
the
readme
file
all
the
time.
But
if
you
guys
have
anything
in
mind,
probably
we
need
to
modify
that
that.
C
A
B
A
B
A
You
know,
tooling,
an
enterprise
group
and
promises
general
yeah,
but
not
promises,
because
I
think
that
you
know
that's.
We've
said
that's
sort
of
like
a
support
for
a
different,
but
you
know
the
the
tooling
and
the
enterprise
groups
and
the
general
group
er
two
or
three.
You
know
ongoing
efforts
that
we
have
yes,
which
does
remind
me,
I,
guess
the
next
action
on
the
general
one
was
Stan.
Did
you
volunteer
just
to
set
up
something
in
terms
of
the
the?
B
A
A
A
A
Like
mid
to
late
September
but
I
think
having
an
issue
that
says
we're
doing
this,
oh,
we
already
created
the
Meetup
figuring
out
sort
of
what
we
want
the
general
agenda
to
be
because
I
think
we
want
to
make
sure
we
have
like
feedback
in
there
somewhere
about
how
we
weave
it
in
and
and
I,
and
they
have
you
create
that
issue
and
then
tag
it
at
least
show
up
on
our
agenda,
something
to
make
sure
we're
pushing
forward.
It's
too
easy
to
forget
things
on
this.