Platform Engineering vs. DevOps Why not both?

Is the 'shift left' movement hurting your developer productivity? Discover how platform engineering evolves DevOps to reduce cognitive load and accelerate delivery.

#1about 2 minutes

The historical divide between developers and operators

Specialization in development and operations created departmental silos and friction, which hindered collaboration and efficiency.

#2about 3 minutes

Defining DevOps as a collaborative culture

DevOps is a culture, not a role, where everyone involved in a product works together to imagine, develop, deploy, and operate a system.

#3about 3 minutes

Shifting responsibilities left to developers

The "shift left" model requires developers to own their software in production, which provides a crucial feedback loop for improving the code.

#4about 1 minute

The evolving role of modern operations teams

Operations teams are shifting from managing servers to providing high-level services and abstractions through infrastructure as code.

#5about 3 minutes

Introducing platform engineering and its technical components

Platform engineering builds self-service capabilities through an internal developer platform (IDP) to reduce cognitive load and enable fast software delivery.

#6about 2 minutes

Platform engineering as a socio-technical discipline

Beyond technology, platform engineering is a socio-technical discipline focused on user-centric design and improving the overall developer experience.

#7about 2 minutes

The rise of platform engineering in the industry

Industry reports from Gartner and the State of DevOps show a strong trend toward adopting internal developer platforms in high-performing organizations.

#8about 6 minutes

Treating your internal platform as a product

Adopting a product mindset for your platform, with a focus on user needs and an open roadmap, is crucial for its success and adoption.

#9about 5 minutes

Using the CNCF platform engineering maturity model

The CNCF's maturity model helps assess your platform's current state across dimensions like investment and adoption to guide its evolution.

#10about 3 minutes

Common failure mode: The platform as a cost center

Platforms can fail if they are only seen as a cost center, so it's essential to measure and communicate their value to business leadership.

#11about 3 minutes

Common failure mode: Not taking users seriously

Building a platform based on assumptions or forcing its adoption without genuine user involvement and feedback will likely lead to failure.

#12about 3 minutes

Common failure mode: The jack-of-all-trades platform

A platform without a clear purpose and strategy can suffer from feature creep, so it's vital to focus on quality and a defined scope.

#13about 3 minutes

Common failure mode: A non-cross-functional platform team

A successful platform team must be cross-functional, including members with application development, operations, and product management skills.

#14about 1 minute

Key benefits of a successful platform engineering approach

Effective platform engineering improves developer experience and productivity, reduces silos, enforces standards, and makes technical debt manageable.

#15about 13 minutes

Q&A on platform engineering implementation and future

The discussion covers the future evolution of platforms, supporting scalability, clarifying team roles, and overcoming common implementation challenges.