- [Instructor] And now, let's take a moment to talk about
the cultural side of bringing continual deployment,
continuous integration, and eventually
continuous improvement into an organization.
First of all, fear of change is natural.
We've all been burned by brand new designs
that were going to come in and revolutionize the company
and ended up just making a little bit more work
for some of the people some of the time.
Fear and skepticism are a natural response from experience
and one of the reasons that upfront grand designs
tend not to get funded.
None of us really know coming into
continuous employment and continuous integration,
what we're really trying to build.
We have a system that's manual, we're trying to make it flow
but as we change the system to flow,
it changes how we use it, that changes what
we want it to do, which changes how it flows.
Adopting a broad base of projects and then figuring out
what really works for you will probably encounter
less resistance amongst the colleagues.
Starting with independent tools
that don't pull too many strings
or interfere with too many peoples' routines
is generally a good place to start and a bad place to stay.
Automating deploy jobs for production,
well that just saves time, and most importantly,
it reduces the error rate, which helps your ops people
sleep through the night.
That's a no brainer, everyone's going to get behind that.
And it's not too big a step to go from that, to say,
let's have deployed jobs for the testing environments.
We spend a lot of time building them,
it'd be nice if they were more easily reproduced.
Maybe we could spend more time on automated testing
or all the myriad of other projects
that are waiting for attention.
That's not a big step and brings the project into
a larger scope through the organization and then from there,
you can go on to deploy jobs for individuals.
Anyone can have an environment to develop on
with all the production services,
or at least production-like.
Now that's when you start to get a cultural momentum
for people to realize that continuous improvement
can really bring new ways of going to work.
But if you start off with continuous improvement
will change the way you work,
probably get more skepticism up front.
When you're building tools for others,
first work on being helpful,
then work on changing the company.