> Markdown version of [/videos/885-platform-engineering-vs-devops-why-not-both?t=2](https://www.wearedevelopers.com/videos/885-platform-engineering-vs-devops-why-not-both?t=2). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Platform Engineering vs. DevOps Why not both?

Is the shift-left model crushing your developers with operational complexity? Discover why platform engineering doesn't replace DevOps, but provides the product-centric machinery to finally achieve it.

- **Speakers:** Christian Strack
- **Event:** WeAreDevelopers LIVE
- **Published:** April 25, 2024
- **Duration:** 58:40
- **URL:** https://www.wearedevelopers.com/videos/885-platform-engineering-vs-devops-why-not-both

## Summary

The evolution of software development has drastically increased the cognitive load on developers through the "shift left" model, requiring them to manage security, scaling, and operations alongside coding. While DevOps originally aimed to break down silos between development and operations by fostering a shared culture, the sheer complexity of modern infrastructure has overwhelmed engineering teams. Platform engineering emerges not as a replacement for DevOps, but as the sociotechnical machinery needed to actually achieve its collaborative goals. By building internal developer platforms (IDPs), organizations can abstract backend complexities—like domain management, configuration, and compliance—into automated self-service offerings, empowering application developers to focus purely on product logic.

The central tenet of a successful implementation is treating the platform as a true product. Rather than a top-down mandate laden with rigid operational assumptions, a platform must be user-centric and curated specifically for internal developers. Moving forward involves leveraging tools like the CNCF platform engineering maturity model to evaluate capabilities across investment, adoption, and interfaces to identify incremental next steps. Applying product thinking means starting small, establishing a thinnest viable platform, and validating assumptions through continuous qualitative research. Observing how developers actually interact with internal systems yields far more actionable intel than merely asking for feature requests.

Historically, platform initiatives fail due to structural anti-patterns, such as staffing the platform team exclusively with operations personnel, failing to empower a dedicated product owner, or forcing tool adoption without delivering genuine value. A definitive litmus test for platform team health is service uptime ownership: if the platform team functions as an on-call catch-all for an application's reliability instead of the app developers, they are operating as a legacy infrastructure team. True platform engineering teams should squarely own developer productivity. By resisting feature creep, gracefully deprecating unused tools, and accepting that internal platforms cannot accommodate every edge case, organizations can bridge the operational gap to ensure rapid, reliable deployment.

**Keywords:** platform engineering, devops culture, internal developer platforms, IDP, shift left challenges, sociotechnical systems, developer cognitive load, product thinking, minimum viable platform, developer experience, CNCF maturity model, team topologies, self-service capabilities, infrastructure abstractions, service reliability ownership

## Chapters

1. **Introduction to cloud native infrastructure and platform engineering** (00:02) — Exploring motivations for integrating automated platforms with established code delivery pathways.
1. **Evolution of software complexity and departmental specialization** (03:53) — How the growing complexity of distributed systems led to fragmented development and operations departments.
1. **Core definition and cultural mindset of modern DevOps** (06:03) — Aligning cross-functional teams around the common goal of operating production software systems.
1. **Practical limitations of the shift-left development model** (09:11) — Why developers need active operational feedback loops without becoming overwhelmed by infrastructure tasks.
1. **Changing responsibilities for modern infrastructure operations teams** (12:36) — How operations shifts toward providing high-level services using infrastructure as code and abstractions.
1. **Defining platform engineering as a sociotechnical discipline** (13:49) — Building self-service capabilities to minimize developer cognitive load and enable fast flow delivery.
1. **Technical components of internal developer platforms** (14:52) — Designing self-service offerings like configuration management and automated deployments using simplified systems abstractions.
1. **Social and human elements of platform team support** (16:59) — Supporting development teams through user-centric design, reference implementations, and dedicated enablement tasks.
1. **Industry trends and adoption rates of developer platforms** (18:58) — Market data validating how internal developer platforms correlate with high levels of operational maturity.
1. **Applying product thinking to internal platform design** (21:18) — Using user research and continuous feedback to curate an effective experience for engineering customers.
1. **Assessing capabilities with the platform engineering maturity model** (26:52) — Evaluating current investment, adoption, and operational aspects to determine the next skills to acquire.
1. **Overcoming the cost center mindset for infrastructure platforms** (31:25) — Ensuring the business clearly visualizes the value of developer productivity and system reliability.
1. **Validating platform adoption through genuine user choice** (35:12) — Preventing failed adoptions by addressing developer needs rather than relying on mandatory compliance.
1. **Avoiding feature creep and lack of product focus** (37:56) — Defining a clear platform roadmap to prevent the creation of unmanageable edge-case solutions.
1. **Building truly cross-functional platform engineering teams** (41:20) — Equipping platform efforts with product owners, application developers, and necessary organizational mandates.
1. **Summarizing the organizational benefits of platform engineering** (44:11) — How proper internal tooling bridges organizational silos, manages technical debt, and boosts developer experience.
1. **Speculating on the future evolution of developer platforms** (45:54) — Predicting how platform patterns will abstract external infrastructures across more overarching business domains.
1. **Ensuring structural scalability in rapidly growing architectures** (47:27) — Communicating clearly with users to build flexible tools that avoid over-engineering structural solutions.
1. **Fostering collaboration between developers and operational staff** (48:36) — Unifying disparate workflows around common organizational goals through shared programmatic platform interfaces.
1. **Simplifying modern software development with operational abstractions** (50:11) — Eliminating manual ticketing and deployment hurdles through curated self-service infrastructure governance.
1. **Necessary skills for adopting a platform engineering mindset** (51:37) — Transitioning organizational focus toward product thinking and communicating actionable pain points seamlessly.
1. **Implementing effective developer platform practices through iterations** (53:01) — Treating infrastructure solutions strictly as a product through short loops and direct user validation.
1. **Clarifying organizational roles within technical engineering topologies** (53:54) — Aligning teams and execution responsibilities strictly to avoid friction when rolling out modern internal toolchains.
1. **Navigating operational hurdles after initial platform launches** (55:11) — Shifting strategies from reactive infrastructure firefighting toward proactive capability development without sacrificing organizational trust.
1. **Tracing a personal journey into professional software engineering** (56:25) — Discovering an enduring passion for computer science and adjusting dynamically toward organizational infrastructure consultancy.

## Related Moments

- [Shifting focus from platform engineering to developer productivity](https://www.wearedevelopers.com/videos/884-forget-developer-platforms-think-developer-productivity) (from "Forget Developer Platforms, Think Developer Productivity!")
- [Designing internal developer platforms and product team responsibilities](https://www.wearedevelopers.com/videos/1614-ai-augmented-devops-with-platform-engineering) (from "AI-Augmented DevOps with Platform Engineering")
- [Pivoting product strategy toward platform engineering](https://www.wearedevelopers.com/videos/100122-how-agentic-devops-gave-us-dev-time-back) (from "How Agentic DevOps gave us Dev time back")
- [Breaking down organizational silos to define platform engineering culture](https://www.wearedevelopers.com/videos/238-the-journey-from-developer-to-devops-what-i-ve-learnt-along-the-way) (from "The journey from developer to devops - what i've learnt along the way")
- [Recognizing the downward spiral of platform engineering](https://www.wearedevelopers.com/videos/884-forget-developer-platforms-think-developer-productivity) (from "Forget Developer Platforms, Think Developer Productivity!")
- [Scaling platform engineering adoption across organizational boundaries](https://www.wearedevelopers.com/videos/1596-backstage-software-templates-for-java-developers) (from "Backstage Software Templates for Java Developers")

## Related Articles

- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)
- [Why developer experience matters](https://www.wearedevelopers.com/magazine/514-why-developer-experience-matters)
- [How Engineering Hubs Build Visibility at Developer Conferences like WeAreDevelopers World Congress](https://www.wearedevelopers.com/magazine/720-how-engineering-hubs-build-visibility-at-developer-conferences-like-wearedevelopers-world-congress)
- [Events like RSAC Get You CISOs. Developers Decide What Actually Gets Deployed.](https://www.wearedevelopers.com/magazine/693-events-like-rsac-get-you-cisos-developers-decide-what-actually-gets-deployed)

## Related Jobs

- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**
- [Senior Software Engineer, Client Apps Platform](https://www.wearedevelopers.com/jobs/ext/1773893-senior-software-engineer-client-apps-platform) at **GitHub**
- [Principal Product Manager, Agent Platform](https://www.wearedevelopers.com/jobs/ext/277541-principal-product-manager-agent-platform) at **GitHub**
- [Platform Engineer (DevOps)](https://www.wearedevelopers.com/jobs/48264-platform-engineer-devops) at **WDW Consulting GmbH**
- [Software Engineer, Platform Engineering (L2)](https://www.wearedevelopers.com/jobs/ext/1956829-software-engineer-platform-engineering-l2) at **Twilio**