Tanzu Talk

We're seeing more adoption of agile in large organizations than ever before. More interestingly, they're really doing it, totally transforming the multiple layers of process to boil down to the the leanest bucket of parts that ensure quality, useful software. While there's a lot - a lot! - of work to be done, there's a slew of useful best practices, stories, and anecdotes emerging. In this episode we discuss this general trend and two of the related topics: scaling agile up and pair programming.

We also cover spate of recent news about Cloud Foundry performance, .Net rolling out into various ecosystems, the new leadership at the Cloud Foundry Foundation, and lobster eggs benedict.

Companies that want to get better at software are staffing and organizing themselves in new ways. The traditional "silos" approach clusters teams together into functional groups, whereas modern approaches cluster around product. We cover skills by looking at a recent Cloud Foundry Foundation survey on developer skills and then discuss some sections of Coté's upcoming cloud native journey booklet related to team composition and outsourcing.

While news is sparse this week, we point to some "what does the US election mean for tech" news and also cover Microsoft Teams in relation to how "chat ops" has been extended to be SOP in most modern IT shops or, rather, how it should be.

Containers are as big a deal in the Cloud Foundry world as anywhere else; what was once an obscure method of process isolation is a good way to boost developer productivity. In this episode we talk with Pivotal's Onsi Fakhouri and James Bayer about containers and Pivotal Cloud Foundry. After discussing the history of containers, we talk about how containers are supported in Pivotal Cloud Foundry, and then discuss how to think through the use of containers versus buildpacks, or using containers at all. See full show notes here: https://blog.pivotal.io/pivotal-conversations

There's no end of discussion about the Internet of Things now-a-days, but much of it is either about flashing toothbrushes or crazy-making huge numbers with abstract use cases. This week we talk with Pivotal's Saurabh Gupta about the work he's been doing in the IoT space with Pivotal customers. He has a great model illustrating how to think about IoT use cases which we cover in-depth, with several examples. At the end of our discussion, you'll have a good appreciation of IoT is improving the business of "the big, noisy, dirty machines."

We also discuss some recent news: clouderati's new jobs, CenturyLink buying Level 3, new MacBooks and Surfaces, AI market-sizing hijinks, and an example of cloud native business thinking in the hotel industry.

See full show notes: https://blog.pivotal.io/pivotal-conversations

Distributed systems are hard. Building a microservices architecture that supports evolutionary changes without breaking “contracts” among services? Especially hard. In this podcast, we grabbed Oliver Gierke, Kenny Bastani, and Andrew Clay Shafer to talk about inter-service communication, consumer-driven contract testing, and service versioning. Listen in as we wrestle with tricky concepts, and still end up as friends.

See full show notes at https://blog.pivotal.io/pivotal-conversations.

Live to Tape from DellEMCWorld (Ep. 38) by Pivotal Software

When you're moving fast, things will break more often. It's little wonder, then, that with a microservices approach you need to pay close attention to ensuring the safe, yet speedy change to APIs. The idea of "consumer-driven contracts" has been percolating for a long time. The idea is to shift the "power" in the relationship between the provider of APIs and the consumer of those APIs more to the consumers. In this episode, I talk again with Marcin Grzejszczak on this topic and we discuss how the newly GA's Spring Cloud Contract enables all this thinking.

See https://blog.pivotal.io/pivotal-conversations for full show notes.

Building a high performance organization requires more than just putting good technologies and practices in place for developing and delivering product, it requires the right culture as well. In large organizations, this often means changing the culture. At the heart of that is people, so it's natural that Human Resources will get involved, hopefully sooner rather than later.

To discuss these topics, we bring back Joe Militello for the second time to discuss how Pivotal thinks through HR and the consultative work our team has been doing on these topics. His framing that I really liked relates to his summary of what HR does: improving "the experience of our employees and candidates.” We go over some best practices for transforming how HR operates and give a little peek into how Pivotal manages employee's experience.

Released a few weeks ago, Pivotal Cloud Foundry 1.8 is chock full of new features and improvements. We talk with Jared Ruckle about them, delving into security, databases, and new services. These features deliver on the Pivotal Cloud Foundry goal of speeding up time to market (with faster release cycles) and, yet, still being a general purpose application platform that organizations can use to run all their customer software. We also discuss another recent piece from Jared on opinionated platforms - check out that tree house!

In the news, we cover the recent data breach at Yahoo, Windows Server 2016 and Docker support, Azure's ever growing geographic foot-print, and our hopes and dreams for the rumored Twitter acquisition.

See full show notes: http://pivotal.io/podcast

Backed up into a corner, developers will start coding. It's little wonder then that as large organizations have been faced with modernizing their approach to software - all that "digital transformation" - developers in years past have been focusing on building their own platforms. Our guest this week, Matt Walburn, worked on one such project. He joins us this week to talk about the lure of the DIY platform and why, now that options like Pivotal Cloud Foundry are available, it's usually a poor use of organization time. Not only do you need to build the full platform with all the features from the development phase to running in production, but you have to maintain it as well. As Matt says, this will run you several millions of dollars in staff salary alone. And then, after all that, you still have to write all those applications you originally set out to make.

See full show notes at http://pivotal.io/podcast