<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Leadership on Dr. Hitesh Sarda</title>
		<link>https://hitesh.in/tags/leadership/</link>
		<description>Recent content in Leadership on Dr. Hitesh Sarda</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Tue, 27 Oct 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://hitesh.in/tags/leadership/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Microsoft is trading payroll for compute. Anthropic&#39;s S-1 is the other side of the trade</title>
				<link>https://hitesh.in/2026/payroll-for-compute/</link>
				<pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/payroll-for-compute/</guid>
				<description>&lt;p&gt;On Monday Microsoft &lt;a href=&#34;https://www.businessinsider.com/microsoft-is-offering-buyouts-read-the-memo-2026-10&#34;&gt;offered voluntary exits&lt;/a&gt; to about 60,000 employees, more than a quarter of the company, at level 70 and below in the US, Canada, India and the UK. The same week, Anthropic&amp;rsquo;s &lt;a href=&#34;https://www.sec.gov/Archives/edgar/data/2130357/000162828026067168/anthropicpbc-sx1.htm&#34;&gt;S-1&lt;/a&gt; showed revenue of $4.6 billion for all of 2025 and $16.3 billion for the first six months of 2026. Six months of this year earned more than three times what all of last year did.&lt;/p&gt;&#xA;&lt;p&gt;The memo does not mention AI. Business Insider links the two, noting that Microsoft has been spending heavily on AI infrastructure and reducing headcount at the same time. That is a reporter&amp;rsquo;s inference and so is what follows, but I think it is a reasonable one: a large company is converting payroll into compute, and the S-1 is a look at the other side of that trade.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The most dangerous postmortem is the one that makes sense</title>
				<link>https://hitesh.in/2026/dangerous-postmortem-makes-sense/</link>
				<pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/dangerous-postmortem-makes-sense/</guid>
				<description>&lt;p&gt;Michael Heap tells a story about an SVP who, five minutes into a detailed incident readout, stopped the meeting. &amp;ldquo;I already believe you did your best,&amp;rdquo; he said. &amp;ldquo;Now let&amp;rsquo;s talk about what happens next.&amp;rdquo; No interest in the timeline, no interrogation of who missed what. Heap &lt;a href=&#34;https://michaelheap.com/i-dont-want-the-details/&#34;&gt;wrote it up&lt;/a&gt; as a case for skipping the details, and the reaction split almost exactly down the middle: half the readers called it real leadership, delegation done right; half called it an executive signing off on fixes he had no way to evaluate. Both camps are arguing about trust. I think they are missing the more useful question, which is why a good explanation feels like enough in the first place, when it so rarely is.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Some writing is thinking. Automate the rest.</title>
				<link>https://hitesh.in/2026/some-writing-is-thinking/</link>
				<pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/some-writing-is-thinking/</guid>
				<description>&lt;p&gt;Two people who agree on almost nothing about AI just landed on the same rule for writing with it.&lt;/p&gt;&#xA;&lt;p&gt;Thomas Ptacek is one of the loudest public defenders of building software with language models. Erich Grunewald wrote a piece this month arguing, plainly, that &lt;a href=&#34;https://erichgrunewald.substack.com/p/why-you-should-almost-never-use-ai&#34;&gt;you should almost never use AI to write&lt;/a&gt;. Ptacek says &lt;a href=&#34;https://sockpuppet.org/blog/2026/09/17/how-to-write-with-an-llm/&#34;&gt;use the model but never as a ghostwriter&lt;/a&gt;: treat it as a copyeditor, and don&amp;rsquo;t keep a single word it suggests. Grunewald says don&amp;rsquo;t hand it the draft in the first place, though he&amp;rsquo;s fine with it editing one you wrote. Take the heat out of both and you get the same line. The model can polish your prose, but the sentences have to start as yours.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Who sits in the meeting when AI writes the memo?</title>
				<link>https://hitesh.in/2026/ai-cant-sit-in-the-meeting/</link>
				<pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/ai-cant-sit-in-the-meeting/</guid>
				<description>&lt;p&gt;Bryan Cantrill has a good phrase for the person who pastes a language model&amp;rsquo;s output onto LinkedIn and hits publish: &lt;a href=&#34;https://bcantrill.dtrace.org/2025/12/05/your-intellectual-fly-is-open/&#34;&gt;their intellectual fly is open&lt;/a&gt;. Everyone in the room can see it. The author is the only one who can&amp;rsquo;t. The emojis, the single-sentence paragraphs, the &amp;ldquo;it&amp;rsquo;s not just X, it&amp;rsquo;s Y&amp;rdquo; cadence. The tells are consistent enough that readers stop reading your argument and start reading the machine.&lt;/p&gt;&#xA;&lt;p&gt;I agree with him. But I think the fixation on the tells points people at the wrong problem. Clean up the tells with a better model or a careful editing pass, and the deeper exposure is still there. It just goes quiet until the moment it matters.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Beyond the Chatbox: The Rise of the Sovereign Engineer</title>
				<link>https://hitesh.in/2026/beyond-the-chatbox-the-rise-of-the-sovereign-engineer/</link>
				<pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/beyond-the-chatbox-the-rise-of-the-sovereign-engineer/</guid>
				<description>&lt;p&gt;For most of my career, engineers were measured by how fast and how well they could implement. Know the framework. Optimise the query. Debug the production incident. Architect the system. Those skills still matter, but they have stopped being where the value sits.&lt;/p&gt;&#xA;&lt;p&gt;AI has changed the economics of building software. Working code is becoming abundant and close to free. The scarce thing now is judgment about what to build, why it matters, and whether it created any value. I have started calling the person who owns that judgment a &lt;em&gt;sovereign engineer&lt;/em&gt;: someone accountable for the outcome, from &amp;ldquo;should we build this at all&amp;rdquo; through &amp;ldquo;did it actually work.&amp;rdquo;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Information Overload</title>
				<link>https://hitesh.in/2021/information-overload/</link>
				<pubDate>Wed, 28 Jul 2021 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2021/information-overload/</guid>
				<description>&lt;p&gt;There is a deluge of knowledge today. On platforms like YouTube and LinkedIn, there are so many thought leaders who could be followed for great insights. But how do you absorb, retain and apply this knowledge? This has become the real challenge.&lt;/p&gt;&#xA;&lt;h3 id=&#34;my-2-part-system-for-knowledge-management&#34;&gt;My 2 part system for knowledge management&lt;/h3&gt;&#xA;&lt;p&gt;1.&lt;strong&gt;Store and Index.&lt;/strong&gt; No, I am not building a knowledge base, database, or even write things done (which I should!). I tend to commit things to memory. What is important is to be able to recall on demand.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
