►
Description
PowerShell Saturday is a training event for all things PowerShell. The event was held in Raleigh, North Carolina and hosted by Research Triangle PowerShell User Group.
In this session Dave Carroll explores the question What is DevOps and explains his belief that he is now a "PowerShell Developer" instead of a System Admin.
This is a great presentation to help you understand the huge technological shift that is DevOps.
The files for Dave's slides and code can be found on our github page:
https://github.com/rtpsug/PowerShell-Saturday/tree/master/2019-NC.State/
A
So
before
we
begin,
I
want
to
say
that
partial
Kennedy
couldn't
happen
without
people
like
you
and
also
couldn't
happen
without
the
sponsors
like
systems,
frontier,
chocolatey,
Texas
from
4,000
script,
mother
they're,
the
leaders
in
the
industry-
and
they
want
to
make
your
technical
lives
easier,
I'm,
making
work,
smarter
and
helping
the
work
smarter
and
be
smart.
Please
check
out
their
boots
when
you
have
some
time
so.
A
Of
what
we
get
the
really
cool
stuff,
you
know
this
is
sort
of
my
path
and
getting
into
DevOps
spoiler
I'm,
not
exactly
there
yet.
But
one
of
the
things
that
has
changed
is
then
my
mindset
and
that's
from
primarily
but
this
what
this
presentation
is
about.
It's
about
the
shift
in
mindset
and
it's
kind
of
considered.
This
is
a
DevOps
primer.
A
I
I
I
started
tight,
but
I've
been
doing
this
a
long
time
and
when
I
first
found
out
that
I
really
like
technology
I,
was
typing
a
balloon
game
that
was
written
in
c6
before
basic
out
of
a
magazine
into
my
Commodore
I
knew
that
technology
would
be
a
sin
with
a
car.
My
life
said
the
c64
later
Apple
to
see
that
is
a
multi-speed
laptop
when
I
was
a
college
computer
lab
assistant.
A
Therefore,
for
a
couple
of
semesters
and
the
transition
from
small
town
to
the
College
in
Toledo,
as
leaders
and
I
dropped
down
after
we
shot
a
couple
of
scholarship,
so
yeah
fast
food
has
to
be
jumps
in
that
and
then,
when
I
got
totaled
everyday
stress,
I
decided
to
look
for
a
job
and
computer
I
didn't
realize.
There
was
also
stress
there.
A
My
first
real
real
computer
job
was
working
on
a
small
mom-and-pop
computer
store.
We
prepared
and
sold
pcs.
We
set
up
servers,
installed,
networks,
I,
didn't
the
first
buffing
out
the
fiber-optic,
and
all
that
way
we
did
like
the
whole
whole
shebang.
I
get
my
personal
I
was
there,
and
also
this
was
during
the
time
when
he
had
to
download
the
drivers
from
BDS
and
a
bunch
of
other
stuff
too.
There's
also
the
first
time
I
ever
saw
software
development
firsthand.
A
We,
when
I
decided
to
move
back
to
Tennessee
and
then
I
work
for
medical
gas
company,
now
work
for
a
global
bank
notes.
The
positions
are
more
multiple
apps,
so
I
was
I.
First
started
out,
though
mostly
best
helpdesk,
stuff
at
Community
College,
that
was
the
service
engineer.
Service
manager
had
several
people
over
42,
then
I
moved
from
that
transition
into
webmasters
and
then
throughout
all
of
this
time,
I
was
still
kind
of
doing
server,
stuff
and
then
I
started
doing
server
stuff
on
the
been
doing
that
for
over
half
at
some
time.
A
Someone
out
there
and
I
had
a
front
end
for
Linux
Apache
PHP,
where
students
and
support
staff
did
support
to
have
to
go
in
put
in
the
user
and
synchronize
to
make
sure
that
that
user,
all
the
data
was
up-to-date
and
all
of
the
systems,
all
the
back
things
or
something.
So,
basically,
if
I
had
to,
if
something
need
to
be
done,
I
learn
how
to
do
it
and
then
I'll
get
it.
I
became
a
jack-of-all-trades,
widely
skilled
in,
like
general
technologies
and
TVs.
A
So
for
over
half
my
career,
like
I,
said
I,
call
myself
a
systems
engineer
or
administrator
but
beginning
this
year,
a
certain
elements
of
a
powerful
developer,
because
it's
really
what
I
am
I
build
things
so
with
the
show
of
hands.
How
do
you
label
yourself?
Who
here,
considers
himself
systems
administrator
or
systems
engineer.
A
A
A
A
So
DevOps
is
a
framework.
It's
a
set
of
practices
and
principles
that
focuses
on
the
rapid
release
of
applications
and
production
and
the
carrot
feeding
of
those
applications
from
throughout
their
lifecycle.
It's
about
having
the
necessary
skills
to
do
all
that
within
either
one
team
or
very
good
collaboration
between
that.
A
A
Let's
talk
a
little
bit
about
originally
had
no
idea
otherwise,
up
until
a
couple
years
ago,
I
mean
it
wasn't
even
on
my
radar,
when
I
moved
back
to
Tennessee
a
lot
of
open
jobs,
mission,
DevOps
and
more
so
even
the
last
year,
when
I
started
looking
for
any
job
to
leave
politics
because
I
at
the
time
I
wanted
to
focus
on
you
know,
directory
and
one
of
the
focus
on
any
management.
Of
course,
PowerShell
then
sort
of
blogging
on
the
PowerShell
and
I
became
I
have
acted
in
the
online
community.
A
I
realized
that
DevOps
was
something
that
you
need
to
learn
about
and
I
shouldn't
just
disregard.
It
I
had
the
pleasure
of
attending
the
local
dev
updates
in
Nashville
this
year,
and
the
technology
was
one
thing
it
was,
you
know
impressive,
but
the
one.
The
other
thing
that
I
really
liked
was
the
openness
and
impermanence
of
the
people,
the
attendees
and
presenters
I'm
sure
most
everyone.
There
were
intimate,
but
they
were
talking
music.
A
So
the
2008
idled
conference
in
Toronto
is
actually
where
Andrew
Schaeffer
hello,
the
birds
of
a
feather
session,
and
there
was
only
one
person
that
came
up
to
it
and
it
was
a
package
of
law.
He's
I,
picked
applause,
a
Belgium
consultant,
and
he
has
been
frustrated
with
the
the
wall
of
confusions.
What
separated
Devin
off
then
at
the
2009,
a
rally
conference,
Paul,
Hammond
and
Davos
bomb
he
gave
a
presentation
has
become
famous.
A
It
was
ten
plus
the
place
where
they
Devon
opted
cooperation
and
flickered
and
the
blog
couldn't
attend,
but
he
was
able
to
stream
the
session
and
he
was
inspired
so
he
actually
coined
the
term
DevOps
whenever
he
was
organizing
the
first
a
table
states
and
get
Belgium
in
2000
I.
Now
the
theme
that's
really
telling
is
that
several
people
across
the
globe
were
coming
to
the
same
realization,
something
that
was
a
better
way
to
do
things.
A
The
status
quo
wasn't
going
to
get
them
for
the
next
level
and
to
me,
a
man
that
face
to
face,
but
reality
most
of
them
communicated
either
through.
Through
blog,
you
know
their
own
blogs
or
through
social
media,
and
they
gave
each
other
confidence
that
developers
and
sysadmin
could
actually
work
side
by
side
without
killing
each
other.
A
So
who
suggested
that
I
read
the
Phoenix
project,
but
it's
a
it's
a
fictional
narrative
that
has
it
that
uses
a
Socratic
method.
So,
like
this,
this
teacher,
this
mentor
that
that
the
protagonist
keeps
going
back
to
and
it's
actually
helped
changed
my
mind
and
it
was
when
I
guessed
read
that
book.
It
was
really
the
turning
point
when
I
realized,
you
know
I'm,
definitely
not
a
systems,
admin,
something
different,
and
it's
what
the
really
need
that
aha
moment
to
the
transition
into
a
DevOps.
You
know
full
of
they're,
not
soldiers.
A
So
how
many
times
have
you
heard
something
like
this
developers?
Don't
care
about
security?
Those
systems
seem
they're
roadblock.
They
were
supposed
to
have
the
VM
built
a
month
ago,
we'll
never
get
to
zero
downtime
deployments
endless
of
lost
their
minds.
So
every
one
of
these
statements
causes
visceral
reactions
with
developers
and
engineers
systems
admins
alike,
but
in
the
beginning
there
was
no
real
separation
between
developers
and
the
like,
especially
on
the
UNIX
systems.
You
had
to
be
a
programmer
because
you
had
to
compile
the
application.
A
If
you
want
to
be,
then,
as
the
os's
evolved
as
programming
language,
a
languages
evolved,
the
more
the
duties
started
diverging
and
then
you
have
eventually
the
dev
versus
odds
or
the
horses
win,
and
then
that's
the
status
quo
for
four
decades
until
Patrick
and
John
all
fought
and
another
that
realized
that
it
shouldn't
be
this
way
so
like
whenever
developer
needs
something
from
the
system
team,
they
would
typically
throw
it
over
the
wall
and
said:
hey.
You
know,
ETA's
had
no
idea
what
it
did
that
conduct.
A
Then
you
know
likewise.
Whenever
the
systems
team
leaders
something
of
the
developers,
they
would
throw
it
over
the
wall.
So
this
enters
a
bird
called
this
barrier,
the
wall
of
confusion
and
is
actually
one
of
the
from
the
people
and
the
biggest
challenge.
For
me
that
I
think
I
said
it's
been
the
shift
in
myself.
You
know
going
from
the
SIS
system
and
mine
said
to
something
that
that's
not
necessarily
sis
that
man
and
that's
a
fairly
developer.
A
Jean
Kim
is
one
of
the
co-authors
of
the
Phoenix
project
and
several
other
devops
boaters,
and
he
developed
the
freeways
so
the
first
way
system
spending-
and
he
doesn't
mean
you
know
the
servers
that
the
running
on
he
means
the
complete
systems
like
from
design
phase.
All
the
way
to
you
know:
maintenance
of
the
application
or
whatever
the
second
way
is.
We
identified
the
feedback
we
so
each
step
of
the
way.
The
idea
is
you,
don't
you
don't
send
anything
upstream
unless
it's
the
highest
quality
and
what
you
want
and
its
past?
A
A
A
A
A
Is
you
start
with
a
small
team
and
you
have
one
goal,
whether
it's
a
product
or
an
application
or
service
or
whatever
or
a
feature
of
the
small
team,
one
goal
so
before
before
DevOps?
You
would
have
a
project
team,
you
had
company,
but
hire
people,
or
you
know
bring
vendors
in,
they
would
develop
it,
they
would
customize
it.
A
A
It
basically
says
that
a
team,
the
most
optimum
size
for
a
team
as
someone
as
the
team
that
can
be
fed
by
cookies
and
that
could
very
special
in
yourself,
but
typically
it's
about
eight
people,
so
your
team
has
about
eight
people
and
working
on
one
product.
You
know
you've
done
your
ironically
I
learned
about
teamwork
from
working
at
a
pizza
place.
You
know
we
put
the
customer
first
and
then
working
in
the
small
IT
teams.
We
also
had
a
single
folk
that
Senate
was
the
end
music.
A
A
A
A
Once
you
have
the
mindset
change
the
people
change,
then
you
can
start
changing
your
processes
and
no
matter
what
the
vendor
says,
you
can't
go
and
buy
that
off.
Devops
is
not
a
tool,
a
lot
of
people
they,
you
know
they
think
you
can
buy
DevOps,
but
your
culture
has
to
support.
You
know
the
new
methodologies.
Now
that
doesn't
mean
that
a
tool
can
help
solidify
that
laughs.
I
mean
you
have
to
have
the
tools
in
order
to
do
what
you
need
with.
A
A
You
know,
15
video
scripts,
to
build
out
your
environments
or
to
compile
things.
You
have
agile
infrastructure
that
just
in
time,
and
then
you
have
something
that
within
figured
the
things
that
you
just
stood
up.
You
would
have
the
testing
and
all
of
that
it's
really
controlled
or
encapsulated
in
the
CIC
b-59
and
there's
a
per
minutes
amount
of
tools
that
can
help
with
automation,
and
it
seems
like
every
day,
there's
just
more
and
more
that's
popping
out.
So,
let's
pump
source
control.
A
So
it's
good
do
so
to
put
the
ones
that
don't
use
source
control,
yeah
filenames,
let
that
maybe
end
and
repeat
to
you
or
v3
or
dates
and
times
for
something
like
that.
How
can
you
revert
those
version
like
if
you,
you
know,
make
a
new
change
and
it
doesn't
work?
How
can
you
revert
goes
back
to
something
that's
known,
but
you
know
good.
You
have
to
look
through
all
of
the
heat
1
B
2,
B,
3
or
whatever,
or
maybe
some
is
something
to
main
a
programmer.
A
A
It's
be
centralized
repository,
there's
a
version
which
is
centralized
repository,
so
you
can
I
think
what
that
can
be
granular
with
which
key
members
you
can
in
grant
access
to
modify
certain
pieces
of
a
certain
components,
level
and
then
the
third
one
which
haven't
actually
seen
in
a
while.
There
is
material.
A
A
So
you
know
we
got
the
github
get
lab
bitbucket
all
these
without
the
big
ones,
I've
actually
used
it
up
get
loud
and
just
play
it
around
a
little
bit
with
a
DevOps.
We
buddies
and
I've
got
my
personal
website,
and
you
know
so
I'm
not
tried
to
go
to
Google
cloud
for
people
I
found
out
about
it
in
prepping.
For
this
from
the
baby,
so
the
next
thing
you
can't
really
be
automation
without
spitting,
and
this
is
where
obviously
PowerShell
comes.
You
know
we
can
bring
to
the
brawl
full
bore.
A
It's
one
of
the
biggest
players
and
then,
of
course
outside
of
the
winners
world.
There
are
other
planets
like
pipeline.
Go
Andrew,
though,
is
short
for
going
and
DevOps.
You
really
need
to
be
proficient,
and
at
least
two
of
these
think
PowerShell,
don't
tell
the
organizers,
I,
don't
think
our
show
is
going
to
get
you
all
the
way
to
where
you
need
to
be.
A
We
have
a
parcel
commandments
that
can
easily
convert
to
them
from
or
export
from
import
and
those
types
and
then
in
CI
pipelines
the
integration
pipe
one.
You
see
a
lot
of
me
animal
pursuits
that
animal
was
yet
another
market
look,
and
it's
just
basically
like
space
indentation,
specific
things
like
that
will
give
a
little
more
into
that
later.
A
That's
what
you
have
networks,
or
servers
or
storage,
and
your
security
all
tightly
provisioned
together,
where
you
can
scale
up
or
down
the
pipe.
A
lot
of
like
that
was
one
God
worked
with
yeah.
We
talked
about
the
slider
and
he
hated
the
slider,
because
developers
said
the
slide
was
great
and
he,
as
the
VMware
architect,
hated
the
slider,
because
you
had
no
idea
on
how
to
plan
for
resources.
A
A
Containers
containers
is
like
the
VM
accepted.
It's
highly
focused
on
one
particular
thing
and
anything:
that's
in
the
VM.
You
know
it
basically
just
does
the
wrong
processing
anything
and
you
can
spin
it
up,
use
it
and
then
discarded
without
you
know,
without
worrying
about
it
or
morning
as
well,
and
you
have
the
dr.
A
vagrant
and
the
redhead
over
there
and
then
so
once
you
have
all
of
these
individual
small
Miriam's
running
these
containers
you'd
have
some
way
to
to
push
the
workload
between
them
and
that's
where
the
focus
tration
engines
come
into
play
like
the
kubernetes
or
dr.
storm
I.
Think
urban
Eddie's
is
sort
of
VHS
and
Betamax.
A
So
the
next
thing,
like
I,
said
before
the
quick
feedback
for
dot
to
amplify
the
feedback.
Whenever
you
send
something
up,
you
have
to
test
it
before
it
goes
on
for
the
next
things.
Basically,
instead
of
being
manually
controlled,
you
control
whether
something
moves
forward
using
tests
and
there's
different
types
of
tests
that
you
can
do.
A
You
have
unit
tests,
integration
tests,
system
tests
or
acceptance,
trust
now
the
exception
test
might
be
still
mostly
human
based,
but
these
others
are
our
script
base.
For
you
know,
whatever
testing
mechanism
you
can
use
with
PowerShell
is
of
course
pestered.
You
can.
You
know,
write
unit
tests,
integration
tests
and
it
means
existence
has
festered,
and
you
can
also
use
the
PS
Script
analyzer,
which
can
make
sure
that
your
code
looks
like
it
needs
to
look
like
it
supports
best
practice.
A
A
So
you're
the
the
lint
linters
that
I
put
up
there.
Basically
his
pedometer
it'll
enter
or
for
PowerShell,
but
any
lint
or,
like
I,
think
these
Microsoft
bells,
which
was
a
lending
or
grandma
we
can
use
any
lint
or
that
checks
to
see
if
the
code
is
is
right,
but
you
can
make
sure
that
there's
not
any
back,
ticks
or
check
to
make
sure
that
you
don't
have
you
no
longer
line
with
and
like
80
characters
away.
A
So
once
you
know
within
the
automation,
then
we
have
the
CI
CD
pipeline
and
involves
usually
taking
in
code.
So
you
take
in
the
food
and
then
it
does
an
auto
trigger
and
it
gets
pushed
throughout
the
mix
next
step
next
step
and
if
any
point
it
fails,
you
know
it'll
get
it
back
and
you
have
to
kind
of
start
all
over
them.
A
Deployment
actually
takes
those
releases
and
then
put
them
into
the
press
environment
or
into
a
production
environment
and
there's
several
CITV
products
available,
there's
Jenkins,
which
is
open
source
and
it's
like
lively,
most
widely-used
Travis
CI
teamcity
than
highest
rate
DevOps
and
epilator
they're,
the
ones
that
actually
these
most
of
these
have
like
argues
with
monies
containers.
These
two
is
less
about,
as
you
gave
out
and
hunt
player
can
use
like
the
windows
or
Visual
Studio
template
to
build
out.
So
you
see
a
lot
of
powerful
modules.
They
typically
I've
seen
the
news
out
there.
A
They
might
be
using
something
else,
and
then
they
just
added
github
actions
and
still
in
beta,
but
I
think
you
can
pretty
much
get
enjoyed.
If
you
want
to
do
and
then
the
aw
is
code,
go
to
make
it
BS
code
pipeline,
I
haven't
actually
gotten
into
those
yet
but
I'm
playing
around
with
them.
Trying
to
play
around
with
and
I
don't
know
what
the
difference
is
between
disease.
A
By
feeling
again,
the
fully
automated
CICE
pipeline
is
really
the
goal
of
automation.
It
reminds
you
provide
the
past
this
way
and
codes
release
to
the
fun.
So
the
we've
talked
about
the
CNA.
Now
we're
gonna
talk
about
the
L.
The
L
is
the
front,
largely
well
the
elders
lean.
This
comes
from
the
Toyota
Production
system,
GPS,
so
TPS
reports.
A
Then
the
whole
point
of
ApS
is
your
respect.
You
have
respect
for
the
people
and
you
have
to
make
all
the
work
visible
originally
had
an
idea
of
putting
a
Kanban
board
up
here
and
then
moving
things
across,
but
time
crunch
life,
and
that
didn't
happen.
So
any
case
we'll
show
you
well
something
here.
It's
about
about
what
a
Kanban
board
is
so
calm
on
board
is
it's
where
you
can
quote
all
the
tasks
you
have
to
do.
A
You
have
to
codify
every
task,
identify
every
task
and
you
put
them
up
and
then
and
the
DevOps
world.
Ideally,
you
would
have
multiple
people
on
the
team
that
could
just
grab
what
they
need,
so
they
they
hold
the
work
to
them.
Work
is
not
wish
to
them.
That's
also
a
huge,
significant
difference
between
DevOps
and
pretty
much
the
way
we've
been
doing
things.
A
Then
you
also
do
everything
in
small
batches.
So
like
what
Silber
said
do
things
in
small
batches?
You
don't
want
to
have
so
that
you'd
be
doing
a
release.
You
want
to
do
a
release
on
a
particular
piece
of
it.
You
don't
want
to
wait
until
you
have
every
part
of
the
of
the
application
done
so
I
think
I
think
the
tentative
release
the
the
most
viable
or
the
least
viable
product,
and
then
you
kind
of
build
up
through
there.
A
Then
you
also
have
to
manage
appealing.
So,
let's
say
typically
in
a
Kanban
board,
you
would
have
like
three
columns.
One
is
things
to
do.
The
next
one
is
things
that
you're
working
on
and
then
third
one
is
things
that's
been
done.
We
can
get
maybe
a
couple
more
local
defeat
or
sideways,
but
the
key
links
is
like.
If
you,
if
you
have
say
18
members,
you
want
that
key
length
and
that
are
the
things
that
you're
working
on
really
to
be
eight
or
five
or
something
like
that.
A
A
A
It's
all
about
continuous
improvement
from
from
every
every
part,
so
metrics
I'm,
going
to
just
flop.
Through
some
of
these,
you
need
to
measure
all
the
things
you
know
usage
things
like
that
need
to
bring
visibility
to
this
into
the
systems.
Typically,
this
is
done
with
application
performance
monitoring,
some
comes
from
Tracy,
and
it
also
includes
volcano
legs
and
management.
A
So
the
final
part
of
the
conferring
mark
is
sharing.
You
share
your
knowledge
and
you
share
your
journey.
You
don't
have
to
be
the
foremost
authority
on
the
topic.
There's
always
going
to
be
someone
that
knows
less
than
you
and
is
always
going
to
be
someone
who
knows
more
me
always
I
mean
I'm,
not
I.
Don't
consider
myself,
foremost
authority
on
DevOps
I
mean
I'm
trying
to
get
to
DevOps.
But
again
the
mindset
is
the
thing
that
makes
me
think
I
can
help.
A
So
one
of
the
things,
if
you
haven't
heard
of
markdown,
if
you
haven't
heard
of
markdown,
you
should
really
get
into
that.
It's
it's
a
text-based
file
that
you
basically
have
indicators
that
can
been
applied
headings,
emphases,
tables
things
like
that.
There's
different
flavors
mark,
you
know
github
as
it's
our
own
flame
pub
has
its
own,
and
you
can
also
use
partial
Platypus
module
to
turn
markdown
into
our
shell
external
help
and
simply
having
the
documentation.
Sorry,.
A
Simply
handling
documentation
is
not
enough.
You
need
to
have
it
in
a
consistent
location
and
it
needs
to
be
properly
version
presentations
another
way
to
share.
Sometimes
if
you
have
enough
time,
we
can
make
sure
your
presentation
goes
easier
than
this
and
then
also
blogging.
So
I
started
blogging
last
year
and
you
know
I
don't
have
a
lot
of
content,
but
but
I'm
working
on
that
and
then
meetups
and
lightning
sessions
and
birds
of
a
feather
that
those
are
ways
that
you
can
share
information
with
others.
A
A
The
west
from
the
topology
is
based
on
I.
Didn't
work
either
like
it
with
the
books
to
see,
has
the
three
primary
the
three
coastal
models
the
pathologic
build
your
product.
We
generated
the
the
best
way,
which
I
think
is
final-
is
the
generative
performance
oriented
and
focuses
on
the
mission
in
the
goal
and
I
encourage
innovation.
The
risk
was
shared.
Is
the
devops
family
one
feel
like
a
pathological?
That's
where
you
know,
there's
not
an
option.
A
You
get
and
get
it
written
up
for
villain,
just
a
small
office
of
things
bureaucratic
and
protects
the
department's,
and
it's
still
it's
better
than
pathological.
But
it's
not
unfair.
So
I,
you
know
check
out
the
westrom
topology
kind
of
see
the
different
differences
between
the
G
definitively
the
bureaucratic
is
ruled
I'm
going
to
get
into
some
the
key
findings
of
the
DevOps
research
and
assessment
or
say
the
DevOps
report,
the
that
didn't
even
happen.
So
the
the
key
metrics
look
like
your
lead
time
for
changes
from
commitment
employed.
A
The
for
the
delete
on
V
deployment
frequency
is,
they
deployed
two
hundred
and
eight
times
more
to
restore
service
when
you
handle
failure,
two
thousand
six
hundred
and
four
times
faster,
because
if
everything
is
is
designed
properly,
you
know
it
doesn't
matter.
If
you
have
one
machine
that
failed,
something
that's
going
to
come
off
and
something
else
is
going
to
come
back
on.
I
think
Netflix
has
designed
chaos
monkey.
If
you
haven't
heard
about
that
taken
to
that
it's
they
actually
have
something
running
that
that
randomly
picks
something
and
killed
it.
A
So
the
thing
about
that,
if
you
haven't
made
the
mindset
to
DevOps
and
you're
still
operational,
I
get
a
house
six
nines,
you
know
uptime
that
doesn't
really
happen
and
then
the
change
totally
so
the
more
changes
you
pretend
it's
actually
seven
times:
lower
failure
for
the
for
the
elite
performers,
so
the
soft
skills
is
just
as
important
as
the
hard
skills
practice.
Even
more
so
the
collaboration
you
have
to
learn
how
to
communicate
and
includes
listening
people
dem
up
for
teaming
they're
going
to
be
on
our
field
notions
by
needs
they're
prone
to
errors.
A
Let
people
be
human
they're
gonna,
make
mistakes,
be
sincere,
genuine
and
humble
praise
and
reward
accomplishments
and
then
share
your
experience
and
knowledge,
and
it
was
for
watch
Twitter
for
announcements
on
the
Power
Cell
conference
book
volume.
Food
I'm,
gonna
have
a
chapter
actually
that's
dedicated
to
sorceress
and.
A
There's
a
summary
to
begin
here:
DevOps
future.
We
need
to
be
sure,
you're
proficient
on
multiple
scripting
languages.
You
need
to
use
force
control
every
day,
who's
dead,
it's
better
than
subversion,
but
I'm
biased
and
adopt
a
continuous
improvement
mindset,
continually
improve
your
own
skills
and
become
better
more
effective
at
communication.