►
From YouTube: Community Stream #24: Mike Soldner, part 2
Description
Community Stream #24: Mike Soldner, part 2
A
All
right,
that's
a
great
answer.
I,
you
no
wonder
we
are
very
tool,
centric
industry
right
now,
where
every
the
answer
to
every
problem
is
to
throw
a
tool
at
it.
What
you
described
is
almost
tool
this
right,
like
you
make
your
own
little
tools,
you
don't
make
you
don't
need
big
giant
frameworks
and
stuff
and
and
but
I
mean
the
you
do
for
some
things.
I
will
say
that
there's
some
there's
certain
things
that
some
frameworks
are
written
for,
that
they're,
very
handy,
like
napalm
and
and
netbox
and
stuff.
A
They
are
not
the
team,
that's
going
to
decide
on
the
tool,
so
I
don't
know
if
you've
kind
of
run
into
this,
like
what
what
kind
of
tools
if
you
looked
at
and-
and
you
said
earlier
that
you
talked
before
that
before
we
start
it
again-
that
you
know
that
you
have
that
you've
tried
to
talk
about
tools
with
other
oranges.
Can
you
talk
about
that?
A
little
bit
yeah.
B
So
we
we
have
predominantly
survived
to
date
on
on
Python,
writing.
I,
say
100%
of
our
stuff
is
in
Python
and
then
we
ran
Infoblox
info
block
shop
and
we
were,
we
would
leverage
net
MRI
pretty
heavily,
so
we
would
kick
off
something
in
Python,
it
would
do
a
bunch
of
stuff
and
then,
if
we
were
going
to
push
it
to
network
gear,
we
crafted
things
in
net
MRI
to
kind
of
be
our
I
guess.
I,
don't
know
way.
B
B
A
It
so
just
to
be
clear
when
you
say
that
what
pops
into
my
mind
is
you
know
you're
sitting
at
your
desk.
You
have
your
laptop
and
you
want
to
run
this
script
that
go
and
collect
stuff
rain,
and
but
you
can't,
because
your
laptop
is
being
blocked
by
a
firewall
that
separates
your
corporate
land
from
your
production
network,
and
so
you
need
a
way
to
get
into
your
production
network
in
order
to
run
these
scripts
and
what
you're
saying
is
the
net
MRI
is
real,
like
a
jump
point
for
you
for
us
right
now.
B
So
a
good
example
is:
if
our
network
build
script
that
builds
our
data
center
networks.
We
we
until
recently,
which
we've
recently
changed
and
do
some
direct
interaction
with
figure
via
net
comp
right
now
and
we'd
use
PI
easy.
Traditionally
what
we
did
was,
we
would
maybe
sounds
a
little
bit
archaic,
but
we
we
had
this
Python
script.
A
B
Like
it'll
it'll
hit,
imagine
imagine
sending
everything
that
you
need
to
commit
for
all
of
your
equipment
up
into
net
MRI,
and
then
you
say
if
device
matches
this
spit
this
out.
If
it
didn't
match
this,
it
would
just
bypass
it
and
go
to
the
next
thing.
It
wouldn't
even
try
sending
it
because
it
would
it's
the
wrong
thing.
Yep,
where
this
conversation
is
really
kicked
off
now
is
kind
of
when
I
talked
to
earlier,
when
you
have
all
these
silos
that
are
now
trying
to
reach
out
and
talk
to
each
other
right.
B
So
we
are
we're
working
on
a
git
server
so
that
we
can
start
kind
of
versioning
our
code
across
the
across
all
of
our
teams.
That's
a
big
challenge
because
coming
from
a
again
non
developer,
thing
I
feel
like
I,
start
learning
it
and
then
I
stop
using
it
and
then
I
have
to
relearn
how
to
use
git
all
over
again
and
then
find.
A
Ways,
yeah
by
the
way
before
you
I'm,
gonna,
stop
you
there
real
quick.
That
is
the
story
of
ket
there's
so
many
unless
you're
using
it
every
day,
I
don't
know
what
it
is
about,
get
like.
I
have
used
it
on
and
off
my
whole
life.
If
I
don't
use
it
for
three
months.
My
brain
just
like
I,
think
it's
literally
killing
my
get
brain
cells
like
there's
someone's
like
you,
gotta
use,
get
I'm
like.
Oh
my
god,
I,
don't
even
know
how
to
commit
code
anymore,
like
after
three
months,
people
just
freaked.
B
B
A
No
that's
normal.
This
is
normal,
so
you
know
what
you're
describing
is
you
know
in
some
ways
you
know
that
I
think
was:
was
it
Isaac
Newton
he's
the
inventor
of
calculus
right?
Isn't
that
right,
sir?
No?
No!
No!
No!
Okay,
I'm,
pretty
sure!
That's
true
I,
don't
know
if
that's
true
but
I'm,
pretty
sure.
That's
true.
If
it's
not
true,
then
I'm
just
gonna,
say:
Isaac
Newton
invented
calculus
I.
A
Though
I
believe
you're
correct
yes,
so
before
him,
people
just
did
arithmetic
right
in
geometry,
like
you
know,
like
so
many
degrees
angles,
stuff
like
that
and
without
kalki,
can
you
imagine
living
in
a
world
where
you
could
not
interpret
the
world
with
the
help
of
calculus
like
it's?
It's,
unfathomable
and,
and
you
know
what
I
mean
we're
talking
about
something
to
happen
to
hundreds
of
years
ago,
I
mean
there's
new
math.
A
All
all
automation
boils
down
to,
even
if
it's
not
necessarily
a
continuous
closed
loop
and
it
boils
down
to
the
same
pattern.
That's
across
all
industries,
which
is
you
have
this
unit,
it's
a
control
unit,
and
then
you
have
your
process.
In
your
case,
your
process
is
your
network
and
you
and
there's
like
a
loop
in
and
even
if
your
loop
is
broken
and
there's
some
manual
intervention,
one
way
or
the
other
there's
still
a
loop.
That
goes
between
your
control
and
the
network
and
the
count
and
what
automation
is
for
an
organization.
A
Is
it's
the
calculus
of
infrastructure,
meaning
your
organization
has
to
focus
on
control
and
not
your
infrastructure
and
and
that's
that's,
a
huge
leap
for
a
lot
of
organizations.
So
I'll
give
you
an
example.
You
said
what
triggered
this
is
that
you
said
you
don't
want
manage
management
said
they
don't
want
people,
or
maybe
it's
not
ideal,
anyways
to
present
to
management.
You
know,
I
want
to
use
these
20
tools
and
every
every
silo
has
their
own
thing.
A
You
have
to
narrow
it
down
to
a
set
of
tools,
you're
gonna
use
across
organizations
and
the
way
you
bridge
the
gap
between
covering
all
your
needs
and
having
the
right
tools
is
you
have
people
who
focus
on
the
process
of
your
process,
meaning
you
know
you
actually
have
full
time,
automation
or
DevOps
people
who
are
working
on
the
core,
the
core
and
ongoing.
It
never
stops
they're
permanent
part
of
your
group
and
they
never
change
roles.
B
We
as
an
organization,
we
did
something
that
I
really
liked.
So
we
built
this
this
four
person
team.
We
we've
recently
moved
to
some
of
our
development
teams
going
agile
and
we
management
saw
the
need
for
us
to
kind
of
circle
back
to
the.
Why
we
were
doing
this
and
what
we
were
trying
to
do
so
we
pointed
the
sea-ice
they
coined
it.
I
shouldn't
say
we
we
coined
it
the
CI
CD
team,
so
we
have
a
member
from
the
network
team,
the
infrastructure
team,
the
server
hardware,
guys
the
security
team
and
the
development
team.
B
A
So
way,
I
was
actually
part
of
this
survey.
We
just
did,
and
it's
funny
you
mentioned-
that
we're
one
of
the
things
is
and
I
think
this
is
a
reflection
of
the
fact
that
automation
is
still
not
outside
of
Silicon
Valley
like
real.
You
know.
Well,
automated
organizations
are
kind
of
rare
and
I
think
or
I'll
said
it's
at
companies,
especially
technologists.
A
They
were
meaningless
right
and
it's
and
you
want
to
avoid
that
at
all
costs
like
the
threat
of
having
too
many
different
tools
isn't
just
like
you
know
the
I
mean
you
have
all
the
stuffs.
You
predict,
you
know
you
don't
have
people
trained
on
all
the
tools,
so
you
end
up
with
again
people
specializing
and
then
breaking
up
in
tribal
knowledge
and
all
that
stuff.
A
But
one
of
the
one
of
the
issues
is
that
because
you're
not
investing
on
making
the
tools
meaningful
when
it
comes
to
actually
fixing
this
is
the
thing
IT
is
about
fixing
problems.
It's
not
about
building
new
stuff.
You
can
engineer
all
you
want
it's
and
no
matter
how
awesome
you
think
you
are
as
an
engineer
whatever
you
did
is
gonna
blow
up
in
somebody's
face.
A
You
said
that
I
asked
you
very
pointedly
so
as
automation,
something
you're
doing
on
top
of
your
existing
work,
and
you
said
yes,
the
the
next
step
for
you,
er
I.
Think
for
an
organization
like
yours
now
that
you're
having
this
conversation,
you
got
developers
on
the
security
team
stuff.
Is
that
you're
gonna?
You
know
the
next
step
is
you're.
Just
gonna
have
people
who
just
focus
on
this:
that's
a
full-time
job
and
and
now
you're
in
the
calculus
of
your
infrastructure.
If,
then,
if.
B
Tools,
meaningful
yeah,
because
at
some
point
you
we
and
our
company
are
always
gonna
need
network
engineers.
You're
always
gonna
need
the
network
guys
you
always.
You
need
to
telecom
guys
you're
gonna
the
infrastructure,
guys
those
people
are
going
to
exist
in
some
capacity.
It
may
not
be
a
huge
team,
but
there's
they're
going
to
be
there
at
some
capacity.
Somebody.
A
B
It
that
brings
a
really
really
really
good
point
up,
but
anyway
yeah,
so
you
you
need
to
have
somebody
that
has
the
understanding
of
how
this
thing
is
working
before
you
do
this
layering
on
top
of
it,
when
you
start
poking
the
automation
holes
into
it,
to
say:
oh
I'm
gonna.
Do
this
somebody?
That's.
Will
you
even
know
what
you're
doing
nope,
but
this
works?
B
You
know
cuz
what
happens
when
it
breaks
it's
going
to
break
at
some
point
either
it's
gonna
break
because
you
misconfigured
something
and
you
didn't
use
automation,
so
it
wasn't
repeatable,
so
you
put
fat-fingered
something
or
it's
gonna
break
just
because
something
breaks
you
get
a
member
somewhere
somebody
plugged
something
in
the
wrong
place.
Somebody
puts
the
wrong
parameter
into
the
input
of
the
switch
or
something
happens
right.
So
some
it's
going
to
break
at
some
point,
so
you
need
to
have
the
understanding
of
how
did
it
break?
What
was
the
scope
of
the
break?
B
Are
you
getting
the
information
back?
You
know
which
so
some
of
that
kind
of
plays
kind
of
in
a
fun
way
into
what
what
I
have
started
to
learn
as
I
have
started
to
mature
I,
guess
a
little
bit
more
as
a
noob
developer.
So
to
speak
like
when
you
start
writing
code,
it's
one
thing
to
write
code
and
you
just
kind
of
cobbled
together
a
script,
even
if
it's
just
couple
together
at
first
one
thing
to
do
that.
It's
another
thing
to
start
writing
things
that
other
people
are
going
to
use.
B
A
B
A
B
B
Especially
when
you're,
especially
when
what
you're
doing
is
reaching
out
interacting
with
tech
here,
it's
one
thing:
if
it's
logging
in
and
functionally
doing,
some
show
commands
and
spitting
some
specific
information
out.
But
it's
another
thing:
if
you're
you
know,
you're
hitting
the
button
and
you're
logging
into
70
pieces
of
equipment
and
you're
making
configuration
changes
totally
different
animal.
So.
A
B
A
conversation
we've
had
that
I've
had
with
at
least
with
my
direct
managers
that
we
we
as
an
organization
a
we
need
to
kind
of
circulate
this
back
to
the
challenges
and
maybe
kind
of
segues
into
the
last
section,
come
to
talk
about
the
people
that
want
to
do
this.
You
have
to
continue
foster.
They
want
to
do
this.
You
have
to
encourage
them
to
want
to
do
this,
and
you
have
to
be
okay
with
the
failure.
The
failure
that's
gonna
happen,
because
one
of
the
downsides
make
more
socially.
B
That,
when
it
it's
it
can
the
the
blast.
Radius
for
failure
is
much
bigger
than
or
oftentimes
is
much
bigger
than
it
would
be
doing
it
manually.
So
you
need
to
be
okay
with
you
being
the
organization,
not
just
management,
but
even
you
on
your
own
team
when
you're,
when
you
are
when
you
are
thinking
through
how
you're
going
to
automate
something
at
least
we've
done,
this
is
okay.
B
A
A
Network
engineers
do
not
behave
like
engineers,
and
this
is
one
of
the
ways
that
we
as
a
I'm
serious
as
a
profession,
fail
utterly.
We
do
not
systematically
deal
with
failure
very
well
because,
because
we
just
you
know
we
have
someone,
we
can
call
it
just
magically
makes
they
just
wave
their
wine.
Then
it
goes
away,
and
you
can't
do
that.
You
know,
and
one
of
the
things
about
adopting
automation-
and
this
is
again
part
of
the
whole
DevOps
way
of
thinking
is-
is
that
you
you?
A
You
stopped
fostering
golden
children
and
you
start
systematically
dealing
with
failure
and
there's
going
to
be
failure
in
the
beginning.
Whenever
you
do
automation,
it's
there's
it's
and
actually
throughout
right,
just
more
in
the
beginning,
but
then
always
forever.
There's
gonna
be
failure,
just
like
there
is
now
except
the
difference
is
that
you
have
a
systematic
way
of
doing
it
that
doesn't
blame
people
that
doesn't
discourage
them,
that
you
analyze,
what
you
did
you
fix
it.
A
Is
it's
not
good
for
the
golden
child,
I'm
gonna
say
that
that's
the
first
thing
you
gotta
say:
you're,
like
you're,
gonna,
burn
that
person
out
or
drive
them
insane.
It's
not
good
for
everyone
else.
It's
it's
just
bad
and
in
part
of
DevOps,
is
it's
the
process
of
the
process
right
and
this
this
is
part
of
when
I
said
the
calculus
of
infrastructure.
It's
this
is
part
of
managing
the
process
of
the
process
is
dealing
with
failure
systematically.
That's
of,
and
thank
you
for
bringing
that
up.
I
think
that's
super
important.
A
Okay,
we'll
move
on
actually
to
you
said
something
interesting.
You
were
at
junipers
next
work
event
and
you
said,
and
you
said
you
ran
into
somebody-
you
don't
have
to
name
names
or
anything
like
that,
but
they
were
they
were.
Actually.
This
is
such
a
unique
sort
of
situation
where
everyone
knows
they
have
to
do
it,
but
in
the
networking
space
everyone
knows
automation
is
going
to
happen
and
there's
gonna
be.
A
You
know
varying
ways
that
it
evolves,
but
but
one
of
the
things
that's
not
really
well
defined
yet
in
our
industry
and
every
vendor
has
Network
automation.
Training
at
this
point
is
exactly:
how
do
you
train
someone
to
be
a
Network
automation
person
in
the
field,
because
everyone's
multi-vendor
and
and
everyone's
environment
is
different.
So
what
do
they
need
to
know?
And
now?
How
do
they
make
it
happen?
And
so
tell
us
that
you've
met
somebody
and
they
had
an
interesting
story
so
yeah
one
of.
B
B
Quasi,
just
straight
up
almost
developer
training,
one
of
the
things
that
this
gentleman
said
they
did
for
their
network
engineers
as
they
went
to
a
local
college
and
they
said:
hey.
We've
got
a
bunch
of
people
here
who
were
trying
to
get
this
knowledge
base
under
get
them
up
to
speed
on
how
to
do
this,
so
they
took
him
through.
They
work
the
this
local
school
to
develop
kind
of
a
developer
bootcamp
so
that
everybody
was
on
the
same
page
and
I.
B
It's
one
thing
for
us
in
our
group
to
say:
oh,
we
wrote
this
Python
code
and
this
is
kind
of
cool,
and
this
interact
with
it.
Oh
and
hey
infrastructure
guys
we
used
our
read-only
vCenter
access
to
kind
of
pull
some
stuff
from
your
VMware
environment.
To
help
us
configure
this
thing
right,
that's,
okay,
that's
great
and
maybe
another
person,
then
that
team
could
look
at
our
code
and
kind
of
see.
Oh
yeah
see
how
you
did
that.
That's
that's
cool
right!
B
If
I
say,
we
could
use
a
function?
Do
they
know
what
we
mean
like
all
these
there's
this?
This
is
general
level
of
I
feel
like
that
developers,
kind
of
have
that
we
don't
have
in
generally
speaking
in
our
traditional
textile
O's.
Networking
infrastructure
servers.
All
of
that
so
I
I
don't
profess
to
know
what
the
answer
is
to
that.
But
I
feel
and
I've
said
this
before
to
a
couple
guys
at
work.
B
I
feel
as
though,
if
we
went
to
we
have
all
of
these
hooks
to
local
schools
right
because
we
hire
a
lot
of
developers.
We
have
all
these
folks,
these
local
colleges,
these
professors
and
these
teachers
that
are
there
I
feel
like.
If
we
went
to
them
and
said
look,
we
got
a
whole
bunch
of
really
talented
engineers
who
are
kind
of
going
down
the
development
road,
no
they're,
not
full-on
application
developers,
but
what
would
be
some
good
base
level
knowledge
that
we
could
give
to
all
of
them?
B
I
feel
like
they
could
come
up
with
something,
because
at
some
point,
there's
gonna
have
to
be
I
feel
like
there's.
Gonna
have
to
be
some
formals,
some
sort
of
formal
training
for
us,
maybe
not,
but
I,
don't
know
how
we're
think
it
would
accelerate
the
process
of
getting
there
if
we
had
some
form
of
that
form.
A
training
yeah.
A
A
But
you
know,
as
you
know,
every
vendor
has
automation,
training
and
every
every
single
one
that
we
just
did
a
whole
Podcast
fit
cast
or
whatever
this
is
called
now
we
did
a
hole.
We
did
a
hole,
one
up
on
this
and
a
blog
post
and
they
all
have
training
and
certification.
So,
but
there
is
something
about
it.
I
mean
it's
I'm,
not
saying
it's
not
useful.
It
is.
A
It's
super
useful,
actually,
some
of
this
training,
but
it's
it's
not
it's
not
enough
to
get
you
off
the
ground
or
something
like
it's
not
enough
to
have
you
be,
have
you
think
about
the
whole
picture
and
and
so
at
that
I've
always
felt
that
way.
So
to
hear
you
say
that
you
know
this
has
been
so
important
to
you
and
there's
such
a
lack
of
of
whatever
we
need
for
for
someone
in
your
org
or
for
this
person.
A
B
A
B
The
basically,
though
his
his
bit
about
that,
where
he
talked
about
that,
and
then
there
was
another
one
I
know
there
was
another
one
that
talked
about
this
idea
of
the
organizational
paradigm
shift
they
kind
of
they
I
took
both
of
those
as
super
important,
they're,
not
mutually
exclusive
by
any
stretch,
but
those
are
two
big
takeaways,
like
I
tried
taking
back
to
the
organization
to
our
to
our
management,
be
like
look.
This
is
what
we
need
to
be
doing
because
maybe
not
to
go
to
nuclear
here
with
this,
but.
B
I've
told
I've
talked
to
a
couple:
I've
gone
back
at
the
tech
school
that
I
went
to
it
gives
them
like.
So
just
give
a
little
talk
to
the
graduating
class
they're,
the
one
of
my
one
of
the
instructors
there
had
he
kind
of
brings
in
industry
able
to
kind
of
give
a
gonna
give
these
students.
This
is
what
the
real
world
like
like
your
school,
but
this
is
kind
of
what
the
real
world
is
like
right
and
one
of
the
things
that
I
started.
B
But
it's
quickly
getting
to
that
point
where,
if
you
don't
know
what
that
is
that
you've
never
done
it,
you're,
probably
not
going
to
be
a
top
pick
for
that
for
that
role,
especially
for
a
senior
for
a
senior
level
position,
so
you
either
have
to
as
an
organization
foster
that
or
at
the
what's.
Even
worse,
is
it's
two
prong
your
organization's
not
going
to
benefit
from
from
what
automation
can
give
you
and
you're
going
to
start
losing
talent,
because
people
are
gonna
be
like
look
if
I
want
my
job
to
be?
A
B
Yeah,
so
I
got
I
got
lucky
in
that
this,
like
I,
think
like
I
mentioned,
we
I
have
a
new,
a
new
engineer,
starting
in
a
couple
weeks,
and
he
was
an
intern
and
he
kind
of
he
showed
the
aptitudes
there
for
these
things,
not
only
for
networking
but
for
a
lot
of
these
scripting
things,
so
I
kind
of
fell
into
that
got
lucky
there.
If
I
were
hiring
for
a
new
position,
I
would
absolutely
require
a
senior
position
to
have
some
form
of
automation,
API
Python
experience.
B
It
doesn't
need
to
be
extensive,
but
it
would
be
difficult
for
me
to
bring
somebody
on
the
team
at
a
senior
level
that
didn't
know
that
now
there's
caveats
there
I'm
not
saying
that
not
having
it
would
be
completely
a
disqualifying
thing
depending
on
the
individual,
but
it
would
be
if
I
have
to
close
candidates
from
a
pure
networking's
knowledge,
and
one
of
them
has
API
knowledge
of
one
of
them
doesn't
or
scripting
knowledge
of
one
of
them
does
it.
You
can
bet
that
I'm
gonna
be
going
with
the
one
with
knowledge
when.
B
It
it
really
happened.
Probably
within
the
past
I
mean
shortly
within
the
past
couple
of
years,
and
it's
so
when
we,
when
we
got
into
where
we're
at
and
the
company
were
at
and
then
after
I
came
on
shortly
after
I
brought
my
buddy
Chris
on
shortly
after
getting
on,
we
started
kind
of
dabbling
in
this
automation.
B
It's
kind
of
been
both
I
feel
like
one
seeing
the
benefit,
that's
there
and
then
who
maybe
maybe
I
had
just
had
been
blind
to
it,
but
I
feel
like
in
the
past
few
years,
it's
gotten
even
bigger,
now
I
know
that
I've
seen
posts
of
network
engineers
doing
things
with
Python
for
years.
So
it's
not
like
Network
people
doing
Python
is
brand
new,
but
I
feel
like
in
the
past
few
years.
B
It's
really
taken
off,
so
I
could
be
wrong
there,
but
I
seen
it,
especially
in
the
circles
of
like
my
direct
peers
and
networking.
Five
years
ago
we
weren't
talking
about
Python
or
scripting
or
automating
anything.
Now,
some
of
the
guys
that
I
used
to
work
with
at
my
previous
company
are
like
dude.
Are
we
thinking
fight
we
should
have
been.
We
should
have
been
learning
this
stuff
five
six
years
ago.
Oh
I,
don't
know
why,
but
it
just
wasn't
there.
It
wasn't
a
thing.
A
Okay,
so
I
ask
one
more
question,
then
we'll
call
quits,
because
it's
been
an
hour.
What
do
you
wish?
You
knew
at
the
outstart
of
this
of
this
whole
automation
thing
for
you
or
had
what
do
you
wish?
What
do
you
wish
could
have
been
a
thing,
whether
it's
something
you
knew
or
some
training
you
had
or
some
access
you
had
to
some
tooling
I,
don't
know
whatever
like?
What
do
you
wish
was
a
thing
at
the
start
of
this
process.
B
Again
this
this
could
be
partially
because
of
my
relative
infancy
in
it.
I
didn't
I,
don't
remember,
hearing
vendors
talking
about
this
this
at
all
five-six
years
ago
at
least
the
vendors
we
were
like
we
were
a
Cisco
shop,
I,
don't
remember
once
hearing
about
Python
or
doing
anything
with
that
we
did
some
simple
bash
scripting
of
certain
things,
but
that
was
that
wasn't
really
interacting
with
any
gear
that
was
more
cycling
through
information,
so
I,
don't
think,
there's
a
there's,
a
tool
that
I
wish
I
would
have
had,
or
anything
I
just
wish.
B
Having
if
you
have
enterprise
networking
experience,
especially
where
you're
at
now,
but
not
you,
especially
where
we
are
at
now,
both
organizationally,
where
I'm
working
as
well
as
I,
feel
like
we're
industry
kind
of
is
right
now,
I
feel
like
that's
the
best
of
both
worlds,
at
least
from,
and
it
doesn't
have
just
be
networking
you
can
be
a
an
infrastructure
VM.
You
know
engineer
you
could
be
whatever
it
may
be.
B
If
you
have
that
and
then
you
have
traditional
like
you
have
that,
and
then
you
have
some
traditional
training
in
actual
software
development
like
that
would
be
golden
right
now,
so
I
almost
wish
I
would
have
known
about
this
sooner.
It's
not
that
I
can't
go
back
and
get
training
now,
but
it's
I
feel
like
I'm
catching
up
more
than
I
am
in
front
of
it.
I
guess
I
would
say.
A
I'll
tell
you
something
I
kind
of
wish:
there's
certain
things
we
do
as
network
engineers,
we're
expected
to
know.
I'll.
Give
you
some
examples.
I'll
give
you
two
examples.
One
is
first
sort
of
basic
the
whole
idea
of
some
I'll.
Give
you
one
very
basic
example,
and
it's
the
idea
of
subnet
masks
and
subnetting,
and
what
one
thing
that
always
kind
of
drive
drove
me
nuts
was
that
there
wasn't
like
a
standard,
well-known
set
of
tools
like
like
in
Linux.
A
That
tool
should
have
already
existed
for,
because
we've
been
expected
to
do
these
things
since
the
beginning
of
time,
like
here's,
a
list
of
subnets
summarized
them
right,
I,
don't
understand
why
I
had
to
do
that
by
hand
ever
at
any
point
or
why
I
was
ever
tested
on
it.
You
know
I,
don't
I,
don't
get
that
there
should
have
been
a
tool
built
into
Linux
or
built
into
Cisco,
IOS
or
Juno's,
or
something
where
I
could
just
okay.
B
A
And
I
don't
understand
why
it's
not
just
that
there's
a
whole
bunch
of
things
like
that
that
just
have
always
driven
me
crazy,
like
when
you
do
a
show
MAC
address
on
a
switch.
How
come
not
now
this
should
have
happened
a
decade
ago.
How
come
when
I
do
a
show
MAC
address?
Why
do
I
have
to
guess
what
that
vendor
is?
Why
do
I
have
to
go
and
sort
of?
A
You
can
do
a
search
and
it'll
tell
you
this
is
the
vendor
I,
don't
understand
why
that's
not
automatically
built
into
every
single
networking
thing,
because
that's
useful
who
it
you
know
who
is
or
whatever
you
know,
though,
who
is
IP
or
whatever
that
all
that
stuff
great
I
like
those
kind
of
things
right,
and
then
there
was
the
second
thing
and
I
forgot
where
I
was
going.
Okay,
I
can
make
a
list
of
these
things
right,
we're
sure,
I
kind
of.
A
B
A
B
B
A
Okay,
so
if
you're
watching
thank
you
for
for
sticking
around
so
long,
this
went
longer
than
usual
and
we're
gonna
have
Mike
back
out
again
for
sure
I
guarantee
it
I
think.
Maybe
we
might
do
it
in
a
pub
next
time.
If
I
can
convince
the
powers-that-be,
meaning
my
milady,
let
me
buy
a
camera
for
a
tripod,
so
I
can
record
us
a
low-light
that'd,
be
awesome.
So
again,
thanks
for
watching
I
hope,
I
hope
this
is
being
a
great
show
for
you.
A
B
A
Please
give
him
a
follow
and
I
think
we'll
be
hearing
more
great
stuff
from
Mike
again.
Thank
you
very
much
and
hey.
If
you
want
to
learn
about
Network
automation
and
you're,
just
starting
out
are
the
goal
of
NRI
Labs
is
that
you
know
we
can
help
network
engineers
with
the
with
with
getting
off
the
ground,
and
please
visit
us
at
an
energy
labs,
dot
IO.
Actually,
let
me
verify
that
real
quick.
We
just
changed
our
our
URL.
A
You
know
I'm
typing
stuff.
Is
there
as
we're
signing
off
nope?
It's
still
the
old
URL.
We
haven't
switched
it
yet,
but
it
will
be
switched
soon.
It's
still
labs
dot,
network,
reliability,
dot,
engineering
and
you
can
go
there.
There's
there's
no
marketing
wall.
You
can
just
immediately
launch
into
a
lesson
and
start
learning
stuff,
so
so
go
check
it
out
and
and
a
get
down
this
path
of
learning.