<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Sairam Ugge — Writing</title>
    <link>https://anvilry.vercel.app/articles</link>
    <description>Articles, notes &amp; engineering writing by Sairam Ugge.</description>
    <language>en</language>
    <item>
      <title>How I Built Inkforge: Designing an AI-Powered Article System with STORM Pipeline, BM25 RAG, and AWS Bedrock</title>
      <link>https://anvilry.vercel.app/notes/how-i-built-inkforge-designing-an-ai-powered-article-system-with-storm-pipeline-bm25-rag-and-aws-bedrock</link>
      <guid>https://anvilry.vercel.app/notes/how-i-built-inkforge-designing-an-ai-powered-article-system-with-storm-pipeline-bm25-rag-and-aws-bedrock</guid>
      <pubDate>Sat, 20 Jun 2026 00:00:00 GMT</pubDate>
      <description>A first-person engineering deep-dive into building Inkforge — an AI article generation system that combines the STORM research pipeline, BM25-based retrieval-augmented generation, and AWS Bedrock to produce structured, grounded long-form content at scale.</description>
    </item>
    <item>
      <title>Feature Flags at Scale: Designing a Distributed Control System for Production Behavior</title>
      <link>https://anvilry.vercel.app/notes/feature-flags-at-scale-distributed-control-system</link>
      <guid>https://anvilry.vercel.app/notes/feature-flags-at-scale-distributed-control-system</guid>
      <pubDate>Sat, 20 Jun 2026 00:00:00 GMT</pubDate>
      <description>At scale, feature flags stop being booleans and become a distributed control plane — here&apos;s the architecture, failure modes, and operational patterns that make them work at millions of evaluations per second.</description>
    </item>
    <item>
      <title>How I Traced One Browser Request from Keystroke to Rendered Page</title>
      <link>https://sairam0000.hashnode.dev/how-i-traced-one-browser-request-from-keystroke-to-rendered-page-www-google-com</link>
      <guid>https://sairam0000.hashnode.dev/how-i-traced-one-browser-request-from-keystroke-to-rendered-page-www-google-com</guid>
      <pubDate>Sat, 20 Jun 2026 00:00:00 GMT</pubDate>
      <description>A packet-level walkthrough of what actually happens when you type www.google.com — DNS, TCP, TLS, HTTP, and rendering — with the latency costs and design trade-offs at each layer.</description>
    </item>
    <item>
      <title>How I Traced One Browser Request from Keystroke to Rendered Page</title>
      <link>https://dev.to/sai_ram_0000/how-i-traced-one-browser-request-from-keystroke-to-rendered-page-1fpp</link>
      <guid>https://dev.to/sai_ram_0000/how-i-traced-one-browser-request-from-keystroke-to-rendered-page-1fpp</guid>
      <pubDate>Sat, 20 Jun 2026 00:00:00 GMT</pubDate>
      <description>A packet-level walkthrough of what actually happens when you type www.google.com — DNS, TCP, TLS, HTTP, and rendering — with the latency costs and design trade-offs at each layer.</description>
    </item>
    <item>
      <title>How DNS Actually Works: Resolution Hierarchy, Caching, and Production Failure Modes</title>
      <link>https://dev.to/sai_ram_0000/how-dns-actually-works-resolution-hierarchy-caching-and-production-failure-modes-195h</link>
      <guid>https://dev.to/sai_ram_0000/how-dns-actually-works-resolution-hierarchy-caching-and-production-failure-modes-195h</guid>
      <pubDate>Sat, 20 Jun 2026 00:00:00 GMT</pubDate>
      <description>A systems-level walkthrough of DNS resolution — from browser cache to authoritative nameserver — covering record types, anycast infrastructure, GeoDNS, and the operational edge cases that bite engineers in production.</description>
    </item>
    <item>
      <title>Feature Flags at Scale: Designing a Distributed Control System for Production Behavior</title>
      <link>https://sairam0000.substack.com/p/feature-flags-at-scale-the-complete</link>
      <guid>https://sairam0000.substack.com/p/feature-flags-at-scale-the-complete</guid>
      <pubDate>Sat, 20 Jun 2026 00:00:00 GMT</pubDate>
      <description>At scale, feature flags stop being booleans and become a distributed control plane — here&apos;s the architecture, failure modes, and operational patterns that make them work at millions of evaluations per second.</description>
    </item>
    <item>
      <title>Feature Flags at Scale: Designing a Distributed Control System for Production Behavior</title>
      <link>https://dev.to/sai_ram_0000/feature-flags-at-scale-designing-a-distributed-control-system-for-production-behavior</link>
      <guid>https://dev.to/sai_ram_0000/feature-flags-at-scale-designing-a-distributed-control-system-for-production-behavior</guid>
      <pubDate>Sat, 20 Jun 2026 00:00:00 GMT</pubDate>
      <description>At scale, feature flags stop being booleans and become a distributed control plane — here&apos;s the architecture, failure modes, and operational patterns that make them work at millions of evaluations per second.</description>
    </item>
    <item>
      <title>How I Traced One Browser Request from Keystroke to Rendered Page</title>
      <link>https://anvilry.vercel.app/notes/how-i-traced-one-browser-request-from-keystroke-to-rendered-page</link>
      <guid>https://anvilry.vercel.app/notes/how-i-traced-one-browser-request-from-keystroke-to-rendered-page</guid>
      <pubDate>Fri, 19 Jun 2026 00:00:00 GMT</pubDate>
      <description>A packet-level walkthrough of what actually happens when you type www.google.com — DNS, TCP, TLS, HTTP, and rendering — with the latency costs and design trade-offs at each layer.</description>
    </item>
    <item>
      <title>How DNS Actually Works: Resolution Hierarchy, Caching, and Production Failure Modes</title>
      <link>https://anvilry.vercel.app/notes/how-dns-works</link>
      <guid>https://anvilry.vercel.app/notes/how-dns-works</guid>
      <pubDate>Fri, 19 Jun 2026 00:00:00 GMT</pubDate>
      <description>A systems-level walkthrough of DNS resolution — from browser cache to authoritative nameserver — covering record types, anycast infrastructure, GeoDNS, and the operational edge cases that bite engineers in production.</description>
    </item>
    <item>
      <title>How I Traced One Browser Request from Keystroke to Rendered Page</title>
      <link>https://sairam0000.substack.com/p/how-i-traced-one-browser-request</link>
      <guid>https://sairam0000.substack.com/p/how-i-traced-one-browser-request</guid>
      <pubDate>Fri, 19 Jun 2026 00:00:00 GMT</pubDate>
      <description>A packet-level walkthrough of what actually happens when you type www.google.com — DNS, TCP, TLS, HTTP, and rendering — with the latency costs and design trade-offs at each layer.</description>
    </item>
    <item>
      <title>How I Traced One Browser Request from Keystroke to Rendered Page</title>
      <link>https://medium.com/@uggesairam0000/what-happens-when-you-type-www-google-com-a90611c7b9c0</link>
      <guid>https://medium.com/@uggesairam0000/what-happens-when-you-type-www-google-com-a90611c7b9c0</guid>
      <pubDate>Fri, 19 Jun 2026 00:00:00 GMT</pubDate>
      <description>A packet-level walkthrough of what actually happens when you type www.google.com — DNS, TCP, TLS, HTTP, and rendering — with the latency costs and design trade-offs at each layer.</description>
    </item>
    <item>
      <title>How DNS Actually Works: Resolution Hierarchy, Caching, and Production Failure Modes</title>
      <link>https://anvilry.vercel.app/articles/how-dns-works</link>
      <guid>https://anvilry.vercel.app/articles/how-dns-works</guid>
      <pubDate>Fri, 19 Jun 2026 00:00:00 GMT</pubDate>
      <description>A systems-level walkthrough of DNS resolution — from browser cache to authoritative nameserver — covering record types, anycast infrastructure, GeoDNS, and the operational edge cases that bite engineers in production.</description>
    </item>
  </channel>
</rss>