►
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
Hey
everybody
I'm
an
eel
from
glitch
and,
as
some
of
you
might
know,
glitch
is
a
tool
that
lets
anybody
easily
create
a
full
stack
web
app
right
in
their
browser
and
hopefully
have
fun
doing
it.
It's
also
a
community
where
people
code
together,
collaborate
together,
share
the
apps
and
the
projects
they've
created,
and
it's
really
been
something
special
over
the
last
couple
years
to
watch
it
grow.
A
But
what
I
wanted
to
do
is
share
some
of
the
lessons
we've
learned
that
are
applicable
way
beyond
any
one
product
or
any
one
company
and,
interestingly,
there
are
sort
of
two
key
lessons
that
are
particularly
relevant
to
the
open
Jas
community.
One
of
the
first
insights
we
had
was
what
seems
like
a
small
idea
at
first
that
we
don't
code
alone,
and
you
know
we
started
it
as
sort
of
a
superficial
level.
A
Thinking
about
the
fact
that
you
could
edit
code
together-
and
that
was
where
that
idea
really
started,
but
the
more
we
talked
about
it,
the
more
we
thought
about
it,
the
deeper
that
idea
seek
I'm
gonna
come
back
to
that.
One
of
the
other
early
choices
we
made
was
that
while
any
programming
language
or
any
toolkit
can
work
on
glitch,
we
were
gonna
focus.
We
were
going
to
make
a
choice.
A
decision
about
what
community
we
wanted
to
be
part
of
and
choice
we
made
was
to
support
JavaScript.
Now.
A
These
days,
the
majority
of
developers
who
work
in
the
world
have
JavaScript
as
part
of
their
toolkit.
Now
it
might
be
for
build
scripts.
It
might
be
something
that's
helping
out
as
they
use
another
programming
language,
but
it's
there
and
that's
radical
because
there's
no
point
in
history
before
now,
where
there's
been
a
programming
language
that
most
developers
use,
it's
really
extraordinary
and
it's
gone
kind
of
unremarked
that
this
milestone
happened.
A
But
it
speaks
to
the
power
of
what
javascript
is
and
the
truth
is
that's
a
question
worth
asking
what
is
JavaScript,
because
it's
not
just
a
language
and
it's
not
even
just
a
family
of
languages.
I
mean
these
days.
We
see.
Typescript
is
so
ascendant.
The
tools
are
soaked
and
I'm
old-school
enough.
I.
Remember
back
when
we
had
jscript
an
actionscript
anybody
still
remember:
jscript
I
mean
there's
been
a
family
of
languages
and
tools
for
a
long
time.
So
what's
different
well
a
lot
of
times.
A
The
reflex
when
we
talk
about
what's
different,
is
to
go
to
thinking
about
the
language
itself.
Maybe
it's
the
way
it
uses
curly
brackets
and
semicolons.
Maybe
it's
something
to
do
with
you
know,
inheritance
and,
and
the
truth
is
those
things
matter.
Those
things
matter
as
a
programming.
Language
becomes
more
popular,
but
a
lot
of
those
things
were
in
place
when
it
started
25
years
ago,
and
yet
there's
been
a
renaissance
over
the
last
decade.
A
We
need
to
understand
why
it
has
become
so
central
to
the
way
that
all
of
us
work
and
what
we
realized
is
JavaScript
has
become
a
network,
maybe
even
a
network
of
networks,
and
that's
not
an
obvious
statement
to
make.
We
can
talk
about
as
a
language.
We
can
talk
about
it
as
a
runtime
when
we
talk
about
there's
a
lot
of
different
things,
but
talking
about
JavaScript
as
a
network
is
a
little
bit
well
controversial
to
some
people.
So
I
won't
explain
why
I
say
that
in
what
ways
is
JavaScript
a
network?
A
What
does
that
even
mean?
Well,
take
a
look
at
the
period
in
which
JavaScript
has
taken
off
over
the
last
decade
and
see
what
other
tools
and
technologies
and
platforms
have
been
ascended.
At
the
same
time.
Let's
look
at
sharing
answers
with
you.
Let's
look
at
sharing
answers
with
each
other
on
Stack
Overflow.
A
In
fact,
if
we
want
to
understand
these
behaviors
and
the
shape
of
the
activity
around
JavaScript,
it
starts
to
look
more
like
almost
a
social
network.
It
looks
like
the
apps
we
use
to
keep
in
touch
with
our
friends
or
that
we
use
to
share
photos.
It
doesn't
follow
the
typical
pattern
of
a
programming
language,
especially
because
most
languages
of
a
certain
age
start
to
crescendo
and
then
decrease
in
popularity.
They
become
irrelevant,
but
that's
not
the
case
here
so
now,
when
we
start
to
think
of.
A
Maybe
there
is
a
social
network
that
is
formed
around
JavaScript,
the
question
arises
of
whose
network
is
it?
Who
is
it
designed
for
who
had
the
idea
to
create
these
things
at
whose
welcome
on
that
network?
And
these
questions
are
important
because
we've
had
those
same
questions
arise
on
conventional
social
networks
right,
we
think
of
well
a
lot
of
times.
A
Just,
as
importantly,
we
have
to
think
about
the
ideas
that
underpin
the
creation
of
these
networks,
because
there
are
a
lot
of
assumptions
that
go
into
creating
any
technology.
Sometimes
they
are
a
common
set
of
values.
Sometimes
there
are
common
set
of
delusions
and
in
either
case,
it's
really
really
important
to
understand
what
those
assumptions
are,
so
that
we
know
what
it
is
are
actually
building
together.
A
People
talked
about
how
software
was
becoming
more
influential
in
the
world
and
we
start
to
hear
that
phrase.
Software
is
eating
the
world.
There
are
lots
of
other
sort
of
pithy
phrases
like
these,
but
I.
Think
these
out
is
two
of
the
most
common
that
you
tend
to
hear,
especially
at
conferences
like
this
one,
but
also
just
in
the
general
discussion
about
how
software
technology,
the
tools
that
we
use
and
the
tools
that
we
make
are
impacting
the
world
around
us.
A
Give
me
a
small
example:
I've
had
this
peer
experience
a
number
of
times.
Probably
all
of
you
have
had
this.
If
you've
been
coding
for
more
than
a
few
years
where
I
picked
a
toolkit
framework
that
I
really
like
and
I
made
it
part
of
my
standard
dev
setup,
and
that
was
how
I
had
started
up
new
projects
and
at
first
it
was
awesome,
because
I
got
really
good
at
it,
and
I
felt
like
I.
A
Oh
you're
still
using
that
framework,
because
there's
like
the
new
hotness
and
I,
don't
know
why
you
haven't
moved
on
to
it
and
it
started
to
feel
like
being
frankly
out
of
fashion,
it's
a
little
weird
way
to
think
about
a
programming
framework.
But
it
was
definitely
that
sense
that
the
network
was
moving
on
without
me
and
it
manifested
in
a
lot
of
different
ways.
We
start
to
see
fewer
updates
on
that
toolkit
from
the
creators.
You
know
whether
they're
the
core
committers
or
the
company
that
owns
it.
A
You
know
that
framework
starts
to
become
something
that
decays
over
time.
That
framework
starts
to
become
something
where
the
documentation
comes
a
little
bit
out
of
date
and
that's
just
a
minor
example.
That
was
just
something
where
I
felt
honestly
a
little
bit
coerced
into
I,
better
move
on
to
a
new
framework.
A
This
thing
is
well
not
the
thing
I
should
use
anymore,
even
though
it
still
solves
the
problem
that
I
wanted
it
to
solve,
but
there
are
a
lot
deeper
problems
that
can
come
from
the
network
having
this
impact
on
us,
especially
if
you
think
about
the
idea
software
eating
the
world,
because
the
network
impacts
people
who
are
not
coders
and
not
programmers.
You
know
the
truth.
Is
the
world
of
non
coders
has
started
to
think
of
us
as
authorities
on
domains
that
we
don't
necessarily
know
anything
about
what
you
think
about
data.
A
We
know
it
is
something
that
is
dirty
and
often
inaccurate
and
often
has
the
same
bugs
as
the
software
that
created
it
right.
We
know
it's
imperfect,
but
outside
of
the
role
of
coders
people
treat
data
as
if
it
were
authoritative
and
correct.
They
treat
it
like
it's
the
truth.
We
would
never
assume
the
data
we
get
or
the
truth,
and
so
that's
a
lesson.
That's
often
not
obvious
to
people
who
don't
code,
and
that
keeps
repeating
in
more
and
more
serious
ways.
A
The
network
of
programmers
in
the
world
is
having
impact
on
spaces
that
we
didn't
even
know.
We
would
impact
one
of
the
ones
that
jumps
out
to
me
most.
Clearly,
it's
going
back
a
few
years
ago,
several
years
ago
now,
when
I
first
started
hearing
about
the
increased
attention
to
police
violence
here
in
the
United
States,
and
a
lot
of
the
solutions
that
were
proposed
going
back
years
and
years
now
involve
technology.
A
They
involve
things
like
body
cameras
for
the
police,
and
the
idea
was
that
well
to
use
the
programmers
phrase
many
eyes
make
bugs
shallow.
The
idea
is
that
lots
of
people
seeing
and
witnessing
police
violence
happening
would
cause
it
to
stop
happening
and
truthfully
until
four
or
five
years
ago,
I
believe
that
too,
because
it
had
been
framed
in
the
rhetoric
of
the
software
industry,
the
technology
that
was
eating
the
world
I
bought
into
it
I
believed.
Well,
you
know
this
might
fix
these
problems.
A
This
might
fix
these
bugs
in
society,
and
the
truth
is,
as
we've
painfully
seen.
It
doesn't
there
were
some
incorrect
assumptions
here
using
the
logic
of
software
in
a
world
that
has
nothing
to
do
with
software.
It
doesn't
work
using
a
technological
solution
to
a
problem
that
is
cultural
and
social.
Doesn't
work
and
I
didn't
catch
it
I
didn't
want
to
see
it
I
wanted
to
believe
that
our
technologies
would
help,
and
there
was
a
deeper
lesson
here,
which
is
that.
A
Technology
was
not
the
answer,
and
so
there
are
limits
to
these
networks.
There
are
limits
to
how
technology
will
imitate.
Echnology
cool
approaches
can
fix
the
problems
we
have
in
society.
Think
of
it
from
a
technology
standpoint.
You
can't
fix
the
lower
levels
of
the
stack
beneath
the
tools
that
you're
using
you
know.
Reporting
a
bug
is
meaningless
if
the
institution
are
reporting
it
to
doesn't
consider
it
a
problem,
it
won't
fix
it.
A
That's
a
lesson
was
painful
for
me
to
learn,
but
not
obviously
nearly
as
painful
as
the
impact
that
it's
had
on
society,
because
politicians
believed
it
elected
officials
believe
that
many
people
believed
that
if
we
would
just
apply
technology
to
a
social
problem,
it
would
work.
But
it's
not
enough.
A
Now,
that's
not
to
say
that
networks
don't
give
us
power.
They
do,
but
only
in
certain
ways
that
the
network
of
technology
that
we
create
can
move
power
around
within
people
in
that
network,
but
it
can't
bring
new
people
in
right
and
it
also
can't
challenge
us
to
interrogate
what
are
the
assumptions
that
network
was
built
around
because,
as
painful
as
that
example
was
there's
also
a
lot
of
power.
A
There's
honestly
a
lot
of
hope
that
I
see
because
you
know
we
joke
about
the
size
of
there-
are
node
modules
directory
right
and
and
how
it's
so
easy
to
just
pull
down.
You
know
gigabytes
of
code
that
we
don't
even
know
what
they're
doing,
but
the
truth
of
it
is.
We
can
instantly
almost
automatically
reuse
the
work
of
thousands
of
other
coders
around
the
world,
millions
of
lines
of
code.
A
It's
almost
automatic
to
be
able
to
not
just
stand
on
the
shoulders
of
giants,
but
take
advantage
of
the
brainpower
and
the
generosity
of
programmers
around
the
world
and
I
think
about
the
way
we
share
code
and
share
your
answers
with
each
other,
and
it's
it's
almost
like.
We
take
it
for
granted,
but
this
is
an
extraordinary
act
of
kindness
that
coders
extend
to
one
another.
A
A
Well,
that's
the
promise
of
technology
right,
and
so
there
are
two
sides
to
this.
There
is
this
great,
optimistic
and
altruistic
sense
of
how
we
share
our
great
technologies
with
one
another,
but
there's
also
that
reality.
We
all
know
where,
even
aside
from
the
profound
social
ills,
we
know,
every
open
source
libraries
might
have
bugs
in
it
we've
all
seen
times
when
a
bug
goes
on
fixed
for
years
and
years.
A
Nobody
looked
at
that
code,
you
know
the
theory
might
be
many
eyes
make
bugs
shallow,
but
a
lot
of
times
many
eyes
are
looking
at
something
else.
We
keep
assuming.
Somebody
else
is
going
to
fix
that
bug
and
a
lot
of
times.
Somebody
else
thinks
we're
going
to,
and
that
is
what
we
have
to
really
challenge
ourselves
on,
because
we
have
also
seen
the
positive
potential.
A
All
of
us
have
had
that
moment
where
a
bug
gets
fixed
for
us
almost
for
free
right,
the
we
do
an
update
of
our
you
know,
dependencies
and
all
of
a
sudden
that
thing
that
we
have
been
struggling
with
is
fixed
almost
magically.
We
are
able
to
extend
that
to
each
other
to
the
people
that
are
already
in
the
network,
and
it
does
feel
like
magic,
I
mean
I
think
about
even
just
from
a
language
standpoint.
The
fact
that
we
talk
about
dependencies.
A
So
I've
tried
to
challenge
myself
a
little
bit
about
whose
choices
I
am
accepting
unquestioningly.
You
know
the
truth
is
every
day,
I
use
tools
made
by
organizations
that
I
don't
agree
with
every
day.
I
use
software
and
code
made
by
companies
that
I
would
like
to
not
support
and
I
feel
the
other
side
of
that
very
acutely.
You
know
I
work
at
a
company
where
a
glitch
we
do
hope
you
use
our
tools,
but
I
know
that
people
need
to
make
their
own
judgments
about.
Do.
I
feel
good.
A
Now,
using
these
tools
do
I
feel
like
I'm
supporting
something
I
can
believe
in,
and
so
we've
pushed
ourselves
at
the
ground.
Can
we
have
a
business
model
that
doesn't
involve
you
know,
surveillance
based
business
models,
we're
not
doing
creepy
things
with
people's
data?
We're
not,
you
know,
reselling
their
information,
somebody
else,
but
it's
hard,
because
we
also
have
to
compete
against
companies
that
do
do
those
things,
and
so
we
end
up
with
imperfect
answers.
I
am
NOT
preaching
about.
We
do
the
one
right
thing
by
any
means:
I'm
not
pointing
any
fingers
at
anybody.
A
That
I
couldn't
point
myself.
I
just
think
that
we
have
to
push
each
other
to
work
a
little
bit
harder.
You
can
think
a
little
bit
harder
about
who
is
making
the
choices
around
the
technologies
that
we
use,
who
were
supporting
when
we
use
them
and
who
we're
excluding
when
we
strengthen
our
networks
and
give
power
to
our
networks,
but
don't
think
about
who
is
excluded
from
those
networks?
A
What
I'm
hoping
is
that
we
can
challenge
each
other
and
that
we
can
see
our
acts
of
creation
and
collaboration
encoding
and
take
pride
rightfully
and
the
fact
that
there
is
such
a
generous
spirit.
You
know
I
see
it
every
time,
I
go
to
any
event
with
coders.
There
is
just
this
general,
genuine
sense
of
camaraderie
and
a
willingness
to
share
knowledge
to
share
insights,
but
a
lot
of
times.
We
don't
push
hard
enough
around
thinking
about
how
others
take
the
code.
A
We
make
the
ideas
we
share
apply
for
the
problems
that
may
not
be
appropriate
for
apply
them
in
situations
that
we
didn't
anticipate
and
cause
real
harm,
and
so
we
need
to
lift
that
importance
of
those
ideas.
We
need
to
challenge
each
other
about
our
responsibility
to
one
another
and
I.
Think.
Most
importantly,
we
need
to
remember
that
we
don't
code
alone.
We
are
always
coding
in
collaboration
with
thousands
or
millions
of
people
around
the
world,
and
we
are
also
always
creating
an
environment.
There
are
billions
more
who
don't
have
a
say.
A
I'm
gonna,
challenge
myself
to
try
and
do
better
in
those
regards
and
I'm
gonna
ask
all
of
you
to
do
the
same
and
I
hope
we'll
each
hold
each
other
accountable,
as
we
do.
I
hope
that
we'll
deliver
on
the
promise
that
we
all
had
the
first
time
we
ever
wrote
a
line
of
code
that
we
thought
we
could
make
something
useful.
We
thought
we
could
solve
real
problems.
We
thought
we
can
maybe
even
make
the
world
a
little
bit
better
and
I
think
if
we
hold
each
other
accountable.
That's
exactly
what
we'll
do.