Uploaded August 2026 | Updated September 2026, 2 weeks ago
Most internal developer platforms fail not because of flawed technology, but because organizations treat them as infrastructure projects rather than internal products.
In this InfoQ talk, Max Korbacher - consultant, open-source contributor, and author of Platform Engineering for Architects - explores why success in platform engineering cannot be coded and how shift-left initiatives turn into "shit-left" burnt money.
Learn how to pivot from tool-obsessed, infrastructure-first thinking toward a user-centric product mindset that solves real developer pain points, reduces cognitive load, and handles technical debt effectively.
⏱️ Video Timestamps (For Navigation)
00:00 - Why Platform Engineering Success Can't Be Coded
01:03 - The "Backstage" Trap & Developer Portal Pitfalls
02:40 - The Flaw of Infrastructure-First Thinking
04:05 - "Shift Left" vs. "Shit Left" for Developers
05:45 - Hype Cycles, Silos, and Patch Solutions in Enterprise IT
07:15 - Treating Your Platform as a Product, Not a Project
08:35 - The Platform Iron Triangle: Feasibility, Desirability, Viability
10:05 - Defining Guiding Principles ("We Will" vs. "You Must")
12:10 - Strategic, Personal, and Market Drivers
14:00 - Introducing the Platform Engineering Purpose Canvas
16:10 - The Danger of Misusing DORA Metrics
17:40 - Measuring Real Value with SPACE & DevEx Metrics
19:15 - Developer Research & Reducing Cognitive Load
21:50 - Tackling Technical Debt & Sunk Cost Fallacy
23:35 - Setting Deprecation Criteria for Useless Tools
25:10 - Summary: Culture, Community, and Challenging Conway’s Law
🔗 Transcript available on InfoQ: bit.ly/4yVh7aR
#PlatformEngineering #DevOps #SoftwareArchitecture
Most internal developer platforms fail not because of flawed technology, but because organizations treat them as infrastructure projects rather than internal products.
In this InfoQ talk, Max Korbacher - consultant, open-source contributor, and author of Platform Engineering for Architects - explores why success in platform engineering cannot be coded and how shift-left initiatives turn into "shit-left" burnt money.
Learn how to pivot from tool-obsessed, infrastructure-first thinking toward a user-centric product mindset that solves real developer pain points, reduces cognitive load, and handles technical debt effectively.
⏱️ Video Timestamps (For Navigation)
00:00 - Why Platform Engineering Success Can't Be Coded
01:03 - The "Backstage" Trap & Developer Portal Pitfalls
02:40 - The Flaw of Infrastructure-First Thinking
04:05 - "Shift Left" vs. "Shit Left" for Developers
05:45 - Hype Cycles, Silos, and Patch Solutions in Enterprise IT
07:15 - Treating Your Platform as a Product, Not a Project
08:35 - The Platform Iron Triangle: Feasibility, Desirability, Viability
10:05 - Defining Guiding Principles ("We Will" vs. "You Must")
12:10 - Strategic, Personal, and Market Drivers
14:00 - Introducing the Platform Engineering Purpose Canvas
16:10 - The Danger of Misusing DORA Metrics
17:40 - Measuring Real Value with SPACE & DevEx Metrics
19:15 - Developer Research & Reducing Cognitive Load
21:50 - Tackling Technical Debt & Sunk Cost Fallacy
23:35 - Setting Deprecation Criteria for Useless Tools
25:10 - Summary: Culture, Community, and Challenging Conway’s Law
🔗 Transcript available on InfoQ: bit.ly/4yVh7aR
#PlatformEngineering #DevOps #SoftwareArchitecture
