<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Software-Engineering on Dr. Hitesh Sarda</title>
		<link>https://hitesh.in/tags/software-engineering/</link>
		<description>Recent content in Software-Engineering on Dr. Hitesh Sarda</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Tue, 17 Nov 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://hitesh.in/tags/software-engineering/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Your rollback window has an expiry date</title>
				<link>https://hitesh.in/2026/rollback-window-expires/</link>
				<pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/rollback-window-expires/</guid>
				<description>&lt;p&gt;Microsoft&amp;rsquo;s &lt;a href=&#34;https://www.theregister.com/saas/2026/11/16/microsoft-blames-monster-email-outage-on-software-defect-introduced-in-july-fix/5310026&#34;&gt;preliminary report on last week&amp;rsquo;s Microsoft 365 outage&lt;/a&gt;, as The Register summarizes it, traces the failure to a change made in July. That change passed load testing and ran for months without incident. On November 12, a Teams failover and a stretch of reduced capacity pushed the network gateways into a lock-contention defect, and within two hours more than 80 percent of the servers were unresponsive. Exchange Online was down for most of a day. I could not find the primary report in time to read it myself, so I&amp;rsquo;m relying on that account for the details.&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 release date assumed bugs were hard to find</title>
				<link>https://hitesh.in/2026/release-date-assumed-bugs-were-hard-to-find/</link>
				<pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/release-date-assumed-bugs-were-hard-to-find/</guid>
				<description>&lt;p&gt;For a decade, PostgreSQL major releases have landed between mid-September and mid-October. &lt;a href=&#34;http://rhaas.blogspot.com/2026/10/postgres-19-is-late-and-its-ais-fault.html&#34;&gt;Postgres 19 will most likely ship in November&lt;/a&gt;, and between August 27 and September 15 the project pulled three large features it had planned to include: UPDATE/DELETE FOR PORTION OF, SQL property graph queries, and partition merge and split. Robert Haas, a long-time Postgres committer, gives the cause in one line: &amp;ldquo;The short answer is that LLMs happened.&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;The code did not get worse. It got looked at. The bugs were always there, and what changed, in his words, is that it has become &amp;ldquo;vastly easier to find those bugs.&amp;rdquo; I think that sentence applies well beyond databases.&lt;/p&gt;</description>
			</item>
			<item>
				<title>A vendor&#39;s rounding error can be your outage</title>
				<link>https://hitesh.in/2026/vendors-rounding-error-your-outage/</link>
				<pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/vendors-rounding-error-your-outage/</guid>
				<description>&lt;p&gt;On November 17, Chrome 158 stops running XSLT for everyone except sites on an origin trial and enterprises with a policy exemption. Chrome&amp;rsquo;s own &lt;a href=&#34;https://developer.chrome.com/docs/web-platform/deprecating-xslt&#34;&gt;deprecation notice&lt;/a&gt; puts the feature at about 0.02% of page loads. By any aggregate measure it is a rounding error.&lt;/p&gt;&#xA;&lt;p&gt;If you are in the other 99.98%, this is a footnote. If you are in the 0.02%, it is a month-long fire drill, and the vendor did nothing wrong.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Anthropic replaced git because git assumes a human is typing</title>
				<link>https://hitesh.in/2026/tools-built-for-human-speed/</link>
				<pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/tools-built-for-human-speed/</guid>
				<description>&lt;p&gt;Anthropic&amp;rsquo;s merges per day went from about 2,500 in May to over 30,000 by September. In &lt;a href=&#34;https://www.anthropic.com/engineering/redesigning-source-control&#34;&gt;its own account&lt;/a&gt;, source control became &amp;ldquo;our biggest development bottleneck.&amp;rdquo; Seven engineers spent five months replacing git for the monorepo with an in-house system called Scion.&lt;/p&gt;&#xA;&lt;p&gt;Most companies should not copy that. The more useful thing to copy is the diagnosis, because the thing that broke was not a model, a prompt, or an agent framework. It was a tool that had quietly assumed who its user was.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Your coding agent has a default stack. Who chose it?</title>
				<link>https://hitesh.in/2026/your-agents-default-stack/</link>
				<pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/your-agents-default-stack/</guid>
				<description>&lt;p&gt;Nolan Lawson, who has argued for years that developers should &lt;a href=&#34;https://nolanlawson.com/2026/10/03/why-dont-more-developers-use-the-platform/&#34;&gt;use the platform&lt;/a&gt; instead of reinventing it in JavaScript, spent a post this week taking the other side. His explanation for why so many developers resist is mostly about people. They reach for what they know. Documentation for libraries used to be better than documentation for browsers. And building your own modal dialog is more fun than adopting &lt;code&gt;&amp;lt;dialog&amp;gt;&lt;/code&gt;, a pleasure he calls the IKEA effect.&lt;/p&gt;</description>
			</item>
			<item>
				<title>10 patterns where Jev, not your frontier model, should decide</title>
				<link>https://hitesh.in/2026/where-jev-shines/</link>
				<pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/where-jev-shines/</guid>
				<description>&lt;p&gt;TypeSafe shipped something unusual this month: a model that never writes a sentence. &lt;a href=&#34;https://typesafe.ai/blog/introducing-system-one-models-and-jev&#34;&gt;Jev&lt;/a&gt; takes in a state and returns a typed decision, a choice, a score, or a probability, in roughly 70 to 500 milliseconds, for about four hundredths of a cent per call. Route the same decision through a frontier model and you&amp;rsquo;re paying &lt;a href=&#34;https://www.cloudraft.io/blog/top-use-cases-of-jev-typesafe-ai-model&#34;&gt;thirty to a few hundred times as much&lt;/a&gt; and waiting noticeably longer for it. It&amp;rsquo;s already showing up in real infrastructure, not just a launch post: &lt;a href=&#34;https://vercel.com/changelog/typesafe-ai-jev-now-available-on-ai-gateway&#34;&gt;Vercel added it to the AI Gateway&lt;/a&gt; within days.&lt;/p&gt;</description>
			</item>
			<item>
				<title>When code gets cheap, your abstractions get expensive</title>
				<link>https://hitesh.in/2026/when-code-gets-cheap/</link>
				<pubDate>Fri, 11 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/when-code-gets-cheap/</guid>
				<description>&lt;p&gt;Shopify spent five years as one of React Native&amp;rsquo;s loudest champions. It contributed core libraries, shipped its flagship apps on it, and told the industry that cross-platform was the grown-up choice. Last week it &lt;a href=&#34;https://shopify.engineering/back-to-native&#34;&gt;went back to native Swift and Kotlin&lt;/a&gt;, rebuilding its Shop app from a proof of concept to a store-published native app in twelve weeks. The stated reason is AI: coding agents can now do enough of the mechanical work that maintaining two native codebases is no longer the deciding cost it was in 2020.&lt;/p&gt;</description>
			</item>
			<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>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>Pick the stack that catches your AI&#39;s mistakes</title>
				<link>https://hitesh.in/2026/stack-that-catches-ai-mistakes/</link>
				<pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/stack-that-catches-ai-mistakes/</guid>
				<description>&lt;p&gt;A claim has been making the rounds among engineering teams: choose a terse language and your AI coding agent will spend fewer tokens, so you pay less and move faster. The early numbers looked convincing. Then Dan Luu &lt;a href=&#34;http://danluu.com/pl-tokens/&#34;&gt;tested them on real work&lt;/a&gt;, and the advantage mostly fell apart. On toy problems, a dense language like J or Clojure did use a third to half the tokens of the alternatives. On a substantial task, writing a Zstd decoder from the spec, or a full Pandoc feature, the gap closed. What actually predicted a good result was how popular and well-documented the language was.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Shopify scaled checkout by removing a system</title>
				<link>https://hitesh.in/2026/count-your-systems/</link>
				<pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/count-your-systems/</guid>
				<description>&lt;p&gt;On Black Friday last year, Shopify was clearing &lt;a href=&#34;https://shopify.engineering/scaling-inventory-reservations&#34;&gt;$5.1 million in sales a minute at peak&lt;/a&gt;. The piece of software deciding whether the last unit of a sold-out hoodie is yours or the person&amp;rsquo;s next to you just got rebuilt. The interesting part is how they did it: they made checkout faster by removing a system, not adding one. They pulled inventory reservations out of Redis and folded them into the MySQL database that already held the inventory ledger.&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>Writing code got free. Reviewing it is the job now.</title>
				<link>https://hitesh.in/2026/reviewing-is-the-job/</link>
				<pubDate>Tue, 14 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/reviewing-is-the-job/</guid>
				<description>&lt;p&gt;Microsoft ran the experiment most companies are only talking about. Over four months in early 2026 it put command-line coding agents, Claude Code and GitHub Copilot CLI, in front of tens of thousands of its own engineers and &lt;a href=&#34;https://arxiv.org/abs/2607.01418&#34;&gt;measured what happened&lt;/a&gt;. The adopters merged about 24% more pull requests than they otherwise would have, and the lift held for the whole study rather than fading as a novelty. If you sell AI tooling, that is the slide.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Your backlog is the only benchmark that matters</title>
				<link>https://hitesh.in/2026/your-backlog-is-the-benchmark/</link>
				<pubDate>Thu, 09 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/your-backlog-is-the-benchmark/</guid>
				<description>&lt;p&gt;On the 8th of July, OpenAI published &lt;a href=&#34;https://openai.com/index/separating-signal-from-noise-coding-evaluations/&#34;&gt;an audit of the coding benchmarks&lt;/a&gt; everyone uses to rank models, including SWE-bench, and reported that roughly 30% of the tasks in the Pro set were broken in ways that quietly distort the scores. This from the company with every incentive to keep those numbers looking meaningful. When a lab audits the scoreboard it competes on and tells you the scoreboard is unreliable, the honest reading is that the number on the leaderboard has stopped measuring the thing you are trying to buy.&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 your TAM is bigger than US GDP</title>
				<link>https://hitesh.in/2026/when-your-tam-is-bigger-than-gdp/</link>
				<pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/when-your-tam-is-bigger-than-gdp/</guid>
				<description>&lt;p&gt;SpaceX is &lt;a href=&#34;https://www.reuters.com/legal/transactional/spacex-buy-anysphere-60-billion-2026-06-16/&#34;&gt;buying Cursor for $60 billion&lt;/a&gt;. The price alone would fill a week of tech news, but the detail that has stayed with me is the addressable market figure reportedly used to justify it: $26 trillion. Roughly the size of US GDP.&lt;/p&gt;&#xA;&lt;p&gt;I want to take the number seriously rather than just laugh at it, because it actually reveals something about how the industry prices AI right now.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-logic-isnt-crazy&#34;&gt;The logic isn&amp;rsquo;t crazy&lt;/h2&gt;&#xA;&lt;p&gt;The math isn&amp;rsquo;t irrational on its face. There are roughly a billion knowledge workers globally. If AI can accelerate each one enough to replace $5,000 to $10,000 in annual labour value, you&amp;rsquo;re already at $5-10 trillion. Push the productivity assumption further and the number grows. If you believe AI eventually touches every form of paid cognitive work, $26 trillion starts to feel conservative.&lt;/p&gt;</description>
			</item>
			<item>
				<title>AI Writes the Code. Who Governs It?</title>
				<link>https://hitesh.in/2026/ai-writes-the-code-who-governs-it/</link>
				<pubDate>Thu, 11 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/ai-writes-the-code-who-governs-it/</guid>
				<description>&lt;p&gt;A new survey of 831 engineers found that 97% of teams now use AI coding assistants. Only 30% have a fully governed way of overseeing what those assistants produce, and a quarter have no AI coding policy at all.&lt;/p&gt;&#xA;&lt;p&gt;I wrote recently about the &lt;a href=&#34;https://hitesh.in/2026/beyond-the-chatbox-the-rise-of-the-sovereign-engineer/&#34;&gt;sovereign engineer&lt;/a&gt;, the engineer who owns outcomes rather than just output. This is the other half of that argument, and a less flattering one. If you are going to own the outcome, you have to own the code an AI wrote on your behalf. Most teams have skipped that part.&lt;/p&gt;</description>
			</item>
			<item>
				<title>We Stopped Laughing at GenAI</title>
				<link>https://hitesh.in/2026/we-stopped-laughing-at-genai/</link>
				<pubDate>Thu, 11 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2026/we-stopped-laughing-at-genai/</guid>
				<description>&lt;p&gt;For a couple of years we lived comfortably in what I think of as the quaint-dismissal phase. We laughed at the six-fingered hands in image generators. We collected screenshots of confident nonsense from early chatbots. We said &amp;ldquo;&lt;a href=&#34;https://dl.acm.org/doi/10.1145/3442188.3445922&#34;&gt;stochastic parrot&lt;/a&gt;&amp;rdquo; at conferences and went back to work, reassured that our professional moats, built on decades of hard-won knowledge, were safe from a glorified autocomplete.&lt;/p&gt;&#xA;&lt;p&gt;That phase is over for me, and not because of any single model release. The kind of story people tell about these tools has changed. A year ago the stories were &amp;ldquo;look at the silly mistake it made.&amp;rdquo; Now they are &amp;ldquo;I did a thing in one evening that I had assumed was impossible for someone like me.&amp;rdquo; The mood has gone from amused to a slightly uneasy &lt;em&gt;oh.&lt;/em&gt;&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>
			<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>When AI writes code from intent, the spec becomes the hard part</title>
				<link>https://hitesh.in/2025/are-you-prepared-for-intent-drive-development/</link>
				<pubDate>Fri, 13 Jun 2025 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2025/are-you-prepared-for-intent-drive-development/</guid>
				<description>&lt;p&gt;Within four days in May, GitHub and Anthropic both shipped coding agents that take a description of work and come back with code. With GitHub&amp;rsquo;s new &lt;a href=&#34;https://github.blog/news-insights/product-news/github-copilot-meet-the-new-coding-agent/&#34;&gt;Copilot coding agent&lt;/a&gt;, you &amp;ldquo;assign one or more GitHub issues to Copilot&amp;rdquo; and it comes back with a pull request. Three days later Anthropic made &lt;a href=&#34;https://www.anthropic.com/news/claude-4&#34;&gt;Claude Code generally available&lt;/a&gt;. In both cases the input is a written statement of what you want, and the output is a change somebody still has to approve.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Exploring Emerging AI Agent Frameworks</title>
				<link>https://hitesh.in/2025/exploring-emerging-ai-agent-frameworks/</link>
				<pubDate>Tue, 18 Mar 2025 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2025/exploring-emerging-ai-agent-frameworks/</guid>
				<description>&lt;h3 id=&#34;the-tools-shaping-the-future-of-intelligent-automation&#34;&gt;The Tools Shaping the Future of Intelligent Automation&lt;/h3&gt;&#xA;&lt;p&gt;Imagine sitting down to build an AI-powered system. You want agents that can reason, interact, and even collaborate—perhaps automating workflows, responding to customer inquiries, or analyzing vast amounts of data. But where do you begin?&lt;/p&gt;&#xA;&lt;p&gt;Fortunately, the world of AI agent frameworks is evolving rapidly, offering a rich ecosystem of tools designed for different levels of complexity, from simple, lightweight libraries to sophisticated multi-agent systems. Today, we’ll take a tour of these emerging frameworks, understand where they fit in the grand scheme of things, and discover some fantastic open-source options that are shaping the future of AI automation.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
