One of my most-repeated mantras is, “If it can be automated, it should be.”

I firmly believe that this is the path to improving the world.

Nobody should be doing work that can be automated. If a machine can do it, that frees up time for a thinking human mind to do something more valuable.

That sounds great, of course, and most of us would agree to it in principle.

But realistically, most of us don’t follow through on it.

We haven’t internalized the mindset it takes to actively keep looking for things we can automate.

This holds just as true for our infrastructure as anything else.

The goal of this series is to make you aware of how it’s possible to automate your infrastructure tasks, so that you can spend less time fiddling with servers and more time doing the things you actually care about.

Over the next week, you’ll get 3 emails that lay out the details of infrastructure automation for you.

  • Infrastructure as Code: How and why to define your servers, databases, and other resources using code instead of ClickOps.
  • CI/CD: How to fully automate your build-test-deploy cycle, freeing up hours of time per week.
  • Immutable Infrastructure: How to produce 100% ready-to-go machine images that run your app the instant they’re done booting up.

Each one will have practical action steps you can take to get comfortable with the concepts and tools available.

At the end, you’ll get a final email with professional advice on how to apply the principles you’ve learned and keep moving forward in your automation journey.

Sound good?

I hope you’re as excited as I am.

Next up: Infrastructure as Code, or “Why use the web console if you can just make an API call?”