<?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>Engineering on Vignesh Ragupathy</title>
    <link>https://vigneshragupathy.com/tags/engineering/</link>
    <description>Recent content in Engineering 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/engineering/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>Stop Handing Out Tools Start Growing Engineers</title>
      <link>https://vigneshragupathy.com/stop-handing-out-tools-start-growing-engineers/</link>
      <pubDate>Sat, 13 Sep 2025 00:45:00 +0000</pubDate>
      <guid>https://vigneshragupathy.com/stop-handing-out-tools-start-growing-engineers/</guid>
      <description>&lt;h1 id=&#34;stop-handing-out-tools-start-growing-engineers&#34;&gt;Stop Handing Out Tools. Start Growing Engineers&lt;/h1&gt;
&lt;p&gt;I’ve seen this happen too many times. A new project kicks off, and the team hears:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;“Here’s the tool. Here’s the plan. Just deploy.”&lt;/em&gt;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;It feels efficient. But it skips the most important step: &lt;strong&gt;exploration.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;When engineers are told what to use, they don’t learn &lt;em&gt;why&lt;/em&gt; . They never see how others solve the same problem. They miss the chance to break, test, and truly understand. And over time, they stay stuck—good executors, but not real decision-makers.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
