I get asked to talk on DevOps a lot. Here’s my current (late 2016 and 2017) presentation, going over the why’s, the how’s, the technologies, and the meatware that supports including some best and worst practices based on what Pivotal customers do. See the newer slides with big pictures on most slides, and some of the older slides Also, here’s a more blatantly pro-Pivotal (and longer) version that you might have seen, esp.

I get asked to talk on DevOps a lot. Here’s my current (late 2016 and 2017) presentation, going over the why’s, the how’s, the technologies, and the meatware that supports including some best and worst practices based on what Pivotal customers do. See the newer slides with big pictures on most slides, and some of the older slides Also, here’s a more blatantly pro-Pivotal (and longer) version that you might have seen, esp.

I get asked to talk on DevOps a lot. Here’s my current (late 2016 and 2017) presentation, going over the why’s, the how’s, the technologies, and the meatware that supports including some best and worst practices based on what Pivotal customers do. See the newer slides with big pictures on most slides, and some of the older slides Also, here’s a more blatantly pro-Pivotal (and longer) version that you might have seen, esp.

I get asked to talk on DevOps a lot. Here’s my current (late 2016 and 2017) presentation, going over the why’s, the how’s, the technologies, and the meatware that supports including some best and worst practices based on what Pivotal customers do. See the newer slides with big pictures on most slides, and some of the older slides Also, here’s a more blatantly pro-Pivotal (and longer) version that you might have seen, esp.

Check out my review of the DevOps Handbook and Start and Scaling DevOps in the Enterprise over on The New Stack. Unsurprisingly, I liked both of them, esp. the second: What I find so helpful, and even thrilling, about Gruver’s book, is that it’s exacting in its instructions and walks through several what-if scenarios for addressing common problems that come up when applying agile and DevOps at scale. Plus, it’s the perfect size for a book of this type: about 90 pages that’ll take you about 90 minutes to read.

Check out my review of the DevOps Handbook and Start and Scaling DevOps in the Enterprise over on The New Stack. Unsurprisingly, I liked both of them, esp. the second: What I find so helpful, and even thrilling, about Gruver’s book, is that it’s exacting in its instructions and walks through several what-if scenarios for addressing common problems that come up when applying agile and DevOps at scale. Plus, it’s the perfect size for a book of this type: about 90 pages that’ll take you about 90 minutes to read.

Check out my review of the DevOps Handbook and Start and Scaling DevOps in the Enterprise over on The New Stack. Unsurprisingly, I liked both of them, esp. the second: What I find so helpful, and even thrilling, about Gruver’s book, is that it’s exacting in its instructions and walks through several what-if scenarios for addressing common problems that come up when applying agile and DevOps at scale. Plus, it’s the perfect size for a book of this type: about 90 pages that’ll take you about 90 minutes to read.

Check out my review of the DevOps Handbook and Start and Scaling DevOps in the Enterprise over on The New Stack. Unsurprisingly, I liked both of them, esp. the second: What I find so helpful, and even thrilling, about Gruver’s book, is that it’s exacting in its instructions and walks through several what-if scenarios for addressing common problems that come up when applying agile and DevOps at scale. Plus, it’s the perfect size for a book of this type: about 90 pages that’ll take you about 90 minutes to read.

Check out my review of the DevOps Handbook and Start and Scaling DevOps in the Enterprise over on The New Stack. Unsurprisingly, I liked both of them, esp. the second: What I find so helpful, and even thrilling, about Gruver’s book, is that it’s exacting in its instructions and walks through several what-if scenarios for addressing common problems that come up when applying agile and DevOps at scale. Plus, it’s the perfect size for a book of this type: about 90 pages that’ll take you about 90 minutes to read.

Check out my review of the DevOps Handbook and Start and Scaling DevOps in the Enterprise over on The New Stack. Unsurprisingly, I liked both of them, esp. the second: What I find so helpful, and even thrilling, about Gruver’s book, is that it’s exacting in its instructions and walks through several what-if scenarios for addressing common problems that come up when applying agile and DevOps at scale. Plus, it’s the perfect size for a book of this type: about 90 pages that’ll take you about 90 minutes to read.