<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Opinion on Dr. Hitesh Sarda</title>
		<link>https://hitesh.in/tags/opinion/</link>
		<description>Recent content in Opinion on Dr. Hitesh Sarda</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Sun, 16 Aug 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://hitesh.in/tags/opinion/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>AI turned every engineer into a manager. Nobody trained the managers.</title>
				<link>https://hitesh.in/2026/every-engineer-a-manager/</link>
				<pubDate>Sun, 16 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/every-engineer-a-manager/</guid>
				<description>&lt;p&gt;Someone whose code I respect wrote this month that &lt;a href=&#34;https://allen.bargi.org/notes/working-with-ai-feels-like-leadership/&#34;&gt;working with AI feels more like leadership than coding&lt;/a&gt;. You stop issuing precise instructions and start setting context, giving examples, correcting, explaining why the work matters. It rang true. Most of my hands-on time with agents lately has felt less like typing and more like running a very fast junior developer who never gets tired and never quite gets it right.&lt;/p&gt;&#xA;&lt;p&gt;The framing is flattering, which is the first reason to be suspicious of it. It tells every engineer that the skill they have been building on the side, telling other people what to do, is suddenly the scarce one. Maybe. But &amp;ldquo;leadership&amp;rdquo; smuggles in a promise the tool can&amp;rsquo;t keep, and it hides the one management failure mode this shift is about to spread through every engineering org.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Boring technology is an AI strategy</title>
				<link>https://hitesh.in/2026/boring-technology-is-an-ai-strategy/</link>
				<pubDate>Fri, 14 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/boring-technology-is-an-ai-strategy/</guid>
				<description>&lt;p&gt;Dan McKinley&amp;rsquo;s 2015 essay &lt;a href=&#34;https://mcfunley.com/choose-boring-technology&#34;&gt;Choose Boring Technology&lt;/a&gt; climbed back onto engineers&amp;rsquo; feeds this week, sitting a few lines above a new frontier model and a faster coding agent. That juxtaposition is the whole argument. The oldest idea on the page is the most useful one for the newest problem on it.&lt;/p&gt;&#xA;&lt;p&gt;McKinley&amp;rsquo;s claim is simple. A company has roughly three innovation tokens to spend, and every genuinely novel piece of technology you adopt costs one. New tools aren&amp;rsquo;t bad; you just don&amp;rsquo;t yet know their failure modes, and finding them out is expensive. Boring technology, in his sense, is not dull technology. It is technology whose ways of breaking you already understand. MySQL, Postgres, a queue you have run for years. You spend a token when a problem is important enough that the boring option genuinely cannot solve it, and you spend it deliberately, because you only get a few.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The hidden bill for cheap automation is understanding</title>
				<link>https://hitesh.in/2026/automation-is-cheap-understanding-is-the-bill/</link>
				<pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/automation-is-cheap-understanding-is-the-bill/</guid>
				<description>&lt;p&gt;A recent arXiv paper by the mathematician Jun-Yong Park, &lt;a href=&#34;https://arxiv.org/abs/2607.06377&#34;&gt;Automation Without Understanding&lt;/a&gt;, opens with an uncomfortable moment: the May 2026 disproof of a longstanding Erdős conjecture on unit distances in the plane, produced by an AI system, in a form few mathematicians could actually follow. The proof checks out. The understanding behind it does not sit in any human head. Park&amp;rsquo;s worry is that a field can keep producing results while quietly losing the capacity to interpret, verify, and challenge them, and that this capacity takes generations to build and no time at all to lose.&lt;/p&gt;</description>
			</item>
			<item>
				<title>AI does your hardest work, not your messiest</title>
				<link>https://hitesh.in/2026/hardest-work-not-messiest/</link>
				<pubDate>Sat, 11 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/hardest-work-not-messiest/</guid>
				<description>&lt;p&gt;This week OpenAI published what it says is a &lt;a href=&#34;https://cdn.openai.com/pdf/04d1d1e4-bc75-476a-97cf-49055cd98d31/cdc_proof.pdf&#34;&gt;proof of the Cycle Double Cover Conjecture&lt;/a&gt;, a problem in graph theory that has sat open since the 1970s, produced by a frontier model left to grind on it with a swarm of subagents. Mathematicians are still working through whether it holds. Set that next to a smaller, less glamorous fact: the same class of model, pointed at a mid-size company&amp;rsquo;s month-end close or a two-step refund exception, still needs a human watching every move. Those two facts together break the assumption most leadership teams are quietly planning around.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The code you can&#39;t explain</title>
				<link>https://hitesh.in/2026/the-code-you-cant-explain/</link>
				<pubDate>Wed, 24 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/the-code-you-cant-explain/</guid>
				<description>&lt;p&gt;Velocity is up, defects are stable, deployments are more frequent. Ask who in the team could refactor the payment module from scratch, and the room goes quiet. The understanding that used to build up through the act of writing has been offloaded somewhere faster and less visible.&lt;/p&gt;&#xA;&lt;p&gt;Armin Ronacher wrote about this last week in &lt;a href=&#34;https://lucumr.pocoo.org/2026/6/23/the-coming-loop/&#34;&gt;a piece about what he calls &amp;ldquo;the coming loop&amp;rdquo;&lt;/a&gt;. His technical concern is specific: AI harnesses that drive coding agents past their natural stopping points, cycling until something passes a test, tend to produce code that is defensive, patchy, and local in its reasoning. Present-day agents add null checks rather than eliminating bad states through strong types; they patch locally rather than preventing the class of problem at the source. But the discussion his post sparked turned personal fast.&lt;/p&gt;</description>
			</item>
			<item>
				<title>When the AI Passes Every Test and Still Gets It Wrong</title>
				<link>https://hitesh.in/2026/when-ai-passes-every-test-and-still-gets-it-wrong/</link>
				<pubDate>Thu, 11 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/when-ai-passes-every-test-and-still-gets-it-wrong/</guid>
				<description>&lt;p&gt;In early March 2026, Amazon&amp;rsquo;s retail site fell over repeatedly, and &lt;a href=&#34;https://oecd.ai/en/incidents/2026-03-10-01aa&#34;&gt;internal documents tied the outages to AI-assisted code changes&lt;/a&gt;. The worst, on March 5, took the site down for about six hours and dropped orders by roughly 99%, an estimated 6.3 million that never happened. A few days earlier, a separate AI-assisted change had quietly started showing customers the wrong delivery dates. That code compiled. It passed review. It shipped.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
