I don’t really know what I think about the idea and movement of “platform engineering.” It definitely has the feel of a market and category now. I reference it all the time, as do “us all” in the cloud native world. I suspect over the next year it’s the phrase everyone will be using for whatever it is exactly.
On the one hand, platform engineering an obvious, kind of goofy-rude hijacking of DevOps. In a sort of ideal world, it would all just be called “DevOps,” and we’d all be debating if a “DevOps engineer” includes managing the developer platform.
On the other hand, the overall community feels like it’s up to a lot of good. It’s certainly rallied a lot of new content, stories, concepts, and all the thought-leaders. The notion of pulling in IDPs and other developer tools is, I think, an addition to DevOps. But again: shouldn’t that just be an addition to, an evolution of, DevOps?
We have a good discussion of what exactly a “DevOps platform” is on this week’s Software Defined Talk, related to discussing the recent Gartner 2023 Magic Quadrant for DevOps platforms.
The names you give things are powerful, and accumulate a lot of meaning. Re-naming something is often required to evolve it, to sort of reboot everyone’s collective mindset to try again.
“We have three DevOps teams.”
“Cool, cool. How do developers get a development environment to start coding.”
“They open a ticket, of course. Wait. Was that a trick question?”
I’m beginning to think that platform engineering is a new take on DevOps where the community reverses the old DevOps principle that culture matters far more than tools.
In platform engineering (so far), tools matter a great deal. Practices are important (the community is close to subsuming the platform as a product notion). Culture is either assumed or not really in scope: there’s almost this feel of “oh, that’s DevOps' job…”
That’s kind of how DevOps played out at first. Automation, monitoring, then several years of surveys, PDFs, and conferences, and all the slowly-sudden: it’s all about the culture, tools don’t matter.
Agile software development was always about practices and, eventually, culture. The only tools required were unit testing frameworks and, if you were luxurious, backlog/project management tools like Pivotal Tracker and Rally for the SAFe-set.
Agile’s utter rejection of tools probably came as a reaction to the Rational era where tools were king. Rational tools embodied the process and practices. It was sort of impossible to do RUP without tools, especially the UML generators.
As with DevOps, platform engineering will learn soon enough that the people and processes are part of the platform as well: they’re as much a technology as the actual tools. Everyone knows this, of course, because of DevOps. But giving your tools and “culture” equal footing has proven hard to do over the decades. You tend to go way too far on one or the other.
Anyhow! You should check out my talk at PlatformCon! It’s posted now. I try to cover the evergreen practices and mindsets of doing platforms, whatever you want to call it.
These practices are based on years of experiences of platform teams in large, normal organizations like Mercedes, BT, The Home Depot, UBS, JP Morgan Chase, etc. And, the talk is a compact 15 minutes, which was a rewarding challenge.
There’s two other talks I recommend:
Great talk from the Cloud Foundry team at Mercedes-Benz on how they’ve been doing platform engineering. 300 apps, 1,500 platform services, and by my count, about 7 years of running it.
An overview of platform best practices from Bryan Ross, formally of Sky TV in the UK. Bryan spends a lot of time talking about marketing and building trust - all the culture stuff. I think it’s VMware’s sponsor talk, so he goes over what VMware does a little bit.
I don’t like Anime, Software Defined Talk #418 - This week we discuss the Gartner MQ for DevOps platforms, Apple’s announcements and Cisco’s attempt to simplify. Plus, some thoughts on Meatloaf and Anime.
What’s a ”Platform Maturity Model”? Tanzu Talk - In this episode, Cora and Coté talk with Abby Bangser about the platform maturity model draft that the platform working group at the CNCF has been working on. While the draft is a work in progress, the model the team is developed is extremely useful for thinking about how you build and run your platform team. Check out the interview, and if you’re interested in more, take a look at the draft paper. If you’re really full of beans, you can also contribute.
Talks I’ll be giving, things I’ll be doing, places I’ll be going.
June 21st Cloud Foundry Day, Heidelberg, speaking. June 21st Making digital transformation stick in government agencies, online. June 22nd to 23rd DevOpsDays Amsterdam June 28th, July 4th, July 11th Cloud Native for Financial Services talk series.August 21st to 24th SpringOne & VMware Explore US, in Las Vegas. Sep 6th to 7th DevOpsDays Des Moines, speaking. Sep 18th to 19th SHIFT in Zadar.
Apple Savings Accounts Funds Withdrawal Concerns - “Customers who have requested withdrawals have reported waiting 2–4 weeks for their money to show up.” // This is the catch with that account. 4.5% interest is great, though. You have to think of the Apple savings account as a weird, 30 day CD.
Improving developer productivity with Platform as a Product, from PlatformCon 2023 - Great talk from the Cloud Foundry team at Mercedes-Benz on how they’ve been doing platform engineering. 300 apps, 1,500 platform services, and by my count, about 7 years of running it.
Richard Seroter on shifting down vs. shifting left - Clever, fun phrasing! Build stuff into the platform instead of having (application ) developers figure it out, or, really, ops/platform engineer/DevOps types. The ability to do this depends on using a vendor stack, either public cloud or the likes that VMware and others sell.
Netherlands enables contactless payments on entire public transport network - Yup, it’s pretty great.
Microsoft Design - Wallpapers - Fun! Including the old XP one in 4K somewhere.
Gartner Marketing Survey Finds B2B Buyers Value Third-Party Interactions More Than Digital Supplier Interactions - “The survey showed YouTube as the top social media channel to influence a recent B2B purchase decision, followed by Facebook, Instagram, Twitter, LinkedIn and TikTok.” And: “Where buyers do research when figuring out what to buy // “B2B buyers identified a supplier’s website as the most leveraged channel, followed by the supplier’s social media channels, an online search for the supplier and the supplier’s interactive tools.”
How to keep your new tool from gathering dust - “Learn where your tool can have the biggest impact; Enlist advocates to demonstrate and socialize your tool; Build consensus over time; Minimize friction around adoption”
See y’all next time!