<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Build-vs-Buy on Dr. Hitesh Sarda</title>
		<link>https://hitesh.in/tags/build-vs-buy/</link>
		<description>Recent content in Build-vs-Buy on Dr. Hitesh Sarda</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Sat, 03 Oct 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://hitesh.in/tags/build-vs-buy/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Rent the AI harness. Own what it learns.</title>
				<link>https://hitesh.in/2026/rent-the-harness-own-what-it-learns/</link>
				<pubDate>Sat, 03 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/rent-the-harness-own-what-it-learns/</guid>
				<description>&lt;p&gt;Shrivu Shankar argues that &lt;a href=&#34;https://blog.sshh.io/p/the-harness-is-the-company&#34;&gt;every SaaS business will become a harness around a model&lt;/a&gt;: the infrastructure, interfaces, context and state wrapped around an LLM that has no memory of its own. In his telling, companies move from engineers pairing with agents, to humans triggering background agents, to a harness that runs work proactively while people sample the output. His conclusion is that the harness stops being a tool you buy and becomes something you no more outsource than your product team or your sales team.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Cheap to fork, costly to keep: AI redraws build versus buy</title>
				<link>https://hitesh.in/2026/cheap-to-fork-costly-to-keep/</link>
				<pubDate>Tue, 04 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/cheap-to-fork-costly-to-keep/</guid>
				<description>&lt;p&gt;The argument that &lt;a href=&#34;https://blog.exe.dev/devtools-must-be-open-source&#34;&gt;developer tools must now be open source&lt;/a&gt; rests on a small, concrete observation: an AI agent can fork an open-source tool, bend it to fit exactly how you work, and then run a nightly rebase that folds upstream updates into your version while you sleep. Customizing software used to be a project you staffed. Now it&amp;rsquo;s a prompt you write once. The author keeps the point aimed at developer tools. I think it reaches the oldest decision in enterprise software, and moves it.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
