►
From YouTube: Create:Editor Think Big Monthly - November 2021
Description
This month we discuss executable snippets but can't avoid talking about cloud-based development environments.
B
A
B
A
B
B
D
B
B
C
I'd
love
to
be
in
the
discussions
of
like
you
know,
should
we
use
16
bits
to
represent
or,
like
enamy
bits
to
represent
the
epoch.
You
know
well.
That
means
it's
going
to
be
done
at
20
30,
something
I
was
like.
That's
okay,
we're
not
going
to
be
still
using
it
then
or
the
world
should
be
ended
by
then
like
then
come
why
at
2k
the
world's
supposed
to
be
over
now
what
what
happened?
You
guys
are
still
using
this.
D
E
E
Just
gonna
be
helping
today
we
can
just
kind
of
figure
out
what
we're
in
the
mood
to
talk
about,
but
the
the
three
I
had
in
mind
were
maybe
a
more
fun
one
and
something
we
don't
think
about
often
related
to
snippets,
but
the
idea
of
having
executable
snippets.
I
think
pretty
big
on
that.
What
that
could
mean
to
the
category
we
could
think
a
little
bit
smaller
and
more
tactical,
but
potentially.
E
Try
and
uncover
a
longer
term
plan
for
rich
editing
of
markdown
content
in
the
context
of
the
repository
view
or
the
web
editor
or
the
source
editor
or.
However,
we
want
to
frame
that
or
we
could
go,
think
really
big
and
reopen
all
the
discussions
around
the
note
development
environments
and
try
and
stay
more
along
the
lines
of
thinking,
big
and
not
retroing.
F
F
E
A
E
C
E
E
They
are
static
and
not
dynamic.
We'll
say
that
you
know
they
can't
really
do
anything
other
than
be
snippets
and
be
copied
and
be
edited.
So
I
think,
on
the
backlog,
we've
had
this
idea
of
executable
snippets
and
we
might
kick
off
the
conversation
by
talking
about
what
that
even
means
and
who
would
use
that.
I
don't
know
for
those
that
voted
for
executable
snippets.
What
what
about
it
interests
you
in
the
future.
A
I
know
there
is
server
side
and
client
side
exclusive,
snippets
and
yeah.
I
I
don't
know
which
one
we're
really
talking
about
when
we're
talking
about
and
these
things
and
this
like
from
the
server
side
like
that's
the
part
that
I
don't
really
understand
like
how
that
ties
in,
and
you
know
if,
if
there's
like
a
sequencing
thing
here
like
do
you
do
client-side,
like
you
know,
like
compile
this
javascript
kind
of
like
a
code
pen
or
is
it
like.
G
A
G
A
E
E
F
F
So
the
the
confusion
that
michael
has
is
is
very
very
is
quite
generic.
I
think
I
have
the
same
confusion
as
well
so
with
like.
I
will
vote
it
for
the
executable
snippets,
because
I
just
genuinely
want
to
hear
what
we
can
do
here
and
whether
we
can
do
anything
here
and
whether
we
really
want
to
do
anything
about
this,
because
I
was
I
was
thinking
about
the
same
thing.
F
The
other
day
when
we
were
discussing
the
source,
heater
architecture-
and
I
thought
well,
it
would
be
really
cool
to
have
snippet
like
executable
snippets,
so
that
we
could
just
play
with
like
with
the
isolated
snippet
and
make
it
run
and
do
some
chats
for
us
when
we
have
discussion
about
what
happens.
If
we
do
that
or
what
happens
when
we
do
that,
and
that
would
be
super
cool.
F
The
problem
is
that
I
sincerely
have
no
idea
how
we
could
how
we
could
create
that
thing,
like
we
have
the
executable
javascript
environment
through
the
code
sandbox
in
the
live
preview
right
in
web
id,
but
not
more
than
that.
Technically,
so
we
we,
if
we
say,
executable
snippets.
What
do
we
mean
like?
Is
it
just
the
javascript
executables
or
is
it
like
any
snippet
should
be
executable
or
this
there
are
so
many
questions
here.
So
I
think
the
we
we
have
to
figure
out.
What
is
the
ultimate
goal
like?
F
F
We
have
to
think
about
this
being
a
digestible
part
like
that
we
wouldn't
bite
much
more
than
we
can
chew.
Really
we
we're
very
small
team
anyway
and
we
could
probably
move
the
live
preview
to
for
javascript
files.
Somehow
I
don't
know
paul
will
will
be
the
person
probably
to
to
judge
about
whether
we
can
do
that
or
not.
F
E
So
I
would
say
that
we
should
think
big
and
not
think
about
the
limitations
of
our
team
as
much
as
the
potential
benefit
that
executing
code
within
snippets
can
offer
so,
whether
it's
paul
going
off
and
building
this
feature
himself
or
whether
we
have
a
team
of
20
engineers
assigned
to
it,
because
the
market
opportunity
is
huge
or
we
acquire
a
company
to
make
this
happen.
That's
kind
of
that's
not
the
part
of
the
mental
exercise
that
I
think
we
need
to
focus
on.
I
do
think
it's
potentially
a
hard
problem.
H
E
So
that's
I
think
what
we
should
talk
about
is
what
are
the
benefits
to
either
what
are
the
use
cases
for
either?
Who
would
be
using
those
and
in
what
context,
and
then
a
little
bit
about
how
we
might
make
that
work,
but
not
so
much
about,
like
you
know
how
the
you
know.
Six
engineers
we
have
on
the
team
are
really
gonna.
Actually
do
it.
C
I,
when
we
talked
about
this,
the
reason
I
did
not
vote
for
this
issue
because
I
could
not
immediately
see
what
was
the
benefit
of
executable
snippets
but,
as
we
were
talking
about
it
specifically
as
michael
talked
about
codepen
it
dawned
on
me.
I
think
there's
a
pretty
neat
use
case
for
this,
where,
when
I
think
about
project
snippets
and
it'd
be
really
cool
to
see.
C
A
project
that
is
providing
some
sort
of
library,
you
could
look
through
snippets
of
live
examples
off
the
latest
release
of
the
project
in
use
and
actually
how
it
runs
and
how
that
how
that
looks
like
whatever.
So
I
think
when
we
talk
about
who
this
would
be
for
and
what
are
the
use
cases
and
the
wind
there.
E
G
B
And
I
think
that
that
would
be
very
powerful
within
projects
for
trading
context
and
offering
solutions
to
problems,
because
it
doesn't
necessarily
all
have
to
happen
inside
a
merge
or
inside
a
code
review.
But,
funnily
enough,
you
could
probably
eventually
look
to
link
it
back
into
a
code
review
process.
If
you
wanted
that's
kind
of
the
direction,
I
see
where
we
might
be
able
to
take
the
wiki
executable,
snippets
and
snippets
in
general
into
something
that
might
be
very
usable
for
people
who
are
maintaining
repos
in
gitlab.
F
F
So
first
of
all,
paul's
point
was
really
good
one
about
using
this
in
the
context
of
a
project
where
we
have
so
technically,
we
by
default
snippets
will
somehow
like
inject
well,
we'll
have
will
have
the
library
or
like
the
project
somehow
injected
and
have
these
snippets
would
have
the
full
context
of
the
project,
because
that
makes
sense
when
the
snippets
are
used
in
the
context
of
the
project
that
we
have
some.
We
have.
These
snippets
have
knowledge
about
this
project
right.
F
Otherwise,
what's
like
the
the
difference
is,
is
not
that
big
between
the
pro
the
simple
snippets
and
the
project
ones.
How
to
do
this
technically
is
super
challenging.
I
think-
and
it's
like
it's
pretty
interesting,
but
what
david
mentioned
is
that
that's
that's
that's
an
interesting
thing
like
I
have
never
thought
about
snippets
in
the
context
of
wiki.
F
We
are
just
including
the
snippet
amp
that
would
allow
it
to
be
executable
in
the
context
of
the
wiki
page
right.
Is
that
what
you
mean
yeah,
that's
more
or
less,
exactly
like,
like,
like,
like
code
sandbox,
for
example,
does
when,
when
you
sort
of
add
a
snippet
and
then
you
can
run
it
right
so
like
consent,
box,
different
sources
to
do,
allow
that
right,
yeah,
exactly
yeah,
and
that
and
that's
this
means
that
technically,
this
is
not
not
necessarily
coupled
to
the
wiki
pages.
F
Right
like
this
would
be
useful
for
any
scenario
where
we
have
our
snippet
snippets
embedded
right,
so
our
snippets
are
embeddable
and
they
can
be
embedded
everywhere
by
chad.
But
that's
that's!
That's
a
pretty
pretty
neat
scenario
and
that's
exactly
what
so,
technically,
there
are
two
different
scenarios
right
like
the
first
one
is
when
we
include
the
snippet
somewhere
inject
it,
and
then
it's
executable
on
that
side.
F
Another
one
is
when
we
create
sort
of
a
a
sandbox
in
our
snippets
so
like
we
have
up
to
10
snippets
up
to
10
blobs
available
to
be
added
for
one
snippet,
so
we
create
some
sort
of
a
mini
project.
We
can.
We
can
call
it
probably
so
like
sandbox
mini
project
and
then
comparing
like
combining
this
with
what
paul
said
were,
for
example,
snippets
with,
with
the
context
of
the
within
the
context
of
the
project,
have
knowledge
about
the
project.
That
would
be
super
powerful
thing.
F
F
For
example,
is
this
what
you
do
and
is
this
what
you
expect
to
get,
and
that
would
give
us
sort
of
very
a
very
tangible
and
very
obvious
scenario
of
what
has
to
be
proved
or
fixed
in
the
project
in
the
first
place,
but
that
by
combining
these
two
ideas
would
be
super
powerful.
I
think
it's
gonna
be
super
challenging,
but
very
powerful.
C
A
I
had
it
open
and
I
headed
up,
but
then
I
kind
of
put
it
back
down
because
yeah
I
was
thinking
about
what
you
said
earlier
about
like
project
snippets
and
providing
like
documentation
kind
of
stuff.
Then
I
was
thinking
like
oh
there's,
like
mdx
in
the
world
of
react
where
you
like
jam
and
like
react
code
inside
mark
down
and
then
you,
you
know,
magically
happens,
but
then
I
was
like,
oh
with
snippets
it.
It's
kind
of
like
doing
that,
and
then
I
I
was
just
like.
A
Oh
that's
just
like
so
that
when
dennis
was
talking
about
the
wiki,
I
was
like
okay,
he
covered
that
kind
of
point
and
then
the
point
about
stack
overflow.
This
one's
really
interesting,
because
the
stack
overflow
is
good
to
like
sample
or
like
do
like.
Oh
here's
how
to
do
like
the
for
loop
or
something
like
that,
but
like
sometimes
in
the
big
repo
like
this,
it's
almost
like
you
might
need
to
run
the
whole
beast
to
get
the
code
running,
to
run
that
one
little
bit
and
then
this
slowly
edges
towards
remote
development.
E
I
B
But
that
raises
a
really
good
question.
Then:
is
there
an
a
broad
enough
and
big
enough
audience
that
executable
snippets
would
appeal
to
that?
We
wouldn't
just
cover
if
we
leaned
into
remote
development
like
would
we
is
there
a
use
case
for
this
or
would
be
wasting
our
time?
What
is
what
is
the
target
in
general
right
like
what.
F
C
C
I'm
sorry,
I
lost
my
train
of
thought,
but
I
did
add
to
our
agenda
dog
there's
some
really
interesting.
Libraries.
Often
libraries
have
to
do
this
like
showcasing
of
what
their
library
can
do
and
if
we
thought
that
would
be
an
interesting
use
case
to
solve
inside
of
git
lab.
I
think
that's
where
executable
snippets
could
be
an
interesting
way
to
showcase
a
user
may
want
to
showcase
what
their
library
can
do.
C
A
Cool
so
dennis
brought
up
a
good
point
about
what's
the
objective
and
I
was
like
looking
at
some
of
the
stuff:
it's
like.
We
don't
fully
understand
how
snippets
are
used,
so
it
might
be
worthwhile
to
see
like
where
snippets
are
being
embedded
now
and
seeing
those
make
a
good
use
case
to
execute.
So
let's
say
it's
a
lot
of
like
code
snippets
about
like
here's,
how
to
do
xyz
or
like
tutorial
like
things
and
then
maybe
it's
worth
rendering
that
out
in
client
side.
A
But
if
it's
more
like
snippets
says
like
here's
like
the
get
command
to
like
do
this
like
rebase,
and
it's
like
documented
within
the
team,
you
probably
wouldn't
want
that
to
be
executed
anytime
soon,
so
that
just
stays
as
is
so
as
the
group
responsible
for
snippets.
I
think,
personally,
I
don't
really
know
the
answer
to
this
like
exactly
how
snippets
are
used
in
like
as
deep
as
I
would
like,
or
I
don't
think
we
have
that
information.
But
I
think
this
might
be
a
good
deep
dive
into
like
snippets.
E
F
G
F
D
H
H
E
Organizations
we
don't
know
why
and
there's
a
issue
on
the
backlog
could
be.
Data
is
not
getting
collected
or
reported
correctly.
It
could
be
that
that
is
actually
the
case
and
people
on
sas
don't
create
snippets
as
often
because
they're
doing
things
more
for
themselves
or
smaller
groups.
I
don't
know,
but
right
now,
that's
where
the
data
seems
to
indicate
as
far
as
who's
using
it.
B
That's
really
interesting
yeah.
That
strikes
me
definitely
as
a
possibility
for
like
maintaining
internal
documentation
or
training
internal
codes
in
a
in
a
concise
way.
My
I
only
raised
my
hand
because
I'm
just
very
curious
about
the
contextual
history
of
snippets.
What
who
were
they
originally
designed
for?
What
was
the
gap
that
we
were
originally
looking
to
close
when
we
opted
to
create
them?
C
G
F
In
this
scenario,
we
are
talking
about
sort
of
a
different
thing
like
if
we,
if
we
talk
about
conventional
snippets
as
we
have
them
now,
they
are
indeed
like
were
intended
to
be
competing
with
gis.
Never
happened
really
like
people
still
use
gists,
they
don't
use
gitlab
snippets,
but
this
is.
This
is
sort
of
one
sort
of
paradigm
where
it
works.
But
if
we're
talking
about
showcasing
this
means
that
we
are
trying
to
look
into
something
like
story
story
book
where,
where
things
are.
F
F
We
will
have
to
we'll
have
to
employ
different
tools,
employ
different
approaches,
but
this,
like
technically
everything
any
decision,
now
boils
down
to
clear
understanding
of
who
are
the
users
of
this
feature
like
who
we
are
trying
to
at
least
even
if
we
don't
know
who
we
are
going
to.
Who
who
is
this
feature
for
at
the
moment
at
minimum?
We
have
to
realize
who
we
want
to
use
this
feature
after
we're
done.
F
Who
is
our
target
audience
if
the
audience
is
unknown
now
or
we
want
to
change
the
audience,
and
I
have
a
strong
feeling
that
we
have
no
answers
to
any
of
these
questions.
To
be
honest
and
that's
the
main
problem,
because
without
clear
understanding
of
the
answers
to
these
two
questions,
everything
we're
talking
about
is
just
speculation
in
our
our
personal
wish.
As
engineers
working
at
gitlab,
but
how
this
feature
could
be
potentially
used,
we
never
know
like
we.
We
saw
that
gists
are
used
by
people.
F
Why
not
to
use
gitlab
snippets,
but
people
don't
use
this
for
for
for
the
use
of
cases
where
they
can
use
gists.
So
this
may
maybe
due
to
different
reasons
like
first
of
all,
that
github
is
much
better
integrated
in
different
services
and
different
things,
things,
and
when
people
write
blog
posts
or
do
some
something
it's
nearly
like
it's.
There
is
a
much
bigger
case
that
there
is
really
neat
kind
of
integration,
if
not
full
integration
to
to
to
github
and
gists,
and
that's
why
people
just
fall
back
to
that.
F
C
Yeah,
I
think
I
think
you're
right
on
the
money
with
with
that
is
the
that's
the
big
money
question
and
I
would
propose
going
a
step
further
and
rather
than
just
thinking
who,
who
is
the
target
audience
really
understanding
what
problems
are
people
having
that
could
be
solved
and
then
then,
we'll
figure
out,
okay,
marketing
to
these
specific
people,
and
so
thinking
about
what
are
the
problems
that
people
use
and
that
this
this
use,
this
new
tool
would
help
solve,
I
think,
is
and
is
critical.
I
think
some
things
that
are
really
vague.
C
I
have
a
hard
time
seeing
how
executable
snippets
could
be
helpful
in
code
review.
I'd
love
to
know
more
about
that
idea
of
what
are
the
problems
we're
trying
to
solve
there?
What
are
the
actual
like?
What's
an
example,
interaction
and
when
I
think
of
like
showcasing,
I
don't
really
know
if
executable
snippets
is
that
much
better
than
like
a
gitlab
pages,
and
so
I
don't
really
know
if
that
is
a
problem,
but
maybe
it
is.
C
C
Okay,
yeah,
we
just
it
just
it's
a
the
proverbial
hand.
Is
there
so
one?
I
don't
know
if
anyone
has
used
jupiter
notebook
for
writing
python
scripts.
It's
a
really
interesting
executable,
snippet
environment,
where
you're
writing
lines
of
code,
but
you
can
execute
each
block
and
get
like
immediate
feedback
of
what
happened
and
all
of
it,
usually
these
jupiter
scripts.
C
C
C
So
I
see
oh
here
I
am
on
page
two,
so
these
are
the
starred
ones,
there's
some
that
are
like
not
super
starred
and
there's
some
that
have
a
good
amount
of
stars,
but
like
there's
just
markdown
documents,
nothing
to
execute
here's
just
like
a
config
file,
there's
not
really
anything
we
could.
That
would
make
sense
executing
there's
and
here's
one
that
I
saw-
and
I
was
like.
Oh,
this
is
interesting.
Like
there's
a
lot
of
the
snippets
that
are
like.
Oh,
you
know
how
to
build.
C
C
I
I
C
E
I
mean
so,
I
think,
we're
hitting
on
a
few
really
good
points
dennis
that
you
make
about.
We
need
to
think
about
who
we're
using
what
problems
we're
solving
and
then
looking
at
the
most
frequently
or
most
popular
types
of
snippets,
and
reconciling
that,
with
the
the
feature
request
itself
or
the
the
desire
to
enhance
snippet
functionality,
to
the
point
that
they're
executable
don't
exactly
match.
So
what
we
would
be.
E
I
think
what
we'd
be
saying
if
we
were
to
implement
this
feature
is
that
we
are
enabling
new
use
cases
that
are
not
necessarily
what
our
users
are
going
to
snippets
for
today,
and
I
think
what
we've
talked
about
some
really
good
examples
like
the
the
one
that
jumps
out
in
my
mind,
is
like
the
documentation
page
for
strength,
the
gold
standard
for
documentation.
I
believe
they
have.
You
know,
code
examples
in
line
with
their
api
documentation,
but
that
those
code
examples
are
live
and
you
can
actually
type
and
it'll
return
results.
E
H
E
H
E
E
Output
and
and
give
live
examples
similar
to,
like
you,
said,
jupiter
notebook
or
I
wrote
x
code
playgrounds
because
that's
kind
of
where
I've
spent
a
bit
of
time
messing
around
and
it's
kind
of
fun,
but
you
can
do
the
same
thing
or
as
you're
typing.
Any
every
expression
shows
output
on
the
side
and
you
can
manipulate
that
output.
It's
really
interesting,
that's
sort
of
the
like
extreme
of
this
conversation,
which
is
taking
snippets
in
an
entirely
different
direction.
E
That
doesn't
benefit
to
your
point
earlier
that
doesn't
benefit
config
files,
we're
not
going
to
execute
those
config
files.
There's
no
reason
to
so.
Maybe
the
discussion,
if
and
when
we
do
this
is-
is
this
even
called
snippets?
Are
we
enabling
something
different?
Is
this
actually
part
of
the
remote
development
environment
functionality?
H
A
A
That
came
up
was
like
bookmarking
things.
Maybe
a
small
thing
would
be
to
like
start
these
things
and
like
make
people
like
this
will
probably
help
internal
people,
but
will
also
give
us
a
signal
of
what
people
are
like
starring
and
like
what's
useful
to
people,
so
it
works
both
ways,
so
that
might
be
like
it's
not
executable,
but
it
might
help
just
organizing
and
then
like
yeah,
for
the
stuff,
like
showing
code
example,
sometimes
on
github.
A
It's
almost
like
a
pathway
to
do
that
for
us
rather
than
building
this
whole
thing
out
is
building
like
a
pathway
to
like
start
a
new
project
so
like,
as
I
have
like
a
video
file
or
like
a
react
component,
is
like
cool
here's.
How
you
want
do
you
want
to
like
share
it?
And
then
you
press,
like
you,
create
a
project
from
this,
and
it
creates
all
the
scaffolding
for
like
a
react
project
and
sticks
it
in
there
for
you
and
you're
like
cool.
A
Now
I
have
like
an
easy
way
to
share
this,
and
then
we
can
then
leverage
like
a
git
pod
or
like
live
review
app
or
whatever
we
already
have.
We
don't
need
to
build
all
that
stuff
or
people
can
just
do
whatever
they
want
with
that
project.
Well,
we
don't
need
to
build
it.
Then
we
get
this
whole
like
cross
stage
thing
where,
like
from
a
snippet,
you
create
a
project
in
a
pro
project
account
and
all
those
things
go
up
as
well.
So
yeah.
H
A
A
So
this
could
be
the
extreme
version
of
you
know
how
we're
thinking
about
editing
in
blocks
in
the
content
editor,
and
so
we
would
have
like
a
mermaid
block
and
then
maybe
we
have
like
something
like
a
stats
one
where
you
like,
pull
in
like
chart
js
and
then
you
have
a
json
file
or,
like
you
know,
whatever
you
do
to
join
those
things,
but
maybe
that's
like
a
very
elaborate
widget
that
we
built
for
the
content.
Editor.
B
B
You
know
config
files,
these
sample
configs,
I'm
thinking
of
things
like
pipeline
ci
files.
As
an
example
like,
I
think,
chad
once
had
this
idea
of
the
fastest
ci
file.
You
could
possibly
have
to
bootstrap
a
project
for
quick
pipeline
times
and
it's
you
know
endorsed
by
gitlab
or
something
similar
it
doesn't.
It
doesn't
completely
relate
to
the
embedded
snippet,
so
I
don't
want
to
go
down
a
rabbit
hole
with
it,
but
it
just
is
something
that
has
come
up
a
couple
of
times,
and
so
I
just
wanted
to
flag
it.
E
E
E
F
So
I
think
because
I
still,
I
still
think
that
we
have
to
answer
those
questions
and
in
order
to
answer
those
questions,
we
need
statistics.
We
need
statistical
data,
we
need
some
research
in
order
to
get
the
statistical
data.
We
need
more
people
to
start
using
the
feature
and
telling
us
what
is
good.
F
What
is
not
how
they
use
it,
what
they
use
it
for-
and
here
comes
the
idea
that
I
had
a
long
long
time
ago
when
we
just
started
refactoring
the
snippets
like
two
years
ago,
or
something
like
this
about
being
able
like
providing
users
with
an
easy
mechanism
of
creating
the
snippets.
So
I'm
doing
a
review
of
of
an
mr-
and
I
see
nice,
nice
code,
nice
execution-
that
I
don't
want
to
forget.
F
I
go
on
copy
the
text
in
the
diff,
I
right
click
or
do
the
keystroke
and
I
select
save
as
snippet.
It
goes
into
my
personal
snippets
boom.
The
the
the
way
to
re
they
reach
out
to
the
snippets
becomes
like
super
fast
super
short,
and
we
will
we'll.
We
would
allow
people
to
actually
build
this
base
and
we
will
build
because
the
the
user
base
for
this
feature
that
we
could
use
after
some
time
to
run
and
research
and
figure
out
what
this
feature
is
used
for.
F
The
problem,
though,
is
that
once
we
make
create
creation
of
the
snippets
easy
we
will
have,
we
will
face
another
problem
of
the
massive
storage
format
for
the
snippets,
so
it
will
be
all
in
one
place
like
huge,
huge
list
of
snippets,
and
then
we
will
have
to
come
up
with
some
structure
to
the
snippets.
But
that's
another
story.
That's
after
we
get
some
some
information.
I
think
I
think
we
would.
F
It's
just
way
too
long
and
like
we
have
to
provide
this
in
context
again,
getting
back
to
the
in-context
editing
we
have
to
to
review
the
in
context,
create
content
creation
in
this
case
in
context
creation
of
the
snippet.
So
I'm
still
in
the
context
of
the
merch
blast
review,
I
copy
the
text.
I
do
do
some
action.
Keystroke
right
click
create
a
snippet
boom.
It's
generated
with
some
dummy
title
like
order
generated
title,
but
it's
there,
I
don't
lose
it.
F
C
I
wanted
to
throw
a
crazy
idea
what,
if,
instead
of
thinking
just
ourselves
to
snippets
what,
if
it
was
just
executable,
arbitrary
code,
which
I
think
may
actually
be
the
name
of
a
security
vulnerability,
but
never
mind
that.
So
what
if
I
mean
snippets,
may
be
the
way
we
implement
this,
but
I
mean
I
can
see
it
being
really
cool
if
I'm
typing
a
markdown
comment
or
something
being
you
know,
I'm
saying
hey
back,
take
back
to
backtick.
C
E
Well,
I
guess
yeah
maybe
to
take
that
a
little
further
to
to
make
it
more
secure,
potentially
like
we
could
have
those
be
snippets.
You
could
embed
a
an
executable
snippet
as
a
code
block,
and
then
we
rely
on
the
security
of
the
snippets
feature.
However,
we
figure
out
how
to
make
this
secure
to
handle
that
concern,
and
that
way
it's
not
necessarily
like
I'm
gonna,
write
arbitrary
code
and
execute
it
in
line.
It's
like
we've
got
a
snippet
feature.
E
C
E
C
Be
a
way
around
it
and
not
to
to
also
just
propose
thinking
of
it
differently.
The
implementation
there
may
be
a
shared
implementation
that
snippets
happens
to
use
and
markdown
comments
happen
to
use
like
it
may.
The
abstraction
may
not
be
with
snippets
the
abstraction
may
be
this.
I
want
some
sort
of
arbitrary
code,
runtime
environment.
E
Yeah,
no,
that's
that's
a
great
point
and
and
dennis
back
to
what
you
were
saying.
I
think
there
are
other
ways
before
we
go
ahead
and
build
it
to
validate
or
before
we
get
critical
massive
users
to
validate
the
the
problem
and
the
users,
and
that's
a
good
point
that
this
is
a
great
example
of
something
that
we
would
want
to
run
proper
competitive
analysis
and
problem
validation
and
do
active
research
find
people
to
talk
to
about
the
problems
they're
actually
trying
to
solve
about.
E
H
E
Snippets
to
be
so
popular
that
we
can
extract
from
the
usage
data,
the
problem
itself.
That
said
michael
left,
a
comment
in
the
agenda,
doc
that
I
wanted
to
revisit
about.
If
snippets
are
used
more
in
self-hosted,
is
it
more
like
a
replacement
for
codepen
for
internal
users,
and
so
I
wanted
to
go
back?
I
don't
want
to
like
shift
or
think
big
to
just
saying,
like
let's
build
codepen,
but
I
maybe
we
could
just
talk
about
what
are
the
benefits
you
as
designers
and
developers
get.
H
E
Something
like
codepen,
and
would
it
be
beneficial
to
have
that
closer
to
your
gitlab
experience
right,
like
embedded
within
the
gitlab
experience?
Is
there
any
benefit
there
and
that's
as
far
as
far
as
I
understand
more
in
line
with
what
we
would
be
talking
about,
client-side
execution
anyway,
and
we
wouldn't
be
as
and
maybe
that's
a
smaller
surface
area
to
discuss.
A
Yeah
so
for
codepen
stuff,
I
used
to
use
it
to
show
like
front-end
interaction
or
css
stuff.
That's
like
focused
on
the
thing
so
that
the
engineer
can
almost
like
cut
and
paste
and
that,
but
from
an
internal
perspective,
oh
like
so
what
you
would
need
to
do
is
almost
like
work
in
rectangles
because
you
don't
want
to
like
share
an
exact
like
code
and
like
structure
of
like
oh.
This
is
how
I
do
that.
A
This
is
how
we
do
it
at
this
company,
because
and
someone
can
just
like
snatch
it
and
get
it,
but
if
self-host
it
feels
like
there's,
you
know,
there's
probably
firewalls
everywhere
so
so
then
I
can't
go
to
codepen.
As
so.
That's
like
I'm
thinking
from
my
banking
days
like
you
can't
go
anywhere
except
like
certain
websites.
So
it's
almost
like
yeah.
It's
a
good
question
like.
F
F
C
Hey
yeah,
I
was
adding
to
the
agenda
of
one
of
the
things
that
I've
used.
Codepen
like
services,
which
is
really
helpful,
is
with
teaching
other
people
front-end
development,
because
the
feedback
loop
is
so
short.
If
I
make
a
change,
I
can
visually
see
the
change,
the
scope
of
the
changes
and
changes.
I
make,
though,
are
also
really
short.
It's
just
it's
just
all.
This
is
all
right
there
back
in
the
day.
I
remember
using
jsfiddle
a
lot
and
they
actually
have
a
live.
C
They
have
a
multiplayer
fiddle
experience
where-
and
I
don't
think
codepen
does
this,
but
you
can.
You
can
live
program,
multiple
cursors
on
doing
the
same,
js
fill
and
that's
super
helpful
and
super
cool.
The
something
that
I
can
find
personally
myself
using
it
is.
It
can
be
really
helpful
because
you
don't
have
to
set
up
webpack
and
all
the
other
things
if
you
want
to
be
using
some
or
babble.
C
If
you
want
to
be
using
some
modern
things,
and
it's
just
because
right
now
front
of
development
got
so
complicated.
So
that's
a
huge
win
of.
I
don't
have
to
set
up
the
dev
environment.
It's
just
there
and
if
I
want
to
play
around
with
something-
and
I
also
don't
have
to
tear
down
whatever
environment
I'm
currently
working
in,
if,
if
that's
the
situation
as
well
too,
it's
just
there.
E
H
E
E
E
The
the
education
aspect
is
interesting,
too
paul
with
like
teaching,
but
I
think
that
goes
back
to
sort
of
the
live
documentation,
because
your
goal,
in
both
cases,
is
education,
you're
learning
by
doing
you're
either.
I
don't
want
to
start
the
conversation
this
late
into
our
session
about
collaborative
editing
and
multi
user
simultaneous
editing,
but
your
that
would
be
a
cool
feature
too.
In.
H
E
And
pair,
both
with
with
almost
no
setup,
you
know
you
just
spin
up
a
snippet,
let's
dig
in
and
start
working
an
argument
can
be
made.
Then
you
could
just
do
that
in
the
web
id
or
whatever
and
then
save
it
out
as
a
snippet
later.
Maybe
that
doesn't
need
to
start
as
a
snippet,
but
I
think
these
things
are
all
pretty
closely
related
at
this
point.
So.
C
Sorry
I
don't
have
my
hand
up,
but
I
do
realize
I
was
unmuted,
which
I
think
is
like
having
super
hand
up,
I'm
joking,
the
collaborative
editing
is
just
kind
of
nice.
I
I
still
haven't
seen
that
being
like.
Oh,
this
is
a
game
changer.
But
what
is
a
game?
Changers
inc?
Incredibly
short
feedback
loop.
I
make
a
change.
I
see
the
change,
that's
and
you
mentioned
that's
how
you
learn
learning
by
doing
and
if
that's
a
problem
we
want
to
explore.
B
B
This
arbitrary
executable
piece
of
code
that
you
could
write
into
markdown
sounds
like
the
right
direction
for
the
broadest
appeal
to
the
developers
for
just
various
scenarios
I
mean
it
seems
like
it
would
be
highly
useful
to
be
able
to
do
that
and
again,
it
kind
of
suddenly
reminds
me
of
when,
as
a
developer,
you'd
be
on
stack,
overflow
and
you're.
Looking
for
a
solution,
and
not
only
do
you
see
the
code,
but
you
can
actually
see
the
effect
the
code
has
by
clicking
run,
and
that
is
worth
its
weight
in
gold.
E
H
C
You
know
this
remote
development
environment
that
we
have
to
spin
up
for
everybody,
and
I
think,
there's
there's
some
options
that
could
allow
us
for
lots
and
lots
of
different
languages
run
these
things
on
the
client
side.
Considering
web
assembly,
like
you,
could
have
a
web
assembly
build
of
python
that
runs
python
scripts
and
some
sort
of
browser-based
containerized
environment
and,
like
so
there's
those
are
all
part
of
the
solution
and
I
think,
should
block
us
considering
something
it
should
be
really
valuable
and
really
cool.
H
E
H
H
E
E
H
B
E
Do
they
even
know
that
they
want
that
if
we
start
coming
up
with
these
ideas
in
a
more
tangible
way
that
we
can
take
to
research,
then
we
can
talk
about
like?
Is
this
solving
a
problem
for
your
organization?
Is
it
solving
a
problem
for
you
individually?
Is
this
something
you
would
use
in
the
context
of
your
documentation
site,
say
in
the
context
of
wiki
or
something
like?
E
E
Sessions
are
watched,
a
ton
on
youtube
like
end
to
end,
but
hopefully
we
can
post
this
to
the
teammate,
our
teammates
that
couldn't
join
and
then
also
anybody
else
that
might
be
interested
in
for
posterity.
When
we
go
back
to
do
some
solution
or
problem
validation
on
this,
we
can
reference
our
video.
So
thanks
for
your
input
have
a
good
rest
of
the
day
and
take
care,
see
you
next
time.