►
From YouTube: Special Live-stream: NRE Labs is ONE YEAR OLD!!
Description
In this video we sit down with Mike Bushong, who runs Enterprise Marketing at Juniper Networks, to discuss the origins of the NRE Labs project, how the first year of life has gone since it was launched, and what the future looks like.
A
Thanks
for
joining
everybody,
this
is
a
special
stream.
We
we
sort
of
broke
the
cadence.
We've
been
doing
a
little
bit
more
of
a
biweekly
thing
lately,
but
we
couldn't
wait.
This
week
we
had
to
announce
that
we
are
officially
one
year
old.
The
NRA
lapse
project
was
unveiled
at
next
work,
2018.
If
I
have
my
years
correctly
these
days,
it's
kind
of
hard
to
keep
track,
but
yes,
2018
October,
20
18th
is
when
we
went
live
and
it's
exciting.
It's
been
a
year,
it's
kind
of
crazy.
A
That's
been
a
year,
I
that
really
snuck
up
on
me:
hey
fun,
being
honest,
I,
guess
and
I
kept
on
everybody,
but
here
we
are
a
year
later.
So
for
this
anniversary
stream,
we
are
happy
to
have
our
esteemed
guest
Mike
Bhushan,
who
and
who,
in
pretty
much
every
way,
is
responsible
for
the
creation
of
this
project,
as
he
as
the
the
sort
of
the
the
leader
of
the
team
that
created
this
in
the
first
place.
So
Mike
welcome
thanks
for
joining
it's.
B
Actually,
my
pleasure
I
just
want
to
be
really
clear
on
stuff,
though,
if
you
want
to
create
a
project
like
this
for
anyone
listening.
If
you
want
to
do
this
on
your
own
step,
one
hire
really
smart
people
step
two
get
out
of
the
way,
I
think
it's
a
gracious
that
you
say,
I'm
responsible,
but
outside
of
hiring
you
Derek
Lisa,
James
Kelly,
outside
of
getting
the
right
people
on
board.
This
is
really
your
baby,
so
happy
birthday.
Thank.
A
You
yeah,
it
is
a
team
effort
and
fast
and
especially
as
we
go
down
the
path
of
like
making
this
truly
like
a
community
project
like
there's
so
much
that
I've
discovered
as
part
of
this
project
that
I
just
I
just
can't
I
can't
I
can't
do
it.
So
it's
just
it's
good
to
have
a
team
of
folks
behind
this.
A
It's
just
kind
of
kind
of
bizarre
in
a
good
way,
very,
very
good
way.
So
let's
talk
I
think
a
little
bit
about
like
let's
turn
the
time
back
way
before
even
October
of
last
of
last
year.
Mike.
Why
don't
you?
Why?
Don't
you
sort
of
it
tell
it
tell
us
sort
of
what
the
thoughts
were
going
into,
not
just
the
entering
labs
project.
I.
Don't
think
anybody
really
planned
it
to
happen?
B
So
I
fundamentally
I
think
if
you
look
at
where
the
industry
is
I,
think
we're
just
at
a
point
where
it's
about
operations,
I,
think
the
architectural
approach
you
know,
protocols
and
moving
packets
devices
and
Mershon
silicon
I
think
those
bits
are
actually
largely
well
established,
I
think
people
kind
of
know
what
to
do.
I
think
you
know
the
switch
sort
of
looks
like
a
switch
router
sword.
Look
like
routers
I,
think
at
the
time
in
or
the
moment
in
time,
when
those
things
are
like
really
what's
driving,
where
the
industry
goes.
B
I
think
that's
that's
kind
of
behind
us,
and
so,
if
this,
if
we
shift
the
the
point
of
emphasis
from
like
what
do
we
build?
How
do
we
move
packets
to
then?
How
do
we
sort
of
manage
and
kind
of
deal
with
the
infrastructure
and
all
the
bits
there
on
top,
like
I've
thought,
for
for
probably
a
decade
now
that
that
was
really
the
next
big
wave
that
was
kind
in
2000
gosh
2009?
B
We
started
doing
work
with
puppet
and
chef
as
an
exhibit
out
and
the
idea
there
was
that
if
the
network
operator
becomes
really
the
dominant
personality
going
forward,
then
that's
that's
how
we
pivot
it's
not
really
the
beginning
from
an
automation,
perspective
and
I.
Think
I've,
given
you
the
kind
of
this
story,
but
for
everyone
else,
you
know
I,
fundamentally
believe
its
operations,
its
automation
of
matter,
then
you
have
to
look
and
I
described
things
in
terms
of
products
and
sales
right.
B
The
idea
you
know
generally,
is,
if
you,
if
you
look
at
something,
that's
not
really
taking
off,
then
you
have
to
decide.
You
have
a
product
problem
where
you
have
a
sales
problem.
If
you
have
a
product
problem,
it
means
you
just
haven't
built
the
right
thing
yet,
and
so
you
know,
of
course
it
hasn't
taken
off
because
you
don't
have
the
right
set
of
stuff.
B
If
you
have
a
sales
problem,
the
argument
is
that
you
have
the
right
products,
but
for
whatever
reason,
the
adoption
is
just
not
there
and
also
kind
of
spirit
about
the
long
version
of
this.
But
you
know
when
it
comes
to
automation,
we
have
to
to
reconcile
the
fact
that
we,
we
probably
don't,
have
a
product
problem.
We've
had
technology
for
Kate
spends
two
decades
a
thing
good
enough
to
go.
Do
things,
but
we've
gotta
rationalize.
B
A
Yeah
and
I
think
there's
one
thing
that
we
still
like
we've
said
this
I
think
a
few
times,
but
I
think
it
it
warrants
being
underscored,
which
is
the
fact
that
you
know
to
to
move
the
industry
forward.
You
don't
have
to.
In
fact,
it
is
actually
probably
detrimental
to
make
it
all
about
one
particular
set
of
products
right
like
it's.
Not
it's
not
this.
Isn't
it
to
your
point.
This
isn't
a
product
problem.
A
The
problem
is
that
people
aren't
speaking
automations
speak,
not
that
there's
not
speaking
Juniper
automation
speak,
but
that
they're,
just
not
speaking,
automation,
speak
across
the
board.
It's
actually
a
much
bigger
problem
than
I.
Think
anybody
realizes
so
the
the
unique
opportunity
for
us,
I
think
was
to
create
a
community
resource
without
you
know,
really
limiting
the
scope
of
what
we
talked
about.
The
the
scope
of
the
of
the
content
that
we
can
talk
about
is
actually
pretty
limitless.
Yeah.
B
The
other
piece
is
once
you
realize
it's
an
adoption
problem
and
you
look
at
you
can
kind
of
triage
your
root
cause.
Why
why
that's
the
case?
The
other
thing
I
think
in
the
early
you
know
days
of
this
project
and
really
automation
for
us
over
the
last
couple
of
years.
When
you
realize
it's
not
even
like
a
vendor
problem,
it's
very
well
one.
It's
it's
sort
of
terrifying.
If
you
work
at
a
vendor,
but
it's
freeing
once
you
realize
that
it's
not
about
you
know
how
do
we
move
juniper
forward,
but.
C
B
How
do
you
move
the
industry
forward?
It
sort
of
unshackles
you
right,
it's
no
longer
about
how
do
I
tie
something
to
a
piece
of
hardware
or
a
piece
of
software,
so
I
can
sell
more
it's
no
longer
about
how
do
I
drive
traffic
to
a
Juniper
website.
It's
no
longer
about
how
do
I,
even
you
know,
captured
leads
so
I
can
sell
you
something
like
once.
We
sort
of
separated
that
out
so
you're
think
that
was
a
pretty
liberating
moment.
I
think
an
inflection
point
terms
are
one
forward:
I
did.
C
The
the
really
interesting
thing
that
that
this
team
has
done
is
just
conceptualizing
that
that
mental
shift
and
that
that
process
change
in
a
technology-based
way
and
in
addressing
it
in
a
technology-based
way
and
that's
kind
of
unique
that
I
think
that's
that's.
What's
sort
of
special
about
in
our
in
our
labs
to
me,
yeah.
A
It
is
kind
of
funny
that
you
put
it
that
way.
I
haven't
really
thought
of
it,
but
it's
true
like
it
like
for
a
lot
of
open
source
projects,
the
the
product
of
those
projects
or
the
outcome.
The
desired
outcome
is
a
is
a
new
and
more
innovative
technology
solution
right,
whereas,
whereas
our
outcome
is
a
skill
set-
or
you
know,
new
skill
sets
like
that
is
the
thing
that
we
produce
or
that
we
intend
to
produce
yeah.
A
We
do
that
with
software
and
a
few
other
things
that
we
bring
to
the
table,
but
it's
unique
that
the
outcome
isn't
anything
it
has.
It
isn't
anything
to
do
with
any
new
technologies.
Even
though
we
created
some
technologies
to
make
it
possible,
it's
kind
of
funny
Mike
one
thing
I,
looking
back
what
we
do,
I,
don't
think
anybody's
realized
at
the
time,
but
one
of
the
most
pivotal
moments
in
the
journey
towards
entering
labs
was
this
meeting
we
had
out
in
Temecula
California.
B
B
I
would
say:
you're
gonna
order
order,
some
food
pair
it
with
the
wine
and
then
order
like
a
chaser.
You
can
wine,
but
I
actually
have
brought
I
brought
a
maddened
and
James
Kelly
down
to
my
place,
and
we
sit
for
a
couple
days.
Let's
just
talk
about
what
we're
gonna
do
in
the
automation
space.
That's
really
where
I
think
the
energy
lapse.
Piece
came
up
where
it
was
like
the
idea
started
to
really
codify
and
get
it
momentum
there.
B
At
the
time,
though,
what
we're
really
talking
about
was
how
do
we
drive
training
and
education
across
a
broader
industry
right
and
very
sincerely
with
the
idea
that
if
we
move
the
industry
forward,
even
if
it
doesn't
necessarily
lead
to
a
direct
sale
of
a
product,
we
will
have
done
one
we
would
have
done.
We
will
have
done
right
by
the
industry,
and
so
there's
some
some
karmic.
B
Obviously,
we've
been
drinking
the
automation
kool-aid
for
a
while
if
people
are
not
automated
than
the
things
that
are
important
in
our
portfolio,
just
don't
matter
to
them,
so
the
idea
was,
we
could
still
kind
of
attached
it's
what
junipers
doing,
but
we
didn't
want
that
attachment
to
be
to
be
really
explicit
and
we
didn't
want
that
connection
to
be
particularly
tight.
In
fact,
I
think
I
talked
to
early
on.
As
you
know,
what
I
wanted
to
call
this
thing?
Initially,
it
was
uncook
eat
right.
Was
this
whole
idea
that
we
could
build
a
website?
B
B
But
but
we
wanted
to
be
like
so
overt
about
not
being
just
another
project
focused
that
sort
of
vendor
ends
and
means
we
want
it
to
be
go,
they
really
rotate
the
other
way,
and
that
was
at
the
beginning
of
it
and
then
coming
out
of
that
was
visually.
The
idea
that
we
wanted
to
take
a
kind
of
a
like
micro,
education
approach,
I
think
we
talked
about
gamifying
things.
B
B
A
For
sure
I
mean,
like
that's
the
biggest
thing.
I
think
that
is
different
is
that
is
that,
especially
in
the
automation
conversation
sometimes
intentionally,
sometimes
not
it.
The
there's
this
there's
this.
This
belief
that
you
need
to
become
a
CS
major
in
order
to
even
write
your
first
Python
script
that
you,
if
you
don't
know
how
to
implement
a
bubblesort,
that
you
have
no
business,
writing
any
scripts
whatsoever
and
I
find
that
to
be
obviously
just
wrong,
but
also
like
in
terms
of
getting
folks
started.
There's
there's
no
motivation
there.
A
There's
no,
there's
no
reason
to
continue.
If
that's,
if
you
know
that
that's
the
first
step
you're,
just
like
man,
I'm
gonna,
stick
with
what
I
know,
and
you
know
what
I
don't
blame
me
for
thinking
that
way.
But
yet
we
as
an
industry,
seem
to
have
sort
of
over
rotated
on
this
idea
that
you
need
to
be
an
expert
in
order
to
be
a
beginner
which
is
a
little
backwards,
so
yeah
for
sure
I
mean
that
one
of
the
biggest
things
I
think
going
into
this
project
is
we
have
to
solve
that
problem?
A
We
have
to
get
folks
not
just
feeling
like
they're
doing
something
but
actually
doing
something
in
the
first.
You
know
five
to
ten
minutes.
You
you
hear
in
a
meeting.
You
need
to
learn
Python,
whether
whether
or
not
you
agree
with
that.
Why
not
just
spend
the
five
minutes?
Learning
Python
go
to
the
site.
That's
the
idea.
The
other
thing
I
do
want
to
call
out.
One
very
early
inspiration
for
me
was
when
I
was
going
through.
School
was
hurricane
electrics,
ipv6
sage
program,
which
is
awesome.
They
it's
not.
A
A
That
idea
that
for
the
longest
time,
I've
wanted
to
build
something
where
folks
could
actually
learn
by
actually
doing
the
thing
as
we
started
to
get
into
automation,
we
started
thinking
like.
Is
there
a
way
for
us
to
have
a
site
where
people
could
like
take
their
Python
scripts
and
like
slot
it
into
this
site
and,
and
it
goes
ding
if
it
you
know
that
script,
we
had
all
kinds
of
crazy
ideas
at
the
beginning
there,
but
yeah
I
know
that
for
me,
just
looking
back
a
we
did,
I
mean
it
was
it
fun.
A
It
was
fun
hanging
out
in
Temecula
for
a
few
days,
but
I'm
like
I.
Don't
think
any
of
us
really
realized
that
that
the
the
dot
was
sort
of
like
the
starting
point
on
what
would
then
become
over
that
summer.
I
think
we
met
in
like
April
or
something
like
that,
and
then
over
that
summer
was
was
sort
of
I,
know
Derek
and
James
and
I
all
came
here
to
my
house.
A
We
had
all
kinds
of
delicious
beer
and
meats,
and
we
we
just
I
read:
we
have
a
whiteboard
where
I
drew
the
architecture
of
syringe
and
all
that
kind
of
cool
stuff.
That
was
pretty
fun
so
so
that
summer
was
sort
of
when
we
started
really
like
working
on
this.
What
about
what
about
when
we
actually
did
launch
in
October?
Do
you
have
any
memories
from
literally
a
year
ago
of
like
of
the
the
talk
not
only
around
juniper,
obviously
juniper,
there
were
some
folks
with
a
juniper
that
kind
of
got
the
heads
up.
A
B
B
A
B
But
I
think
the
one
we're
trying
to
we
had
to
explain
even
internally
why
we
would
be
doing
something
that
doesn't
necessarily
tie
directly
back
into
the
products
right.
That
by
itself
requires
some
explanation,
and
so
there
was
a
big
part
of
that
and
then
the
second
piece,
once
you
get
past,
that
it
was
just
like
people's
people's
heads
were
blown.
This
is
you're
like
okay,
so
you
know
what
can
you
do
next
and
so
the
conversation
quickly
shifted
to
you
know:
here's
a
million
ideas
and
I.
B
Remember
thinking
at
the
time
like
how
do
we?
How
do
you
rein
it
in
right?
Because
it's
good
that
everyone's
kind
of
excited,
but
then
the
downside
is,
is
that
they're
all
excited
I,
think
about
Sisyphus,
roll
or
rock
up
a
hill?
You
know
the
one
thing
worse
than
roll
in
a
rock
up,
a
giant
Hill
is
chasing
it
down
the
other
side
and
I
think
when
we
launched
it
once
people
don't
understand
really
where
they
are,
they
don't
understand
the
steps
it
takes
to
build
out
on
a
project.
B
They
don't
understand
the
steps
it
takes
to
build
out
a
community.
Then
what
your
expectations
get
away
from
here,
you
spend,
we
spent
to
think
the
rest
of
the
year.
You
know
sort
of
trying
to
chase
that
and
make
sure
things
don't
work.
I,
remember
that
I
mean
to
me.
That
was
like
a
panic
moment.
You
know
when
it's
just
you
and
a
couple,
people
pushing
a
rock
up
a
hill
and
it
could
be
painful
and
it's
arduous.
It's
a
heart,
but
it's
not
it's
not
terrifying.
B
A
B
Crap
we're
in
it
now
right,
yeah
I
think
the
other
thing
we
did
which
I
didn't.
You
know
whole
credits,
it's
you
all
here,
but
I
mean
even
the
shifter
I
think
we
could
have
called
it
automation,
this
or
automation
that
it
could
have
called
it
any
number
of
things,
but
even
even
with
the
really
deliberate
naming
of
NRE
I
mean
you're
talking
about
changing
it.
Automation
discussion,
yeah.
C
B
Reliability
now
it
seems
obvious
now,
but
I
don't
think
it
was
obvious,
and
I
think
that
came
out
when
the
cosh
was
was
talking
about
the
role
of
network
reliability.
Engineering
I
mean
that
was
another
one
of
these
speculative
facts.
I
mean
I
could
have
gone
any
number
of
ways.
I
think
it's
worked
out
well
in
the
world's
coming
this
direction
or
just
good
yeah,
but
another
that
I
would
say
the
outcome.
B
There
was
anything
but
certain,
and
so
when
we
kind
of
took
a
project
that
was
uncertain,
we
got
a
package
it
in
a
way
that
was
uncertain,
and
then
we
aimed
it
at
people
in
the
way
that
was
uncertain.
It's
like
three
huge
spike
for
the
pathetic
it
all
had
to
pay
off
for
us
to
get
to
this
one-year
birthday.
A
Yeah
speaking
of
when
Vikash
started,
saying
it
it
I've
I've
I've
worked
on
a
number
of
side
projects,
none
of
which
I
ever
expected
to
to.
You
know
be
mentioned
at
on
a
keynote,
and
you
know
obviously
I'm
working
on
energy
labs
as
a
as
a
Juniper
employee.
So
it's
not
quite
a
side
project,
but
it
definitely
had
that
side
project
feel
especially
at
the
beginning,
just
because
I
at
the
time.
A
You
know,
of
course,
I
had
all
these
other
responsibilities,
and
so
that
moment
is
that,
were
you
rolling
it
up
the
hill,
and
then
it
goes
over.
I
felt
that
so
so,
very
so,
very
specifically
at
next
work,
because,
like
I
said
it's
like
you
know,
it's
like
something
I've,
just
you
know
sort
of
not
casually,
but
just
we've
been
working
on
for
a
few
months
and
all
of
a
sudden.
It's
there,
it's
like
that's
that's
kind
of
it.
Was
that
moment
it's
very
good
analogy.
A
A
One
was
you
know
we
we
we
wanted
to
get
this
out
in
October
of
last
year
as
a
proof
of
concept,
so
the
people
could
understand
what
was
that
we
were
bill.
We
didn't
want
to
just
get
it
to
some
finished
state
behind
closed
doors
for
five
years
and
then
dump
it
out
on
the
world.
What
we
wanted
to
do
was
get
it
finished
enough,
so
that
people
understood
what
we
were
trying
to
do
and
then
that
way
the
the
community
could
carry.
A
B
For
sure,
for
me,
it's
unquestionable
I
think
it's
about
how
do
we
light
the
fire?
The
question
is
how
you
spread
it
and
I
didn't
for
me,
and
that
only
happens
inside
the
you're
outside
the
halls
of
Juniper
for
sure
sort
of
inside
the
community.
I
think
what
we
see
is
divergent
quests
divergent
points
of
view,
and
so
the
reason
we
have
one
of
the
mix
of
people
working
on
it
that
we
do
is
because
year,
two
and
probably
years
three
four
five
six
are
all
about
community
yeah.
C
And
that's
typical,
the
lifecycle
of
most
open
source
projects,
rights
to
use
it
mostly
they
originate.
You
know
some
engineer
group
of
engineers
haven't
had
this
great
idea
and
sometimes
it
terminates
entirely
within
a
company
and
they
sort
of
build
a
proof
of
concept,
and
then
they
take
it
to
you
know
some
sort
of
independent
third
party,
a
Foundation
Conservancy,
whatever
sometimes
it's
it,
you
know
they
they
get
the
idea
and
they
take
it
to
their
foundation,
and
then
they
build
it
as
directly
as
a
community.
C
You
know
there
are
different
ways
to
go
about
it,
but
usually
the
the
first
year
is
is
just
building
the
thing
and-
and
you
know
getting
it
to-
if
not
a
beautiful
state,
something
that
is
recognizable
as
performing
some
useful
function
right
and
that
that
that
process
of
getting
to
from
from
an
idea
on
a
piece
of
paper
to
something
that
you
know
has
working
code.
That
process
tends
to
draw
some
people
in,
but
it's
it's
once
you
get
to
a
point
where
people
can
can
look
at
it
and
go.
C
Oh
I
see
this
why
this
might
be
useful
or
why
it
might
be
well.
I
want
to
be
involved
in
that.
That's
where
it
kind
of
the
things
really
started
to
picking
pick
up
stream
and
I.
Think
that's
where
we
are
right
now,
and
so
you
know
we're
we're
in
the
process
of
working
very
actively
to
move
the
project
to
an
independent
third
party.
That
will
facilitate
a
lot
of
things
it
will
make.
A
Very
cool
yeah
I
mean
it
like
I
said
it's
been,
it's
been
kind
of
a
crazy
first
year.
I
think
the
first
year
again
was
was
very
I
mean
we
still
have
a
lot
of
technical
things.
We
want
to
work
out,
but
yeah.
If
you're
one
was
about
just
planting
the
flag
in
the
ground,
then
year
two
is
definitely
about.
You
know
going
on
the
going
on
the
March
and
making
sure
everybody
is
involved.
That
wants
to
be
involved
so
closing
thoughts.
What
do
we?
What
do
we
I?
A
Don't
know
we're
gonna
close
out
the
stream
any
any.
Last
thoughts
on
on
where
we've
been.
Where
we're
you
think
energy
labs
could
go.
What's
like
the
what's
like
your
wish
list,
like
I
wish,
energy
labs
was
in
vinyl
on
the
international
space
station.
I
just
found
out
that
puppet
I
think
Luke
Kinesis
tweeted
the
puppet
was
on
the
space
station.
So
when
is
a
when
do
you
think
energy
labs
is
gonna,
be
on
the
space
station
Mike.
A
B
For
me,
I
think
that
the
future
is
a
little
like
I
think
this
is
the
part
that
gets
a
little
bit
uncomfortable
I
mean
I.
Think
candidly,
the
first
year
we
had
a
lot
of
control
because
the
vision
was
tight
and
the
first
steps
were
concrete
and
once
you
kind
of
expand
outside
of
that
first
year,
what
happens?
Is
the
vision
become
shared
and
so
it's
no
longer
mandated
from
top
down,
and
so
you
lose
a
little
bit
of
control.
It's
about
the
community,
as
we've
talked
about
I.
Think.
B
B
You
don't
know
what
people
are
gonna
do
I
think
you
know
the
things
that
give
me
hope.
You
know
when
you
see
people
who
are
you
know
you
don't
even
know
that
you're
impacting
them
and
you
see
them
reach
out
and
they
they
give
you
a
word
of
thanks.
I
can
be
like
a
good
example
down
in
Temecula.
We
have
people
in
our
house
just
random.
They,
like
random
friends.
B
Those
kinds
of
connections
to
me
like
that's
what
I
think
about
what's
next,
it's
it's
about
that
you
know
and
if
you're
saying
I'm
a
word
of
advice
even
for
you
is
that
I
think
the
as
we
think
about.
What's
what's
coming,
you
know
what
you
tend
to
think
about.
Is
the
market
you
think
about
the
community?
You
think
about.
You
know:
groups
of
people,
but
I
will
tell
you
that
the
impact
is
felt
by
individuals
and
the
engagement
happens
by
individuals
that
it's
not
some
blanket
market.
You
know
decision
that
gets
made.
B
It's
not
corporate
decision,
it's
the
it's!
The
passion
of
individual
people
that
carry
things
forward
and
to
me
that's
that's
the
thing.
I
think
I
really
hope
we
carry
forward,
but
there's
one
impact,
I
think
we've
had
it's.
You
know
whether
it's
Matt
or
he's
Derek
James.
Any
of
the
folks
who
we've
worked
with
it's
that
we've
you've
had
individual
impact
and
I
hope
that
that
carries
forward.
Because
I'll
tell
you
what
you
know.
Your
corporate
affiliations,
you
know
are
temporary
right,
but
the
personal
everybody
remembers
in
their
career.
B
The
people
who
made
a
foundational
difference
in
who
they
are
and
what
they're
capable
of
and
I
think
that's
what
we're
building
here
and
so
I
I
hope
that
the
personal
miss
that
kind
of
this
the
passion
I
mean
this
is
a
labor
of
love
in
many
ways.
I
hope
that
that
continues
to
be
front
and
center,
because
I
think
that,
for
me,
that's
what's
really
really
difference
me.
A
Awesome
yeah,
I,
wholeheartedly
agree
and
I've
had
similar
experiences.
It's
it's.
It's
very
useful
too,
because
again,
the
product
for
this
project
is
not.
You
know,
speeds
and
feeds
it's
it's
enhancing
skillsets,
which
is
very
personal
to
many
people,
and
it's
it's
easy
to
lose
sight
of
that
when
you're,
just
coding
all
day,
I
think
it's
important
to
keep
that
in
mind.
I,
think
for
any
really
for
any
discipline
is,
is
to
keep
the
your
eye
on
the
prize
and
for
us
that's
the
prize.
A
C
C
You
know
the
fact
that
this
is
something
that
can
be
used
by
training
companies,
so
they're,
not
spending.
You
know
the
first
to
date,
half
of
a
three-day
training
get
every
Guinea
everybody
just
set
up,
so
they
can
start
working.
You
know,
I,
think
that
that
that
kind
of
you
know
sort
of
it's
the
thing
that
lifts
all
boats
and
I.
Think
that
that's
you
know
the
thing
that
I
like
most
about
the
project
is
the
something
that
it's
it's
not
competitive
to
anybody
in
any
way.
C
It's
not
something
that
need
anybody
to
get
anxious
about.
It's
a
tool
that
anybody
can
use,
whether
it's
something
you
know
for
personal
use,
to
build
a
personal
skills
or,
to
you
know
further
their
business.
It's
it's
just!
You
know
it's!
It's
I
think
it's
just
a
fundamentally
helpful
thing
for
everybody,
so
yeah.
A
I'll,
let
go
that
I
mean
it.
That's
one
thing,
I
think
is
it
can't
be
repeated
enough?
It's
like
this
project
is,
is
everyone's
project
that
you
know
if
there's
a
if
there's
anything
we
should
focus
on
in
the
next.
You
know
year.
I
think
from
a
community
aspect
is
making
sure
that
everybody
understands
this
is
this
is
what
we
built
it
for.
We
didn't
build
it
to
be
the
the
King
and
queens
of
automation.
A
We
built
it
because
we
knew
the
industry
needed
something
like
this,
and
so
we
built
it
want
them
to
be
involved
cool.
So
anyway,
it's
about
half
an
hour
I
think
that's
a
probably
a
pretty
good
place
to
wrap
up
thanks
to
both
Lisa
and
Mike
for
for
attending,
thanks
not
only
to
you
for
carving
out
the
time
today,
but,
of
course,
for
your
involvement
in
this
project
and
the
way
the
the
innumerable
ways
that
both
of
you
have
helped
keep
things
moving
forward.
A
So,
thank
you
for
that
on
behalf
of
Derek
and
on
behalf
of
James,
thanks
to
everybody
for
watching
we'll
post,
this
recording
as
soon
as
we
can
probably
sometime
today
but
in
in
in
for
the
other
streams,
will
probably
resume
our
normal
schedule
next
week,
because
I
think
we
had
a
stream
last
week.
So
this
is
sort
of
like
the
the
odd
the
odd
stream
out.
So
thanks
everybody
for
watching
and
we'll
see
you
next
time.