Quotes About Automation

In other words, those with the oracular ability to work with and tease valuable results out of increasingly complex machines will thrive.

A good chief executive is essentially a hard-to-automate decision engine,

There are many ways to discover that you're not valuable in our economy. For Jason Benn the lesson was made clear when he realized, not long after taking a job as a financial consultant, that the vast majority of his work responsibilities could be automated by a "kludged together" Excel script.

this new economy, three groups will have a particular advantage: those who can work well and creatively with intelligent machines, those who are the best at what they do, and those with access to capital.

The key question will be: are you good at working with intelligent machines or not?

What these organizations have in common is a high-trust culture that enables all departments to work together effectively, where all work is transparently prioritized and there is sufficient slack in the system to allow high-priority work to be completed quickly. This is, in part, enabled by automated self-service platforms that build quality into the products everyone is building.

Without automated testing, continuous integration is the fastest way to get a big pile of junk that never compiles or runs correctly.

DevOps practices can be made compatible with ITIL process. However, to support the shorter lead times and higher deployment frequencies associated with DevOps, many areas of the ITIL processes become fully automated, solving many problems associated with the configuration and release management processes (e.g., keeping the configuration management database and definitive software libraries up to date).

Instead of IT Operations doing manual work that comes from work tickets, it enables developer productivity through APIs and self-serviced platforms that create environments, test and deploy code, monitor and display production telemetry, and so forth.

They start making a list: Every developer uses a common build environment. Every developer is supported by a continuous build and integration system. Everyone can run their code in production-like environments. Automated test suites are built to replace manual testing, liberating QA people to do higher value work. Architecture is decoupled to liberate feature teams, so developers can deliver value independently. All the data that teams need is put in easily consumed APIs

Get humans out of the deployment business.

To have humans executing tests that should be automated is a waste of human potential.

We should also collect telemetry on how long it takes us to execute our builds and tests. By

For Phoenix, it takes us three or four weeks for new developers to get builds running on their machine, because we've never assembled the complete list of the gazillion things you need installed in order for it to compile and run. But now all we have to do is check out the virtual machine that Brent and team built, and they're all ready to go.

As Damon Edwards observed, "Without these self-service Operations platforms, the cloud is just Expensive Hosting 2.0.

if we all want our developers to be productive, they need to be able to perform builds on Day One.

Without automated testing, the more code we write, the more money it takes for us to test.

Continuous Delivery.

a small number of reliable, automated tests are almost always preferable over a large number of manual or unreliable automated tests.

The key thing we should care about is not the form, but the outcomes: deployments should be low-risk, push-button events we can perform on demand.

By adding the expertise of QA, IT Operations, and Infosec into delivery teams and automated self-service tools and platforms, teams are able to use that expertise in their daily work without being dependent on other teams.

Amazingly, the transformations are not primarily based on automation. Instead, the incredible improvements come from modifying policies around the system of work and the policies that control work in process, ensuring that there are effective cross-functional teams, subordinating everything to the constraint, and managing handoffs well.

Chuck Rossi, Director of Release Engineering at Facebook, described, "All the code supporting every feature we're planning to launch over the next six months has already been deployed onto our production servers. All we need to do is turn it on.

This includes the creation of automated build, integration, and test processes so that we can immediately detect when a change has been introduced that takes us out of a correctly functioning and deployable state.