<?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 Santiago Hurtado | System Architect</title><link>/tags/platform-engineering/</link><description>Recent content in Platform Engineering on Santiago Hurtado | System Architect</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 17 May 2026 17:40:37 +0200</lastBuildDate><atom:link href="/tags/platform-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Engineering Beyond Delivery: Shared Responsibility for Outcomes</title><link>/posts/engineering-outcomes-shared-responsibility/</link><pubDate>Sun, 17 May 2026 17:40:37 +0200</pubDate><guid>/posts/engineering-outcomes-shared-responsibility/</guid><description>&lt;h2 id="the-isolation-pattern" class="relative group"&gt;The Isolation Pattern &lt;span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100"&gt;&lt;a class="group-hover:text-primary-300 dark:group-hover:text-neutral-700" style="text-decoration-line: none !important;" href="#the-isolation-pattern" aria-label="Anchor"&gt;#&lt;/a&gt;&lt;/span&gt;&lt;/h2&gt;&lt;p&gt;Engineers are trained to execute. You get user stories, requirements, and acceptance criteria, then deliver against them. The system should handle X concurrent users, scale to Y nodes, and respond in under Z milliseconds. Those are real constraints, and meeting them takes serious work.&lt;/p&gt;
&lt;p&gt;But here is the question nobody asks enough: how many devices in the field are actually running the latest version, and how many users actively use what we built? What does success look like for the product, not just for the current sprint?&lt;/p&gt;</description></item><item><title>What is a Platform? Infrastructure as a Product</title><link>/posts/what-is-a-platform/</link><pubDate>Sun, 10 May 2026 14:30:00 +0200</pubDate><guid>/posts/what-is-a-platform/</guid><description>&lt;p&gt;In the world of engineering, we often talk about &amp;ldquo;systems&amp;rdquo; and &amp;ldquo;products,&amp;rdquo; but the real differentiator for scaling is the &lt;strong&gt;Platform&lt;/strong&gt;. As teams grow and systems become more complex, shifting from manual setup to a structured, product-centric approach is essential.&lt;/p&gt;
&lt;p&gt;






 
 
&lt;figure&gt;&lt;img src="/img/concept-1868728_640.jpg" alt="platform-concept" class="mx-auto my-0 rounded-md" /&gt;
&lt;/figure&gt;

&lt;em&gt;Image by Pexels from Pixabay&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="defining-the-platform-infrastructure-as-a-product" class="relative group"&gt;Defining the Platform: Infrastructure as a Product &lt;span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100"&gt;&lt;a class="group-hover:text-primary-300 dark:group-hover:text-neutral-700" style="text-decoration-line: none !important;" href="#defining-the-platform-infrastructure-as-a-product" aria-label="Anchor"&gt;#&lt;/a&gt;&lt;/span&gt;&lt;/h2&gt;&lt;p&gt;A platform is more than just a set of tools. It is a &lt;strong&gt;reliable way to ship software&lt;/strong&gt; that handles the difficult parts of the infrastructure for you.&lt;/p&gt;</description></item></channel></rss>