# #60 How to NOT fail in Platform Engineering

Page: https://stenobird.com/podcast/reliability-enablers-6320409/60-how-to-not-fail-in-platform-engineering
Text version: https://stenobird.com/podcast/reliability-enablers-6320409/60-how-to-not-fail-in-platform-engineering.md
Podcast: [Reliability Enablers](https://stenobird.com/podcast/reliability-enablers-6320409)
Published: 2024-10-01T12:30:00+00:00
Episode link: https://read.srepath.com/p/60-how-to-not-fail-in-platform-engineering
Audio file: https://api.substack.com/feed/podcast/149602222/fe55c76447e8dcab2a7d6f74a1162e08.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/reliability-enablers-6320409/episodes/60-how-to-not-fail-in-platform-engineering
Duration seconds: 1834

## Resource

Here’s what we covered: Defining Platform Engineering * Platform engineering : Building compelling internal products to help teams reuse capabilities with less coordination. * Cloud computing connection : Enterprises can now compose platforms from cloud services, creating mature, internal products for all engineering personas. Ankit’s career journey * Didn't choose platform engineering; it found him. * Early start in programming (since age 11). * Transitioned from a product engineer mindset to building internal tools and platforms. * Key experience across startups, the public sector, unicorn companies, and private cloud projects. Singapore Public Sector Experience * Public sector : Highly advanced digital services (e.g., identity services for tax, housing). * Exciting environment : Software development in Singapore’s public sector is fast-paced and digitally progressive. Platform Engineering Turf Wars * Turf wars : Debate among DevOps, SRE, and platform engineering. * DevOps : Collaboration between dev and ops to think systemically. * SRE : Operations done the software engineering way. * Platform engineering : Delivering operational services as internal, self-service products. Dysfunctional Team Interactions * Issue : Requiring tickets to get work done creates bottlenecks. * Ideal state : Teams should be able to work autonomously without raising tickets. * Spectrum of dysfunction : From one ticket for one service to multiple tickets across teams leading to delays and misconfigurations. Quadrant Model (Autonomy vs. Cognitive Load) * Challenge : Balancing user autonomy with managing cognitive load. * Goal : Enable product teams with autonomy while managing cognitive load. * Solution : Platforms should abstract unnecessary complexity while still giving teams the autonomy…

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/reliability-enablers-6320409/episodes/60-how-to-not-fail-in-platform-engineering/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/reliability-enablers-6320409/60-how-to-not-fail-in-platform-engineering.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.