Coté

With Matt securely setup in Australia, we get the low-down on the down under. We also discuss rumors of HPE and Rackspace going private and catch up on Verizon buying Yahoo! Also see full show notes.

With Matt securely setup in Australia, we get the low-down on the down under. We also discuss rumors of HPE and Rackspace going private and catch up on Verizon buying Yahoo! Also see full show notes.

I have a larger piece on common objections to “cloud native” that I’ve encountered over the last year. Put more positive, “how to get your digital transformation started with a agile, DevOps, and cloud native” or some such platitudinal title like that. Here’s a draft of the dread-ROI section. The most annoying buzzkill for changing how IT operates (doing agile, DevOps, taking “the cloud native journey,” or whatever you think is the opposite of “waterfall”) is the ROI counter-measure.

Elisabeth Greenbaum Kasson asked me recently for advice on working with legacy applications. Check out her piece on it. Here’s the full reply I sent to her in email: Her topics: - The steps someone could take to get themselves up to speed on their employer’s legacy software. - How this knowledge can make them indispensable (I know that term is relative) - Why this type of expertise is so necessary, especially when it comes to integrating said software with new and/or evolving products.

tl;dr Recently, I’ve been in conversations where people throw some doubt on DRY. In the cloud native, microservices mode of operating where independent teams are chugging along, mostly decoupled from other teams, duplicating code and functionality tends to come more naturally, even necessarily. And the benefits of DRY (reuse and reducing bugs/inconstancy from multiple implementation of the same thing), theoretically, no longer are more valuable than the effort put into DRYing off.

I’ll be in Las Vegas two weeks in a row, which is a rarity. Las Vegas was a frequent destination when I was an analyst at RedMonk and 451: big vendors like IBM and Microsoft love to put on shows here. I suppose it’s cheap, easy to get to, and has rooms a-plenty. The perfect combination. Next week is Pivotal’s big, annual conference, SpringOne Platform. I’m speaking twice, my 5 minute Ignite talk on surviving BigCo corporate culture and then my DevOps/Agile/Everything stump-speech.

Is anyone minding the business side of these container orchestration plays? That’s the main topic we discuss after doing over recent Docker announcements. We then discuss the state of tech journalism and throw out a free business plan for left-ish fried chicken slinging. Also see full show notes.

Is anyone minding the business side of these container orchestration plays? That’s the main topic we discuss after doing over recent Docker announcements. We then discuss the state of tech journalism and throw out a free business plan for left-ish fried chicken slinging. Also see full show notes.

Last week I had a tiny tour of Poland, speaking in Warsaw and in Devoxx in Krakow. It was fun! I got to give the long version of my "Surviving and Thriving in BigCo's talk" and also the "Better Ways of Doing Software" stump speech, as it were. Tragically, I missed the pigs on a spit. Right now I'm up in Chicago at an EPA tech summit where I gave an overview of agile for orginizers such as theirselves.

With two surprise acquisitions this week we have a lot of synergies to discuss. We cover Samsung picking up Joyent, and Microsoft buying LinkedIn. Highly related is a recent article trying to explain what’s going on with private equity buying tech companies. Then, we discuss the big news from chef we’ve been waiting for: the announcement of habitat. Also see full show notes.