I’ve been doing DevOps for a few years now, and I think I’m pretty good at it. Over these years I’ve read some books that really helped me along the way, here they are.

1. The DevOps Handbook

This book is the first one most DevOps professionals start with. I’ve read it 3 times so far, and every time I pick up something new. It’s a great start that gives a great overview of DevOps.

What you’ll get from it: A good generalized knowledge of DevOps. A great place to start.

More Info: The DevOps Handbook

---

2. The Phoenix Project

Another classic you must read. What makes this book different is the fact that’s in novel form, which means after you go through the DevOps Handbook to learn the basics, this book will show the application of the theories and principles in an entertaining story form. It’s much easier to digest and get through. If you read nothing else in this list these two books will give you a solid foundation.

What you’ll get from it: Application of the principles you learned in the DevOps handbook.

More Info: The Phoenix Project

---

3. Accelerate: The Science of Lean Software and DevOps

This book is the result of 4 years of research by Puppet and some of the top minds of DevOps, Dr. Nicole Forsgren, Jez Humble, and Gene Kim. This is a real world application of the theories and principles outlined in the previous two books.

What you’ll get from it: Real world lessons from real organizations implementing DevOps.

More Info: Accelerate: The Science of Lean Software and DevOps

---

4. Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation

The names “Jez Humble” and “David Farley” will become familiar to you after a while, these are solid experts in the field and this book is some of their best work.

What you’ll get from it: A solid foundation in continuous delivery and creating a great deployment pipeline.

More Info: Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation

---

5. Effective DevOps

With O’Reilly books you can always expect quality, and this book is no exception. This covers the big picture of DevOps and provides some actionable suggestions for building up your DevOps organization. Very well written.

What you’ll get from it: A well laid out structure to move your organization into DevOps, including tools, culture guidance, and case studies.

More Info: Effective DevOps

---

6. Measure What Matters

Now matter how well you feel things are going, if you can’t measure it, it doesn’t matter. This book goes in depth into setting goals, measuring them, making changes and achieving them. It really hones in on the iterative process that drives DevOps.

What you’ll get from it: In-depth insight into measuring and improving process flows.

---

More Info: Measure What Matters

7. Site Reliability Engineering

This is a collection of essays from Site Reliability Engineers from Google who focus on the entire lifecycle and introduce effective patterns and principles for keeping things running fast and resilient.

What you’ll get from it: Insight directly from Google into how DevOps helps their organization succeed.

More Info: Site Reliability Engineering

---

8. Site Reliability Workbook

This is a follow up to the previous one that gives real examples and a framework to design your SRE strategy.

What you’ll get from it: Real-world examples and application of everything you’ve learned from the handbook.

More Info: Site Reliability Engineering Workbook

---

9. Infrastructure as Code

This is such a simple concept but one that has many nuances and principles, it takes a deep understanding to get things right.

What you’ll get from it: A deep understanding of Infrastructure as Code and how you can leverage it the right way.

More Info: Infrastructure as Code

---

10. The Goal

Want to read something that will help your modern DevOps structure that was originally written in… the 1980s? Yes, it sounds crazy, but this book is the grandfather of DevOps books and really focuses on process refinement to a microscopic degree. It’s the inspiration for number two on this list and is written in the same “novel” format.

What you’ll get from it: A deep understanding of process. You can use what you learn here in many processes besides DevOps, and in nearly any industry you work in.

More Info: The Goal

---

If you’re looking to start a career in DevOps or just ramp up your skills, this is a great set of books for laying a strong foundation.

Technical knowledge is important for application, but DevOps is more than just tools, it’s a culture change. By better understanding the foundations you’ll be more effective in getting your organization where it needs to be.

What is your DevOps IQ?

My Devops Skill IQ is 232. Can you beat it? Take the test now to find out your Devops IQ score!!

The room is silent except for the buzzing of the fluorescent lights. The judges across the table are staring at you, expressionless. Some have pen and paper, some don’t. They’re all staring at you. Your mouth is so dry it feels like you’ve been eating sawdust all day. You grab the marker and head for the whiteboard. One judge is staring at a laptop. It’s time to show them a quicksort.

I’m going to show you a cool new feature in .NET Core 3.0.

Let’s say you want to create a simple, lean executable you can build and drop on to a server.

In software development you’ll hear the term “moon shot”. If something is a “moon shot” it’s something that’s extraordinarily difficult, like landing on the moon. We say this about some app doing something cool, but what about the software that… landed us on the moon? What was the original “moon shot” all about? 

Do you want to be a coder? Are you on the fence about trying it? Nervous to get started?

The time is now. Time to pull the trigger. 

There has never been a better time to become a coder.

And I’m going to tell you how to get started.  

The mythical “reusable code” idea has existed for decades. It showed up shortly after the first lines of code were written. We preach re-usability and sometimes strive for it but it rarely becomes a reality. I’ve seen various levels of success with this over the years. Everything from “we have a reusable library that 75% of us use” to “we have shared code libraries here, but never use them in your projects”.

Imagine you’re working in a factory. You’re assembling Toyotas all day long, then your part won’t fit. What’s going on? You do this hundreds of times a day but now the bolts won’t go in. No reason to panic, you pull a cord to get help. Two co-workers arrive immediately. They find out you have a box of bolts with the wrong thread. They swap out the bolts, and you keep going.

Imagine you’re an administrator at ACME Widgets and it’s time to upgrade your IIS server. You’ll just copy over some folders and point the DNS to the new server and be done right? If you’ve ever done this before you know that isn’t the case. The new IIS server needs to be configured identically to the old one or you’re going to have problems, and you don’t have time for problems.

Repeatable installs are all the rage in Devops these days. As developers we have this “automate everything” mentality, and for good reason. In this article I’ll show you how you can do that with IIS installation as well. There’s no reason to go hunting and pecking around the GUI every time you need to do this. This is the just one of many ways to automate IIS installs, which I’ll be covering in the next few weeks.

I also cover this in depth in my latest Pluralsight course on Installing IIS.

So you’ve just started building .Net Core applications and really starting to gain some traction. You quickly learn how mature and thorough the .Net Core framework is becoming and think “I need to start writing some unit tests for this!”. As it turns out, it’s super easy and very intuitive, especially for C# developers.