Stenobird

Episode

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

Podcast
PodRocket
Published
Feb 12, 2026
Duration seconds
2762
Processing state
processed
Canonical source
http://podrocket.logrocket.com/how-developer-platforms-fail-and-how-yours-wont-with-russ-miles
Audio
https://dts.podtrac.com/redirect.mp3/aphid.fireside.fm/d/1437767933/3911462c-bca2-48c2-9103-610ba304c673/d7c50869-f660-4748-8d06-5e31f8ad3eee.mp3
JSON
/v1/public/podcasts/podrocket/episodes/how-developer-platforms-fail-and-how-yours-won-t-with-russ-miles
Markdown
/podcast/podrocket/how-developer-platforms-fail-and-how-yours-won-t-with-russ-miles.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/podrocket/episodes/how-developer-platforms-fail-and-how-yours-won-t-with-russ-miles/transcription-requests
    Idempotently request low-priority transcript generation for this episode.
  • GET https://stenobird.com/podcast/podrocket/how-developer-platforms-fail-and-how-yours-won-t-with-russ-miles.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

Stop treating developer platforms as factories and start treating them as products designed to increase the flow of value. This discussion explores how to reduce cognitive burden by building strong feedback loops rather than just adding more pipeline steps.

Topics

  • Platform Engineering
  • Developer Experience
  • Cognitive Load
  • Software Delivery
  • DevOps
  • Internal Developer Platforms
  • Product Management
  • Continuous Integration

Highlights

  • Main idea: A developer platform should be viewed as a product that optimizes for the flow of value rather than a factory for mass production
  • Practical takeaway: Focus on reducing cognitive burden by providing actionable signals at the moment of development, not just dumping security checks into a backlog
  • Failure mode: Creating 'Franken-platforms' by layering bureaucratic pipeline steps that increase developer friction without providing useful feedback
  • Main idea: Effective platform engineering utilizes the OODA loop (Observe, Orient, Decide, Act) to turn technical signals into valuable responses
  • Practical takeaway: Use developer experience (DX) surveys to ensure that the feedback loops you build are actually helpful and not perceived as a nuisance

Chapters

  1. 1:00 What Is a Developer Platform: Redefining the platform as a way to lift the flow of value rather than a manufacturing assembly line.
  2. 4:35 You Already Have a Platform: Why every organization has an internal platform and why adopting a 'platform as a product' mindset is essential.
  3. 8:05 Cognitive Load vs Cognitive Burden: Distinguishing between helpful standardization and the heavy mental tax of poorly designed tooling.
  4. 11:35 Feedback Loops and TDD: The importance of rapid, local feedback loops to build confidence in code before it hits the slow production pipeline.
  5. 15:05 Pipelines, Security and OODA Loops: How to 'shift left' without creating an arms race between developers and security automation.
  6. 25:15 The Factory Metaphor Problem: Critiquing the use of manufacturing terminology like 'pipelines' and 'foundries' in software engineering.
  7. 42:25 Modern Software Engineering: Using DX surveys and the OODA loop to transform technical nuisances into valuable developer experiences.