With Platform Engineering, We Can Forget About DevOps | ✉️ #39

Illustration for "MKDEV DISPATCH #39" featuring a smiling man holding a cute animal, with text "With platform engineering, we can forget about DevOps" against an orange background with paper plane graphics. Illustration for "MKDEV DISPATCH #39" featuring a smiling man holding a cute animal, with text "With platform engineering, we can forget about DevOps" against an orange background with paper plane graphics.

Hey! 👋

Last week we’ve released a podcast episode focused on platform engineering, with Sergiu Petean, Head of DevOps at Allianz Direct, as a guest. Check it out for the deep and insightful conversation on the topic. In this dispatch intro, I want to share some thoughts on why I love the term “platform engineering”.

A while ago, I wrote what DevOps is:

In this complicated situation engineers and those who just sympathize them had to start outreach activities. And how can one be successful in them without a catchword? That is how DevOps was born – a marketing term, which causes different associations in people's minds from "inner company culture" to "jack of all trades". <…> DevOps has naturally changed from "culture" and "ideology" to "profession".

“DevOps” doesn’t have a proper definition. It means so many things at the same time that it stopped meaning anything in particular at all. In comparison, take SRE - it has a pretty solid definition and it’s not that hard to describe what SRE Engineers are doing. But SRE doesn’t quite cover the same areas of responsibility that “DevOps engineers” do. That’s why I am happy to see the growing popularity of the term “platform engineering”. Finally, we have a proper term, that incorporates both engineering tasks and all the collaboration and product building work that modern DevOps teams do.

With platform engineering becoming the new default description to the profession part of DevOps, we can finally rollback the definition of DevOps to its original culture-heavy context, without mixing in all the possible technologies and skill sets. One day in the future, we should see more job positions for platform engineers and less for DevOps engineers. DevOps, like Agile, will stick to the domain of “things that ideally whole engineering department should know and practice” and not something that a special group of people is doing.

Now the final problem we have to solve is to properly define what “platform” means. But that’s a whole other discussion.


What We've Shared

On our Youtube channel the journey of cost optimization for AWS and GCP continues:

And on the website it's articles galore, all kinds of themes this time around:


What We've Discovered


A random reminder

There are more places where you can listen to to our podcast. If you prefer Google Podcasts to Spotify or Apple Podcasts, here you go! Let us know, if you want to find us on some other podcast platform, if we are not there already, and we'll be there for you.


The 40th mkdev dispatch will arrive on Friday, March 15th. See you next time!