<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>AI on Vignesh Ragupathy</title>
    <link>https://vigneshragupathy.com/tags/ai/</link>
    <description>Recent content in AI on Vignesh Ragupathy</description>
    <image>
      <title>Vignesh Ragupathy</title>
      <url>https://vigneshragupathy.com/images/papermod-cover.png</url>
      <link>https://vigneshragupathy.com/images/papermod-cover.png</link>
    </image>
    <generator>Hugo -- 0.148.2</generator>
    <language>en</language>
    <lastBuildDate>Thu, 18 Dec 2025 10:50:00 +0000</lastBuildDate>
    <atom:link href="https://vigneshragupathy.com/tags/ai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Surviving the Rewrite - Managing Risk and AI Memory Loss in Large-Scale Development</title>
      <link>https://vigneshragupathy.com/surviving-the-rewrite-managing-risk-and-ai-memory-loss-in-large-scale-development/</link>
      <pubDate>Thu, 18 Dec 2025 10:50:00 +0000</pubDate>
      <guid>https://vigneshragupathy.com/surviving-the-rewrite-managing-risk-and-ai-memory-loss-in-large-scale-development/</guid>
      <description>&lt;h3 id=&#34;tldr&#34;&gt;&lt;span style=&#34;color:#6366f1&#34;&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;I recently undertook a project that terrifies most engineers: rewriting a massive, critical infrastructure automation tool from scratch. I moved from legacy Bash to Python without writing a single line of manual code - relying entirely on AI agents. Here is how I managed the risk, the architecture, and the &amp;ldquo;memory loss&amp;rdquo; of LLMs to build a production-grade tool.&lt;/p&gt;
&lt;h3 id=&#34;the-stakes&#34;&gt;&lt;span style=&#34;color:#6366f1&#34;&gt;&lt;strong&gt;The Stakes&lt;/strong&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;This wasn’t a simple CRUD app. This tool manages infrastructure for multiple teams. A logic error here doesn’t just throw a stack trace; it could wipe an entire environment or cause immediate customer impact.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building AI for Observability with AWS Bedrock</title>
      <link>https://vigneshragupathy.com/building-ai-for-observability-with-aws-bedrock/</link>
      <pubDate>Thu, 04 Sep 2025 00:45:00 +0000</pubDate>
      <guid>https://vigneshragupathy.com/building-ai-for-observability-with-aws-bedrock/</guid>
      <description>&lt;h1 id=&#34;building-ai-for-observability-with-aws-bedrock&#34;&gt;Building AI for Observability with AWS Bedrock&lt;/h1&gt;
&lt;p&gt;In my &lt;a href=&#34;https://vigneshragupathy.com/closing-the-last-mile-of-observability-with-ai/&#34; rel=&#34;noopener&#34; target=&#34;_blank&#34;&gt;previous post&lt;/a&gt;, I wrote about &lt;em&gt;closing the last mile of observability with AI&lt;/em&gt; . The core idea was simple: we already have plenty of metrics, logs, and traces, but the real challenge is turning them into &lt;strong&gt;insights&lt;/strong&gt; and &lt;strong&gt;answers&lt;/strong&gt; that engineers can act on.&lt;/p&gt;
&lt;p&gt;In that post, I highlighted two main gaps:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Connector layer&lt;/strong&gt; – bridging multiple observability tools like Prometheus, Thanos, Elastic, etc.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Insight layer&lt;/strong&gt; – going beyond raw queries to provide real context and recommendations.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Now, I’ve been experimenting with &lt;strong&gt;AWS Bedrock&lt;/strong&gt; , and it feels like a natural way to solve both layers.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Closing the Last Mile of Observability with AI</title>
      <link>https://vigneshragupathy.com/closing-the-last-mile-of-observability-with-ai/</link>
      <pubDate>Mon, 01 Sep 2025 00:45:00 +0000</pubDate>
      <guid>https://vigneshragupathy.com/closing-the-last-mile-of-observability-with-ai/</guid>
      <description>&lt;p&gt;Over the years, observability has grown in ways I couldn’t have imagined when I first started working in this space. Thanks to &lt;strong&gt;OpenTelemetry&lt;/strong&gt;, we now have a standard way to collect traces, metrics, and logs. Tools like &lt;strong&gt;Grafana, Prometheus, Jaeger and Elasticsearch&lt;/strong&gt; make it easy to store and visualize that data.&lt;/p&gt;
&lt;p&gt;But here’s the truth I keep coming back to:&lt;br&gt;
Even with all the dashboards and alerts, something is still missing.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
