How developer platforms fail (and how yours won’t) with Russ Miles

Feb 12, 2026

Russ Miles, a platform engineering and developer experience practitioner, explains why every org already has an internal platform and how to treat it as a product. He explores cognitive load versus burden, designing fast feedback loops and OODA-minded CI/security, and avoiding needless shift-left or pipeline overload. The chat also touches on AI-assisted coding and preventing attention drain and burnout.

Ask episode

AI Snips

Chapters

Books

Transcript

Episode notes

ANECDOTE

Started In Configuration Management

Russ began his career in configuration management to solve painful 'worked on my machine' problems.
That early work shaped his lifelong focus on developer tooling and platforms.

ADVICE

Shorten OODA Loops

Design platforms to shorten feedback loops (OODA loops) so developers can observe and act near development time.
Bring decision-making signals closest to when developers write code, not only at CI/CD or production stages.

ADVICE

Shift Left With Support

Shift checks left only with support; avoid 'dumping' responsibilities onto developers without help.
Ask when developers actually want to know a signal and provide tooling that enables immediate action.

Get the Snipd Podcast app to discover more snips from this episode

Get the app

Russ Miles joins the show to unpack why developer platforms fail and how to rethink platform engineering through the lens of flow of value rather than factory-style developer productivity metaphors.

Russ explains why every organization already has an internal developer platform, and why treating it as platform as a product changes everything. The conversation explores cognitive load and cognitive burden, how to design around strong feedback loops, and why the OODA loop mindset helps teams make better decisions closer to development time.

They discuss the risks of overloading pipelines and CI/CD systems, the tension between shipping fast and handling security vulnerabilities in a regulated environment, and how to “shift left” without simply dumping responsibility onto developers. Drawing on lessons from Rod Johnson, the Spring Framework, TDD, and modern software engineering as described by Dave Farley, Russ reframes platforms as systems that support experimentation through the scientific method.

The episode also touches on AI assisted coding, developer focus, and how thoughtful developer experience and DX surveys can prevent burnout while improving value delivery.

Links

Website: https://www.russmiles.com
Substack: https://russmiles.substack.com
X: https://x.com/russmiles

Resources

Talk: https://www.russmiles.com/platform-engineering-failure-keynote
Substack article: https://russmiles.substack.com/p/developer-platform-devrel-listen

We want to hear from you!

How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend?

Fill out our listener survey! https://t.co/oKVAEXipxu

Let us know by sending an email to our producer, Elizabeth, at elizabeth.becz@logrocket.com, or tweet at us at PodRocketPod.

Check out our newsletter! https://blog.logrocket.com/the-replay-newsletter/

Follow us. Get free stickers.

What does LogRocket do?

LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. Try LogRocket for free today.

Chapters

00:00 What Is a Developer Platform
03:00 You Already Have a Platform
08:00 Cognitive Load vs Cognitive Burden
12:00 Feedback Loops and TDD
18:00 Pipelines, Security and OODA Loops
26:00 The Factory Metaphor Problem
31:00 Modern Software Engineering and Value Delivery
40:00 Avoiding Burnout Through Better DX
46:00 The Software Enchiridion and Final Thoughts