<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Engineering-Leadership on F. Latini - IT Engineer</title>
    <link>https://latini.dev/tags/engineering-leadership/</link>
    <description>Recent content in Engineering-Leadership on F. Latini - IT Engineer</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 24 Jul 2026 08:00:00 +0000</lastBuildDate>
    <atom:link href="https://latini.dev/tags/engineering-leadership/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Build vs Buy Is the Wrong Question</title>
      <link>https://latini.dev/posts/build-vs-buy-is-the-wrong-question/</link>
      <pubDate>Fri, 24 Jul 2026 08:00:00 +0000</pubDate>
      <guid>https://latini.dev/posts/build-vs-buy-is-the-wrong-question/</guid>
      <description>&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; - &amp;ldquo;Should we build our own platform or buy one?&amp;rdquo; is the wrong question, and the spreadsheet that answers it is lying to you. It lies by comparing the annual license of the thing you&amp;rsquo;d buy against a one-time construction estimate for the thing you&amp;rsquo;d build - as if software you build is a purchase rather than a perpetual staffing commitment. Every platform is already part-built and part-bought; the only decision that matters is &lt;em&gt;where you draw the line&lt;/em&gt;. Draw it in one place: buy the undifferentiated substrate, because it is a commodity someone else operates better than you, and build only the thin layer of opinion that is actually yours - the paved roads, the defaults, the glue that encodes how your teams ship. Then fund the built part like a product, forever, not like a project you finish. The teams that get this wrong build the commodity and buy the differentiation, which is exactly backwards.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
