A recent rendition of one of my standard talks at the Austin DevOps Meetup. See the slides as well.
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. if the talk title was something like “Digital Transformation in the Streets.”
Much of it draws a lot on my cloud native journey booklets as well.
Check out this fine panel from DellEMCWorld:
Observations on how large organizations successfully go through Digital transformation.
When it comes to digital transformation, despite vast resources, large organizations are 40% less likely to be high performing organizations than smaller ones.
A webinar we recently did with Holger and Brian Gregory. It turned out well, esp. the discussion part.
I was kindly invited to guest co-host and be the guest on this week’s Speaking in Tech. There’s not that many “enterprise IT” focused podcasts out there and this is one of my favorite. Check out the show notes, listen below, or just download the MP3 directly.
As you may recall, I was on for the first time last year, while I was down in Mexico.
These are my tips on getting by in a large organization. They’re intended for people who are working in less than ideal circumstances – you know, there’s no leaked “culture deck” or well-stocked snacks. Check out the slides as well.
If you work at a small, cool company, you can skip this talk. The rest of us in large, slow moving companies that rely on meetings, email, and inbox 2,000 to get the daily work done need some therapy and advice for thriving in big, “dumb” companies. I’ve worked in such companies and figured out how to thrive in the “back to back meetings” world we’re taught to avoid. I’ll tell you my tactics. Ideally, you’d adapt the no manager GitHub dream, adapt the Spotify and Netflix cultures of awesomeness. Indeed. However, oftentimes there are good reasons to stay in the relatively dysfunctional companies you’re at. They’re big, slow moving, and seem to use Microsoft Office as their core innovation engine. If people at your work always talk about “aircraft carriers” this is the talk for you. For whatever reasons you’re there, why not make the best of it and learn how to get along and even thrive instead of letting your head explode in rage. This talk will go over what I’ve learned working in large companies from my strange adventure working with a bunch of MBAs in corporate strategy at Dell, to working with large companies as an industry analyst, to working with marketing and product people at large companies.
- The book Moral Mazes, an old, but excellent guide to understanding how people in company’s think and, therefor, how companies operate in the real world.
- “War Stories from the God Pod: Strategies for killing high stakes Executive presentations” – Matt Baker’s excellent tips
- Me: “7 + 5 BigCo Anti-patterns : white collars doing it wrong,” me from April 2016.
- Weekly therapy at SoftwareDefinedTalk.com.
Want something shorter?
I’m often asked to come speak on, well, the topic of “tell us about the new, interesting stuff out there that makes software development better…but don’t be pitching me anything.” This is my most recent cut at that kind of talk.
You can check out the slides as well.
A little while ago I was on The New Stack Makers podcast with Alex Williams, talking cloud and Pivotal. Check it out:
Here’s what we go over:
In this podcast with Michael Coté, who works at Pivotal in technical marketing, he and The New Stack founder Alex Williams talk about current production systems and development environments for building applications. According to Coté, Pivotal describes these new systems and environments as “cloud native.”
Over the course of this interview, Coté discusses best practices and illustrates three requirements for cloud native development and deployment: utilizing the patterns of microservices architecture, implementing a DevOps approach, and striving for continuous delivery as the primary vehicle for software delivery.
Check out my brief (~15 minutes) discussion with Alex Williams at The New Stack about how we’re thinking about the architecture of Pivotal Cloud Foundry. In addition to giving an overview of what Pivotal Cloud Foundry is and the cloud management and PaaS capabilities it has, I go over a way of thinking about the layered architecture (and why you’d care) that Andrew has been talking about recently.
There’s a longer version of this in my recent talk from Gartner ADDI as well.