Some momentum updates. Source: Starbucks CEO explains how company ties together a physical store experience with digital innovation

Free food, during a limited, half-hour window, both saves people some hassle and gets them to show up at the same time to kick off the workday. To understand why this is so important, picture Pivotal without free breakfast. Let’s start with the obvious. Most developers would sleep late if it were up to them. They’d roll into the office around 10 or 11 AM. Which means they’d grab a coffee, maybe respond to a few emails, and then sync up with the team.

Free food, during a limited, half-hour window, both saves people some hassle and gets them to show up at the same time to kick off the workday. To understand why this is so important, picture Pivotal without free breakfast. Let’s start with the obvious. Most developers would sleep late if it were up to them. They’d roll into the office around 10 or 11 AM. Which means they’d grab a coffee, maybe respond to a few emails, and then sync up with the team.

Free food, during a limited, half-hour window, both saves people some hassle and gets them to show up at the same time to kick off the workday. To understand why this is so important, picture Pivotal without free breakfast. Let’s start with the obvious. Most developers would sleep late if it were up to them. They’d roll into the office around 10 or 11 AM. Which means they’d grab a coffee, maybe respond to a few emails, and then sync up with the team.

Free food, during a limited, half-hour window, both saves people some hassle and gets them to show up at the same time to kick off the workday. To understand why this is so important, picture Pivotal without free breakfast. Let’s start with the obvious. Most developers would sleep late if it were up to them. They’d roll into the office around 10 or 11 AM. Which means they’d grab a coffee, maybe respond to a few emails, and then sync up with the team.

Free food, during a limited, half-hour window, both saves people some hassle and gets them to show up at the same time to kick off the workday. To understand why this is so important, picture Pivotal without free breakfast. Let’s start with the obvious. Most developers would sleep late if it were up to them. They’d roll into the office around 10 or 11 AM. Which means they’d grab a coffee, maybe respond to a few emails, and then sync up with the team.

Free food, during a limited, half-hour window, both saves people some hassle and gets them to show up at the same time to kick off the workday. To understand why this is so important, picture Pivotal without free breakfast. Let’s start with the obvious. Most developers would sleep late if it were up to them. They’d roll into the office around 10 or 11 AM. Which means they’d grab a coffee, maybe respond to a few emails, and then sync up with the team.

Free food, during a limited, half-hour window, both saves people some hassle and gets them to show up at the same time to kick off the workday. To understand why this is so important, picture Pivotal without free breakfast. Let’s start with the obvious. Most developers would sleep late if it were up to them. They’d roll into the office around 10 or 11 AM. Which means they’d grab a coffee, maybe respond to a few emails, and then sync up with the team.

I started a new booklet project, the Cloud Native Cookbook. The premise is this: The premise of this book is to collect specific, tactical advice transitioning to a cloud-native organization. The reader is someone who "gets it" when it comes to agile, DevOps, cloud native, and All the Great Things. Their struggle is actually putting it all in place. Any given organization has all of it's own, unique advantages and disadvantages, so any "

In a report giving advice to mainframe folks looking to be more Agile, Gartner’s Dale Vecchio and Bill Swanton give some pretty good advice for anyone looking to change how they do software. Here’s some highlights from the report, entitled “Agile Development and Mainframe Legacy Systems - Something’s Got to Give” Chunking up changes: Application changes must be smaller. Automation across the life cycle is critical to being successful.