<?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 F. Latini - IT Engineer</title><link>https://latini.dev/tags/backstage/</link><description>Recent content in Backstage on F. Latini - IT Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 22 Jun 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://latini.dev/tags/backstage/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Developer Portal Is a Trap (Until It Isn't)</title><link>https://latini.dev/posts/your-developer-portal-is-a-trap/</link><pubDate>Mon, 22 Jun 2026 08:00:00 +0000</pubDate><guid>https://latini.dev/posts/your-developer-portal-is-a-trap/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; - A developer portal is the index of your paved roads, and almost nobody should build the index before they have the book. Standing up &lt;a href="https://backstage.io/"&gt;Backstage&lt;/a&gt; as your &lt;em&gt;first&lt;/em&gt; platform move gives you an empty catalogue, a maintenance burden, and a demo that impresses leadership while helping zero developers. You earn a portal once discovery is a real problem - roughly the &lt;a href="https://latini.dev/posts/platform-engineering-guide/"&gt;~30-services&lt;/a&gt; mark the pillar names, several paved roads worth cataloguing, and ownership data someone actually maintains. Before that, a boring markdown catalogue does the same job for a thousandth of the cost. This is the post-script to &lt;a href="https://latini.dev/posts/building-your-first-golden-path/"&gt;building your first golden path&lt;/a&gt;: what comes after the road, and why it isn&amp;rsquo;t the portal.&lt;/p&gt;</description></item></channel></rss>