<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Ai-Strategy on Dr. Hitesh Sarda</title>
		<link>https://hitesh.in/tags/ai-strategy/</link>
		<description>Recent content in Ai-Strategy on Dr. Hitesh Sarda</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Sun, 15 Nov 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://hitesh.in/tags/ai-strategy/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Your AI-built prototype becomes a liability the day it holds real customer data</title>
				<link>https://hitesh.in/2026/ai-built-app-real-customer-data/</link>
				<pubDate>Sun, 15 Nov 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/ai-built-app-real-customer-data/</guid>
				<description>&lt;p&gt;In November, the security firm Crissy Field, working with the newspaper Handelsblatt, &lt;a href=&#34;https://www.crissyfield.de/research/lovable-en/&#34;&gt;published an analysis of 159,041 apps built on Lovable&lt;/a&gt;, the AI platform that turns plain-language descriptions into web applications. Of the 34,545 that used the Supabase database, 24,664 sent database records to any visitor&amp;rsquo;s browser as soon as the page loaded. In 7,403 of those, a few extra read-only requests returned tables containing email addresses.&lt;/p&gt;&#xA;&lt;p&gt;The authors are careful to say this is not a confirmed leak rate. Some of that data is meant to be public, and the sample is not representative. The examples they did find were not ambiguous: 80,000 forum profiles and 200,000 chat messages, tenant emails summarized by AI, and more than 1,000 records with passport numbers. No login, no exploit.&lt;/p&gt;</description>
			</item>
			<item>
				<title>A ban on AI agents is a statement about your margins</title>
				<link>https://hitesh.in/2026/ban-ai-agents-margin-statement/</link>
				<pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/ban-ai-agents-margin-statement/</guid>
				<description>&lt;p&gt;United Airlines has said it will &lt;a href=&#34;https://www.cbsnews.com/news/united-airlines-bans-ai-agents-booking-flights/&#34;&gt;prohibit unauthorized third-party personal AI agents&lt;/a&gt; from booking flights, on its own channels and through agencies and aggregators. Its stated reasons are sensible ones: handing account credentials to an assistant can expose sensitive information, an agent may buy something or spend MileagePlus miles the traveler never meant to, and some federal rules expect a human to confirm things like what is in their luggage. Meanwhile, according to the same report, Southwest has made its inventory viewable to ChatGPT users.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Be more ambitious with software, but only where you can prove it works</title>
				<link>https://hitesh.in/2026/ambition-needs-a-test-suite/</link>
				<pubDate>Tue, 10 Nov 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/ambition-needs-a-test-suite/</guid>
				<description>&lt;p&gt;A few weeks ago, an engineer I respect wrote that &lt;a href=&#34;https://danluu.com/ambitious/&#34;&gt;we should be more ambitious with the software we build&lt;/a&gt;. His evidence was personal: projects that once took a year or more, finished in a handful of hours with an AI agent doing the typing. I think the premise is right, and most leadership teams will draw the wrong conclusion from it.&lt;/p&gt;&#xA;&lt;p&gt;Ambition got cheap. Knowing whether the result is correct did not.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Your coding agent now takes instructions from your software vendors</title>
				<link>https://hitesh.in/2026/vendors-write-your-agents-instructions/</link>
				<pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/vendors-write-your-agents-instructions/</guid>
				<description>&lt;p&gt;On October 25 a developer &lt;a href=&#34;https://github.com/postmanlabs/postman-app-support/issues/14370&#34;&gt;opened an issue&lt;/a&gt; against Postman&amp;rsquo;s support repository. After an automatic update, the Postman desktop app had installed a CLI and plugins into their Codex and Claude Code setups. Postman&amp;rsquo;s own log reads &lt;code&gt;auto-existing-upgrade&lt;/code&gt;, with &lt;code&gt;claude-code:installed&lt;/code&gt; and &lt;code&gt;codex:installed&lt;/code&gt;. A session-start hook came along with them, whose text tells the agent to load a Postman skill &amp;ldquo;before responding to any non-trivial API engineering task.&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;Postman has since said the components are bundled because people struggled to install them separately, that it is disclosed on the download page and in the update flow, and that it is &lt;a href=&#34;https://github.com/postmanlabs/postman-app-support/issues/14370&#34;&gt;reviewing the hook approval and session-start behavior&lt;/a&gt;. The reporter is explicit that no data theft was shown, and I could not independently confirm the details beyond the issue and that thread. I don&amp;rsquo;t think Postman is the villain here. What matters is where this points for every other vendor.&lt;/p&gt;</description>
			</item>
			<item>
				<title>DoorDash is paying $17 billion for the part of Instacart an AI agent can&#39;t skip</title>
				<link>https://hitesh.in/2026/instacart-what-agents-cant-skip/</link>
				<pubDate>Fri, 30 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/instacart-what-agents-cant-skip/</guid>
				<description>&lt;p&gt;Instacart was valued at &lt;a href=&#34;https://www.cnbc.com/2021/03/02/instacarts-valuation-doubles-to-39-billion.html&#34;&gt;$39 billion&lt;/a&gt; in March 2021. It went public in 2023 at &lt;a href=&#34;https://www.euronews.com/business/2023/09/19/instacart-sets-ipo-price-at-30-a-share-valuing-the-company-at-about-10-billion&#34;&gt;about $10 billion&lt;/a&gt;. This week DoorDash agreed to &lt;a href=&#34;https://about.doordash.com/en-us/news/doordash-to-acquire-instacart&#34;&gt;buy it for roughly $17 billion&lt;/a&gt;, a 26% premium to where the stock traded before the talks leaked.&lt;/p&gt;&#xA;&lt;p&gt;Most of the coverage is about grocery market share and antitrust. I read it differently. The price is a buyer&amp;rsquo;s estimate of which part of Instacart stays scarce once software does the shopping, and every business that sells through an app or a website should be able to answer that question about itself.&lt;/p&gt;</description>
			</item>
			<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>Your best AI use case may not need a frontier model</title>
				<link>https://hitesh.in/2026/your-best-ai-use-case-may-not-need-a-frontier-model/</link>
				<pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/your-best-ai-use-case-may-not-need-a-frontier-model/</guid>
				<description>&lt;p&gt;Dermatologist Magnus Lynch showed &lt;a href=&#34;https://lynchlab.net/llm-skin-cancer&#34;&gt;200 biopsy-proven skin lesions&lt;/a&gt; to GPT-6 Astra and Claude Fable 5.1, then to a ten-year-old image network (Inception v3) fine-tuned for about twenty minutes on one GPU. The old network named the right diagnosis 62% of the time. Both frontier models got 42%.&lt;/p&gt;&#xA;&lt;p&gt;It is tempting to read that as a gotcha about LLMs. I think it is more useful as a procurement story, because it is what happens when a company picks the model first and the task second. Lynch himself says the old network is only a baseline, that regulated products do far better, and that 200 cases from a single run can&amp;rsquo;t rank close results. None of that weakens the lesson.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The open-weight model that was trained to know less about security</title>
				<link>https://hitesh.in/2026/open-weight-model-trained-to-know-less/</link>
				<pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/open-weight-model-trained-to-know-less/</guid>
				<description>&lt;p&gt;When Moonshot released &lt;a href=&#34;https://www.kimi.ai/blog/kimi-k3-1-pro&#34;&gt;Kimi K3.1 Pro&lt;/a&gt; this week, the benchmark table was the usual one: 65.7% on Terminal-Bench 4.0 against 66.4% for Claude Opus 5.5, a 1-million-token context window, weights promised by November 4. The line that matters for a buyer is further down. &amp;ldquo;For the open-weight release of K3.1 Pro, we identified and removed cyber-related data from both training stages.&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;They also published what it cost. Without the removal, the checkpoint solves 90.5% of their cyber benchmark problems at pass@3. The final model solves 81.0%. That is a vendor-reported number on a vendor-chosen benchmark, so treat it as a direction, not a measurement. But it is a rare thing: a lab telling you exactly how much capability it took out on purpose.&lt;/p&gt;</description>
			</item>
			<item>
				<title>LiteLLM was compromised twice in seven months. Here is what that means for your AI strategy</title>
				<link>https://hitesh.in/2026/your-ai-gateway-holds-every-key/</link>
				<pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/your-ai-gateway-holds-every-key/</guid>
				<description>&lt;p&gt;On Wednesday at 11:39 UTC, someone published LiteLLM 1.107.0 to PyPI. It was &lt;a href=&#34;https://securitylabs.datadoghq.com/articles/litellm-compromised-pypi-docker/&#34;&gt;quarantined at 13:20&lt;/a&gt;, so it was live for roughly two hours. In that window, anyone who ran &lt;code&gt;pip install litellm&lt;/code&gt; or pulled the &lt;code&gt;latest&lt;/code&gt; container image got a &lt;a href=&#34;https://safedep.io/litellm-pypi-compromise-credential-stealer-backdoor/&#34;&gt;credential stealer and a backdoor&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;LiteLLM is the open-source gateway many companies put between their applications and the model providers. One endpoint, virtual keys per team, spend tracking, routing across OpenAI, Anthropic and Bedrock. It was &lt;a href=&#34;https://www.netspi.com/blog/executive-blog/ai-ml-pentesting/litellm-supply-chain-compromise/&#34;&gt;compromised once before, in March&lt;/a&gt;, when it was pulling around 95 million downloads a month. Two incidents in seven months make this more than bad luck. They tell you where attackers think the value is.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Nobody has benchmarked AI on 90% of the work your company does</title>
				<link>https://hitesh.in/2026/nobody-benchmarked-your-work/</link>
				<pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/nobody-benchmarked-your-work/</guid>
				<description>&lt;p&gt;Mercor mapped 29 public AI benchmarks onto the US Department of Labor&amp;rsquo;s catalog of work, &lt;a href=&#34;https://www.onetonline.org/&#34;&gt;O*NET&lt;/a&gt;, which breaks 923 occupations into 18,797 tasks. Only &lt;a href=&#34;https://www.mercor.com/research/labor-index/benchmark-map/&#34;&gt;208 occupations have even one task with five or more benchmark prompts&lt;/a&gt;, and only 924 tasks are covered at all. Weighted by time, they estimate that about 90% of American working hours go to tasks with little or no benchmark coverage.&lt;/p&gt;&#xA;&lt;p&gt;Mercor says the numbers are provisional, and they are an estimate built on 29 benchmarks they chose. I would still treat the direction as reliable. It changes how I would read every AI claim that lands on an executive&amp;rsquo;s desk.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Most teams still ration AI that is cheap enough to waste</title>
				<link>https://hitesh.in/2026/ai-cheap-enough-to-waste/</link>
				<pubDate>Fri, 09 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/ai-cheap-enough-to-waste/</guid>
				<description>&lt;p&gt;One developer spent a month &lt;a href=&#34;https://www.dgt.is/blog/2026-10-07-deepseek-freek-out/&#34;&gt;using DeepSeek 4.1 Flash heavily across a dozen projects&lt;/a&gt; and reports that, mid-session, he can&amp;rsquo;t tell it from Opus. His day-long sessions rarely cost more than a dollar. That is one person&amp;rsquo;s subjective report, so weigh it that way. What I find more useful is the behavior he describes: &amp;ldquo;there is no shame now in spinning up mindless tasks,&amp;rdquo; including exploratory UI testing and tidying files, which costs $0.003 instead of $1.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The engineer who picks the model never sees the bill</title>
				<link>https://hitesh.in/2026/who-sees-the-ai-bill/</link>
				<pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/who-sees-the-ai-bill/</guid>
				<description>&lt;p&gt;Microsoft had projected at least $1 billion of internal spending on Anthropic this year. According to &lt;a href=&#34;https://aiweekly.co/alerts/meta-microsoft-scale-back-staff-use-of-anthropics-claude&#34;&gt;The Information&amp;rsquo;s reporting&lt;/a&gt;, that estimate has since been cut by more than a third. At Meta, internal Claude Code users have reportedly fallen from about 60,000 to about 30,000. Neither company has confirmed the numbers, and Microsoft&amp;rsquo;s customer-facing spending on Anthropic models is reportedly still growing.&lt;/p&gt;&#xA;&lt;p&gt;The obvious reading is rivalry. Both companies build competing models and coding tools, so of course they would rather their own engineers used those. That is probably true, and it explains why these two moved. It tells the rest of us very little, because most companies have no in-house model to move to. What the story does show is what happens to an AI budget that nobody was managing: it runs wide open for a year, then gets cut by decree.&lt;/p&gt;</description>
			</item>
			<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>Why Google&#39;s AI products feel broken despite its models</title>
				<link>https://hitesh.in/2026/best-ai-still-feels-broken/</link>
				<pubDate>Mon, 28 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/best-ai-still-feels-broken/</guid>
				<description>&lt;p&gt;Google&amp;rsquo;s search results have started doing things a trillion-dollar product should have grown out of years ago. Paste a quote from a book and it reads the sentence as something you personally believe. Ask about a specific page and it refuses to actually open the link, then makes up what&amp;rsquo;s probably on it. Search for an exact phrase, the one thing Google search reliably did for two decades, and it now returns fuzzy matches tuned for ad inventory instead. A &lt;a href=&#34;https://sancho.bearblog.dev/google-weird/&#34;&gt;widely discussed post&lt;/a&gt; catalogued a long list of these this week, and the comments added a sharper detail: a former Googler describing a culture where engineers are actively discouraged from talking to real users, so &amp;ldquo;ship without testing, iterate later&amp;rdquo; became the normal plan.&lt;/p&gt;</description>
			</item>
			<item>
				<title>450 million seats, 7% adoption: the real Copilot story</title>
				<link>https://hitesh.in/2026/the-copilot-reboot/</link>
				<pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/the-copilot-reboot/</guid>
				<description>&lt;p&gt;Two years ago Microsoft stood up a separate team, hired an outside AI veteran, Mustafa Suleyman, to run it, and gave the effort its own personality: a small animated character named Mico, a &amp;ldquo;Copilot Labs&amp;rdquo; for experiments, a feature for group chats with AI, another for AI-generated podcasts. The bet was that Microsoft could win a piece of the consumer AI-companion market the way OpenAI and Google were building one.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Three frontier labs shipped this week. Only one cut its price.</title>
				<link>https://hitesh.in/2026/frontier-models-read-the-prices/</link>
				<pubDate>Wed, 23 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/frontier-models-read-the-prices/</guid>
				<description>&lt;p&gt;In the space of two days this week, three frontier labs updated their flagship line. Anthropic shipped &lt;a href=&#34;https://www.anthropic.com/claude-opus-5-5&#34;&gt;Claude Opus 5.5&lt;/a&gt; on September 22: 20% cheaper on input and output, 60% cheaper on cached reads, 30% faster, with real but incremental gains on agentic coding and computer-use benchmarks. OpenAI shipped &lt;a href=&#34;https://www.unite.ai/openai-introduces-gpt-6-sol-and-luna-with-50-lower-api-prices/&#34;&gt;GPT-6 Sol and Luna&lt;/a&gt; the same day, extending September&amp;rsquo;s GPT-6 Astra down into faster, cheaper tiers at roughly half of what the equivalent GPT-5.6 models cost. xAI shipped &lt;a href=&#34;https://www.digitalapplied.com/blog/grok-4-7-benchmarks-price-what-changed&#34;&gt;Grok 4.7&lt;/a&gt; a day earlier, ahead of its predecessor on most evaluations, though not all: Anthropic&amp;rsquo;s own Fable 5.1 Max still leads it on several coding and long-task tests.&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>Gemini broke into three companies by guessing passwords</title>
				<link>https://hitesh.in/2026/the-attacker-just-got-cheap/</link>
				<pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/the-attacker-just-got-cheap/</guid>
				<description>&lt;p&gt;In May, Google&amp;rsquo;s Gemini broke into three real companies. It wasn&amp;rsquo;t supposed to. &lt;a href=&#34;https://www.reuters.com/business/gemini-hacked-three-companies-first-known-breakout-by-google-ai-wsj-reports-2026-09-18/&#34;&gt;Google confirmed last week&lt;/a&gt; that during a security test run by the firm Irregular, the model was given a capture-the-flag exercise against a fictional target. The fake company happened to share its name with a real one, Gemini took the exercise out onto the live internet, and it got in. Google&amp;rsquo;s VP for security engineering &lt;a href=&#34;https://www.nbcnews.com/tech/tech-news/google-says-ai-model-gained-unauthorized-access-three-systems-rcna598651&#34;&gt;said&lt;/a&gt; the model &amp;ldquo;found public information online and guessed credentials.&amp;rdquo; In two of the three cases it used login details sitting in public code repositories. In the third it guessed passwords until one worked.&lt;/p&gt;</description>
			</item>
			<item>
				<title>AI deleted your excuse for missing fraud</title>
				<link>https://hitesh.in/2026/ai-killed-the-scale-excuse/</link>
				<pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/ai-killed-the-scale-excuse/</guid>
				<description>&lt;p&gt;A developer clicked a fake &amp;ldquo;iPhone Storage is Full&amp;rdquo; ad served through Google, reported it, and got back a note saying the ad complied with Google&amp;rsquo;s policies. He reported it again. Same answer. Then he &lt;a href=&#34;https://www.atomic14.com/2026/09/13/why-is-google-still-serving-dodgy-ads&#34;&gt;pasted the ad into Gemini&lt;/a&gt;, Google&amp;rsquo;s own model, and asked it to review the thing. Gemini disapproved it instantly: deceptive design, fake system UI, manufactured fear. Every violation was already in Google&amp;rsquo;s published policy.&lt;/p&gt;&#xA;&lt;p&gt;The obvious reading is that Google makes money from ads and loses money by removing them. That is true, and I have written before about how &lt;a href=&#34;https://hitesh.in/2026/ai-incentive-amplifier/&#34;&gt;AI amplifies whatever your scoreboard already rewards&lt;/a&gt;. But the incentive story is the old story. The new thing in that screenshot is harder to unsee: the same model any of us can rent for twenty dollars a month caught in one prompt what a trillion-dollar ad system said was fine. That does not just embarrass Google. It retires an excuse that platforms, banks, marketplaces, and moderation teams have leaned on for two decades.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Your next customer might be an AI agent, not a person</title>
				<link>https://hitesh.in/2026/your-next-customer-is-an-agent/</link>
				<pubDate>Wed, 09 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/your-next-customer-is-an-agent/</guid>
				<description>&lt;p&gt;Meta &lt;a href=&#34;https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/&#34;&gt;launched Muse&lt;/a&gt; this week, a personal AI agent that books your travel, pays bills through Stripe, orders online, and manages your calendar by reading your email, all from inside WhatsApp, an app with more than two billion users. Most of the coverage focused on how much of your life you&amp;rsquo;d have to hand Meta to get any of that, a fair question given the &lt;a href=&#34;https://techcrunch.com/2026/09/08/meta-debuts-its-muse-ai-agent-will-consumers-trust-it/&#34;&gt;$5 billion FTC penalty and $18 billion privacy settlement&lt;/a&gt; already on the record. It is not, I think, the question that should keep a founder or CTO up at night.&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>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>AI just put a price on clever code</title>
				<link>https://hitesh.in/2026/price-on-clever-code/</link>
				<pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/price-on-clever-code/</guid>
				<description>&lt;p&gt;Google published a post last week arguing that &lt;a href=&#34;https://developers.googleblog.com/why-go-is-an-ideal-language-for-ai-assisted-software-engineering/&#34;&gt;Go is an ideal language for AI-assisted software engineering&lt;/a&gt;. The reflex reaction wrote itself: Go is Google&amp;rsquo;s language, so of course Google thinks you should use it. Fair enough. But the conclusion is the least interesting part. Strip the word &amp;ldquo;Go&amp;rdquo; out of the argument and what remains is a claim about legibility that applies to every stack you run, and it quietly settles a fight engineering teams have been having for twenty years.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Your real AI advantage is how fast your company learns</title>
				<link>https://hitesh.in/2026/how-fast-your-company-learns/</link>
				<pubDate>Mon, 10 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/how-fast-your-company-learns/</guid>
				<description>&lt;p&gt;There is a short post going around about &lt;a href=&#34;https://laurentiugabriel.github.io/blog/articles/how-i-use-llms-to-learn/&#34;&gt;how one developer uses LLMs to learn hard topics&lt;/a&gt;. His method is better than the usual &amp;ldquo;explain it like I&amp;rsquo;m five.&amp;rdquo; He has the model assemble a foundation, then asks it to check its own account for mistakes, then turns the whole thing into a small interactive simulation he has to operate himself. The summaries were never the point. The reconstruction was.&lt;/p&gt;&#xA;&lt;p&gt;I read it as a founder rather than a student, and it pointed at something most AI-at-work conversations skip. We keep asking what AI can produce. The more valuable question inside a company is what AI lets people understand, and how quickly.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Name the axis you&#39;re willing to lose on</title>
				<link>https://hitesh.in/2026/name-the-axis/</link>
				<pubDate>Fri, 07 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/name-the-axis/</guid>
				<description>&lt;p&gt;A hundred-year-old economics idea spent this week near the top of the tech feeds, explained through Mario Kart of all things. It is a &lt;a href=&#34;https://www.mayerowitz.io/blog/mario-meets-pareto&#34;&gt;good explainer&lt;/a&gt; and worth ten minutes. But the reason it matters to anyone who makes technology decisions has nothing to do with karts. It is that the Pareto frontier is the cleanest tool I know for catching the most common waste in a strategy meeting: a long argument about an option that was never worth choosing.&lt;/p&gt;</description>
			</item>
			<item>
				<title>AI won&#39;t have your next idea</title>
				<link>https://hitesh.in/2026/ai-wont-have-your-next-idea/</link>
				<pubDate>Thu, 06 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/ai-wont-have-your-next-idea/</guid>
				<description>&lt;p&gt;Tom Zahavy, a researcher at Google DeepMind who worked on &lt;a href=&#34;https://deepmind.google/discover/blog/ai-solves-imo-problems-at-silver-medal-level/&#34;&gt;AlphaProof&lt;/a&gt;, published a &lt;a href=&#34;https://www.tomzahavy.com/projects/llms-cant-jump&#34;&gt;position paper&lt;/a&gt; with a title that reads like a shrug: &amp;ldquo;LLMs can&amp;rsquo;t jump.&amp;rdquo; The argument underneath is one every executive placing AI bets should sit with for a minute.&lt;/p&gt;&#xA;&lt;p&gt;He borrows a distinction the philosopher &lt;a href=&#34;https://en.wikipedia.org/wiki/Abductive_reasoning&#34;&gt;Charles Sanders Peirce&lt;/a&gt; drew more than a century ago. Reasoning comes in three modes. Induction finds patterns in data. Deduction works out the consequences of rules you already hold. Abduction is the odd one: the leap from a pile of observations to a new explanation that was not sitting inside them. Zahavy&amp;rsquo;s claim is that models have gotten very good at the first two and cannot do the third, and that no amount of scaling or clever prompting closes the gap.&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>
			<item>
				<title>The AI gave better advice to people who needed it least</title>
				<link>https://hitesh.in/2026/ai-advice-needed-it-least/</link>
				<pubDate>Sun, 02 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/ai-advice-needed-it-least/</guid>
				<description>&lt;p&gt;A team at MIT Sloan and Stanford ran a study I keep thinking about. They asked 1,000 adults to write their own prompts asking a language model for financial advice, then &lt;a href=&#34;https://mitsloan.mit.edu/ideas-made-to-matter/ai-financial-advice-surprisingly-good-especially-if-you-ask-right-questions&#34;&gt;simulated what would happen&lt;/a&gt; if people aged 22 to 89 followed that advice across a lifetime. The headline is cheerful: the advice was good. It pushed people to save more, hold stocks, diversify, and take less risk as they aged. The lead researcher said the team was &amp;ldquo;somewhat surprised by how good the advice was.&amp;rdquo;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Point your AI where the checking is cheap</title>
				<link>https://hitesh.in/2026/point-ai-where-checking-is-cheap/</link>
				<pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/point-ai-where-checking-is-cheap/</guid>
				<description>&lt;p&gt;Last week Anthropic published something that should reframe how you decide where to put AI to work. An agentic system it calls Claude Mythos Preview &lt;a href=&#34;https://www.anthropic.com/research/discovering-cryptographic-weaknesses&#34;&gt;found a genuinely new weakness&lt;/a&gt; in HAWK, a post-quantum signature scheme that had sat under NIST review for two years without anyone spotting it, and separately produced a faster attack on a reduced version of AES. The AES run went for roughly a week, mostly unsupervised, and cost about $100,000 in compute. Then human cryptographers spent close to a month confirming the result was real.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Your scoreboard is making AI-written software worse</title>
				<link>https://hitesh.in/2026/ai-incentive-amplifier/</link>
				<pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/ai-incentive-amplifier/</guid>
				<description>&lt;p&gt;Most people I talk to hold two thoughts at once and don&amp;rsquo;t notice the tension. The first is that AI has made writing code almost free. The second is that the software they actually use keeps getting worse: the banking app that asks for a fingerprint three times, the car screen that lags, the SaaS tool that ships a new button every week and a fresh bug alongside it. Both are true. The gap between them is the most interesting thing happening in software right now, and it is not a technology problem.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Your AI only knows what someone bothered to write down</title>
				<link>https://hitesh.in/2026/the-commons-that-trained-your-ai/</link>
				<pubDate>Sun, 19 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/the-commons-that-trained-your-ai/</guid>
				<description>&lt;p&gt;In December 2025, developers asked Stack Overflow 3,862 questions in the entire month. At its 2014 peak the site took &lt;a href=&#34;https://www.devclass.com/ai-ml/2026/01/05/dramatic-drop-in-stack-overflow-questions-as-devs-look-elsewhere-for-help/4079575&#34;&gt;more than 200,000 a month&lt;/a&gt;. December&amp;rsquo;s figure was a 78 percent fall from the year before, and it puts activity near where the site sat in 2008, its first year. The line on that chart does not sag. It falls off a table.&lt;/p&gt;&#xA;&lt;p&gt;The easy reading is that AI won, a clunky forum lost, and good riddance to the snark. I think that misses the useful part. The models that replaced Stack Overflow learned to code by reading Stack Overflow. The thing that made them good is the thing they are now starving. If you build a company on top of these models, that is not a nostalgia story. It is a question about where your knowledge comes from next.&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>
	</channel>
</rss>
