<?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 F. Latini - IT Engineer</title><link>https://latini.dev/tags/platform-engineering/</link><description>Recent content in Platform-Engineering on F. Latini - IT Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 11 May 2026 11:00:00 +0000</lastBuildDate><atom:link href="https://latini.dev/tags/platform-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Are You Really Monitoring Your Infrastructure?</title><link>https://latini.dev/posts/are-you-really-monitoring-your-infrastructure/</link><pubDate>Mon, 11 May 2026 11:00:00 +0000</pubDate><guid>https://latini.dev/posts/are-you-really-monitoring-your-infrastructure/</guid><description>&lt;p&gt;Every engineering team I work with answers &amp;ldquo;yes, we have monitoring&amp;rdquo; before I&amp;rsquo;ve finished asking the question. Then I ask the follow-up: &lt;em&gt;the last time a customer hit a bug before you did, why?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;If you can&amp;rsquo;t answer that quickly, you don&amp;rsquo;t have monitoring. You have dashboards.&lt;/p&gt;
&lt;p&gt;This is the distinction worth getting right, because it determines whether you find out about problems on Tuesday afternoon or from a customer email at 2 a.m. on Saturday.&lt;/p&gt;</description></item><item><title>Is Kubernetes the Right Tool for You?</title><link>https://latini.dev/posts/is-kubernetes-the-right-tool-for-you/</link><pubDate>Mon, 11 May 2026 10:00:00 +0000</pubDate><guid>https://latini.dev/posts/is-kubernetes-the-right-tool-for-you/</guid><description>&lt;p&gt;I run Kubernetes for a living. I think you should probably &lt;em&gt;not&lt;/em&gt; use it.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s not a contradiction. Kubernetes is the right answer for a specific class of problem - multi-tenant, polyglot, heterogeneous workloads at meaningful scale. For most teams I meet, it&amp;rsquo;s a tax: a complex distributed system bolted onto a stack that didn&amp;rsquo;t need one, paid for in hiring, security, and &amp;ldquo;why is my Pod CrashLoopBackOff&amp;rdquo; Slack threads at 11 p.m.&lt;/p&gt;</description></item><item><title>What Is Platform Engineering? A Beginner's Guide</title><link>https://latini.dev/posts/platform-engineering-guide/</link><pubDate>Thu, 16 Jan 2025 21:06:34 +0000</pubDate><guid>https://latini.dev/posts/platform-engineering-guide/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; - Platform Engineering is about building an &lt;em&gt;internal product&lt;/em&gt; for your developers: paved roads, golden paths, and self-service workflows that reduce the cognitive load of getting code into production. It&amp;rsquo;s not DevOps with a new logo. It&amp;rsquo;s not SRE with extra steps. It&amp;rsquo;s a specific discipline with its own measurable goals.&lt;/p&gt;
&lt;h2 id="why-this-term-exists"&gt;
 Why this term exists
 &lt;a class="heading-link" href="#why-this-term-exists"&gt;
 &lt;i class="fa fa-link" aria-hidden="true"&gt;&lt;/i&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;A decade of &amp;ldquo;DevOps&amp;rdquo; produced two outcomes. In the best companies, it built a real culture of shared ownership between development and operations. In most companies, it produced a small team of overworked specialists called &amp;ldquo;DevOps engineers&amp;rdquo; who became a human bottleneck - ticket queues, YAML on demand, &amp;ldquo;can you give me access to&amp;hellip;&amp;rdquo; Slack messages at all hours.&lt;/p&gt;</description></item></channel></rss>