<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Backstage on Saurabh Chaubey</title>
    <link>https://saurabh-chaubey.com/tags/backstage/</link>
    <description>Recent content in Backstage on Saurabh Chaubey</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 15 Jun 2025 10:00:00 +0000</lastBuildDate><atom:link href="https://saurabh-chaubey.com/tags/backstage/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building an Internal Developer Portal with Backstage — Lessons from the Trenches</title>
      <link>https://saurabh-chaubey.com/post/platformengg/building-an-internal-developer-portal-with-backstage/</link>
      <pubDate>Sun, 15 Jun 2025 10:00:00 +0000</pubDate>
      
      <guid>https://saurabh-chaubey.com/post/platformengg/building-an-internal-developer-portal-with-backstage/</guid>
      <description>When I first joined the platform engineering team at a large enterprise insurance company, one of the most common complaints I heard from developers was deceptively simple: &amp;ldquo;I don&amp;rsquo;t know where anything is.&amp;rdquo; They didn&amp;rsquo;t mean they&amp;rsquo;d lost their code. They meant the sprawl — dozens of tools, wikis, dashboards, and ticketing systems — had become so unwieldy that even experienced engineers spent significant chunks of their day just navigating the organisational maze to get things done.</description>
    </item>
    
  </channel>
</rss>
