Hey, friends! Welcome to today's video where I want to dive into something slightly different, but oh-so-thought-provoking. Join me as I share my insights on platform engineering and how it's shaping the DevSecRelOps 🤣 paradigm.
Let's take a step back and embark on a storytelling journey. Once upon a time, developers handled everything related to software engineering. But as technology advanced, complexities arose, leading to the birth of DevOps—a fusion of developers and operations to bridge the communication gap and streamline processes. Later, DevSecOps emerged, integrating security into the mix.
And now, we have platform engineering—a term that seems like the missing piece of the puzzle. It goes hand in hand with DevOps and DevSecOps, but with a twist. You see, we've always focused on the technical side and security aspects, but what about the human element? It turns out that 90% of software engineering problems stem from communication issues, with only 10% being purely technical (personal opinion not supported by evidence).
As the industry evolves, we're witnessing the rise of Internal Developer Platforms—a way for developers to operate their applications without getting overwhelmed by the ever-expanding cloud ecosystem. This responsibility is shifting to platform teams, who design internal products to empower developers, allowing them to interact with multiple cloud providers effortlessly.
But why am I proposing the term DevSecRelOps? Well, "Rel" stands for DevRel, short for Developer Relations—an activity where specialists bridge the gap between a product and the developers using it. It's a concept employed by companies like GitHub and Google, focusing on describing new features and services targeted at developers.
With platform engineering, we're moving towards a similar concept. Internal teams produce products targeting developers within the organisation as customers. Being solely an operations or development specialist may not suffice anymore. We must integrate these additional skills into our platform teams. Hence, the notion of DevSecRelOps—a provocative term that aims to close the gap between platform teams, developers, and customers.
I've predominantly worked in platform teams, and one thing I've noticed is the limited focus on developers as customers and the platform as a product. That's where DevSecRelOps comes into play, potentially revolutionizing the way we approach platform engineering.
I'd love to hear your thoughts on this term and the importance of the human aspect in technical teams. Share your insights and join the discussion in the comments below. Don't forget to hit that subscribe button to stay updated with more intriguing topics. Together, let's unravel the future of platform engineering. Catch you in the next one! Bye!
WHO AM I:
Hey friends, welcome to my YouTube channel @outofdevops . If you're new my name is Anto, here I talk about software engineering and software engineers. Don't forget to comment like and subscribe 👍🏻.
YOUTUBE GEAR:
🎥 My YouTube Camera Gear - https://kit.co/outofdevops
MY SOCIAL LINKs:
🐦 Twitter - / outofdevops
📘 Facebook - / outofdevops
📰 My blog - https://amasucci.com
📸 Instagram - / outofdevops
GET IN TOUCH:
If you’d like to talk, I’d love to hear from you. Tweeting @OutOfDevOps directly will be the quickest way to get a response, but if your question is very long, feel free to email me at [email protected].
PS: Some of the links in this description are affiliate links that I get a kickback from 😜