<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>platform-engineering on Coffee Chats</title>
    <link>https://havel.my.id/tags/platform-engineering/</link>
    <description>Recent content in platform-engineering on Coffee Chats</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <copyright>© 2026 Havel Cyrus</copyright>
    <lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://havel.my.id/tags/platform-engineering/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Revisiting Backstage as Developer Portal</title>
      <link>https://havel.my.id/posts/revisiting-backstage/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://havel.my.id/posts/revisiting-backstage/</guid>
      <description>&lt;p&gt;My first interaction with Backstage took place about three to four years ago. At that time, the feature was quite basic, basically a lightweight system for service cataloging, hosting tech docs, and providing templating engine. I admit, I didn&amp;rsquo;t really utilize it properly back then. Initially, my team leveraged it solely to list our microservices, a necessary step given we managed customer data distributed across numerous clusters. We even built a custom plugin to visualize AWS billing based on customer metadata, but beyond that, our usage was limited.&#xA;In retrospect, I didn&amp;rsquo;t realize that we can actually get more out of it. I missed opportunities to leverage all of its features. My focus was elsewhere, leaving the powerful potential of the platform untapped.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
