Video: "In 2017 Amazon is expected to spend $4.5bn on television and film content, roughly twice what HBO will spend. But it has a big payoff." Prime momentum: "Mr Nowak reckons the company had 72m Prime members last year, up by 32% from 2015." Cloud: "Last year AWS’s revenue reached $12bn, up by more than 150% since 2014." Anti-trust, in the US: "If competitors fail to halt Amazon’s whirl of activities, antitrust enforcers might yet do so instead.

Can we take that governance and work with the platform team to codify, to automate that which they were doing on a per application basis - that's, quiet frankly slowing down the delivery of the software - can we take that governance and can we have them work with the platform team to codfiy, to actually automate on a per application basis, have them expose that as a service on the platform -Cornelia Davis on governance and cloud-native, “Who Does What?

If there’s one complaint that I hear consistently in my studies of IT in large organizations, it’s that government IT, as traditionally practiced, is fucked. Compared to the private sector, the amount of paperwork, the role of contractors, and the seeming separation between doing a good job and working software drives all sorts of angst and failure. Mark Schwartz’s book on figuring out “business value” in IT is turning out to be pretty amazing and refreshing, especially on the topic of government IT.

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.

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.

This post is pretty old and possibly out of date. There’s updates on this topic and more in my book, Monolithic Transformation. Every journey begins with a single step, they say. What they don’t tell you is that you need to pick your step wisely. And there’s also step two, and three, and then all the n + 1 steps. Picking your initial project is important because you’ll be learning the ropes of a new way of developing and running software, and hopefully of running your business.