<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Karan Popat</title>
    <link>https://popatkaran.github.io</link>
    <description>Lead Software Engineer &amp; Tech Architect</description>
    <atom:link href="https://popatkaran.github.io/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title><![CDATA[Do We Still Need Frameworks in the Age of AI Coding Agents?]]></title>
      <link>https://popatkaran.github.io/articles/frameworks-relevance-ai-coding-agents</link>
      <guid>https://popatkaran.github.io/articles/frameworks-relevance-ai-coding-agents</guid>
      <pubDate>Wed, 01 Apr 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[AI coding agents can generate boilerplate, enforce patterns, and refactor large codebases at speed. So what exactly do frameworks still offer — and when should you skip them entirely?]]></description>
    </item>
    <item>
      <title><![CDATA[AWS Cost Architecture: How System Design Decisions Become Your Cloud Bill]]></title>
      <link>https://popatkaran.github.io/articles/aws-cost-architecture-system-design-decisions</link>
      <guid>https://popatkaran.github.io/articles/aws-cost-architecture-system-design-decisions</guid>
      <pubDate>Fri, 20 Mar 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[Your cloud bill is a mirror of your architecture. The most expensive line items are almost always the result of design decisions made without cost visibility. Here is how to read that mirror.]]></description>
    </item>
    <item>
      <title><![CDATA[Multi-Agent AI Workflows: From Prototype to Production]]></title>
      <link>https://popatkaran.github.io/articles/multi-agent-ai-workflows-prototype-to-production</link>
      <guid>https://popatkaran.github.io/articles/multi-agent-ai-workflows-prototype-to-production</guid>
      <pubDate>Tue, 10 Mar 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[Multi-agent AI systems are not just a research curiosity — they are changing how engineering teams operate. Here is what it takes to move them from prototype to production without the chaos.]]></description>
    </item>
    <item>
      <title><![CDATA[Kiro CLI vs Claude Code: Building Team-Wide AI Development Standards]]></title>
      <link>https://popatkaran.github.io/articles/kiro-cli-vs-claude-code-ai-development-standards</link>
      <guid>https://popatkaran.github.io/articles/kiro-cli-vs-claude-code-ai-development-standards</guid>
      <pubDate>Thu, 05 Mar 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[Two tools, one standard. Learn how to run Kiro and Claude Code side-by-side across a polyrepo, enforce Epic-to-Subtask pipelines, and let every developer use their preferred AI tool without fragmenting your workflow.]]></description>
    </item>
    <item>
      <title><![CDATA[Building an AI-Powered Documentation System]]></title>
      <link>https://popatkaran.github.io/articles/ai-documentation-generator-case-study</link>
      <guid>https://popatkaran.github.io/articles/ai-documentation-generator-case-study</guid>
      <pubDate>Wed, 25 Feb 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[How we built an automated documentation pipeline using AI to generate inline comments, API documentation, and architecture diagrams — saving hours of manual work.]]></description>
    </item>
    <item>
      <title><![CDATA[The Complete k6 Load Testing Guide]]></title>
      <link>https://popatkaran.github.io/articles/k6-load-testing-complete-guide</link>
      <guid>https://popatkaran.github.io/articles/k6-load-testing-complete-guide</guid>
      <pubDate>Fri, 20 Feb 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[Master k6 load testing from basics to advanced scenarios. Includes a complete ShopFlow e-commerce case study with smoke, load, stress, spike, soak, and breakpoint tests.]]></description>
    </item>
    <item>
      <title><![CDATA[Headless Commerce Architecture: When to Go Composable and When Not To]]></title>
      <link>https://popatkaran.github.io/articles/headless-commerce-architecture-when-to-go-composable</link>
      <guid>https://popatkaran.github.io/articles/headless-commerce-architecture-when-to-go-composable</guid>
      <pubDate>Wed, 18 Feb 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[Headless commerce is not a silver bullet. It is a trade-off. This is the decision framework for knowing when composable architecture delivers real value — and when it just adds cost.]]></description>
    </item>
    <item>
      <title><![CDATA[Building a Senior Engineering Team That Outlasts the Project]]></title>
      <link>https://popatkaran.github.io/articles/building-senior-engineering-team-that-outlasts</link>
      <guid>https://popatkaran.github.io/articles/building-senior-engineering-team-that-outlasts</guid>
      <pubDate>Thu, 12 Feb 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[The measure of great engineering leadership is not the systems you build — it is the team you leave behind. More capable, more autonomous, more confident than when you found them.]]></description>
    </item>
    <item>
      <title><![CDATA[Zero-Downtime Database Migrations at Scale]]></title>
      <link>https://popatkaran.github.io/articles/zero-downtime-database-migrations-at-scale</link>
      <guid>https://popatkaran.github.io/articles/zero-downtime-database-migrations-at-scale</guid>
      <pubDate>Thu, 05 Feb 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[Downtime for database migrations is a choice, not a requirement. These are the patterns that make schema changes invisible to users — even on tables with hundreds of millions of rows.]]></description>
    </item>
    <item>
      <title><![CDATA[The Staff Engineer Playbook: Influence Without Authority]]></title>
      <link>https://popatkaran.github.io/articles/staff-engineer-influence-without-authority</link>
      <guid>https://popatkaran.github.io/articles/staff-engineer-influence-without-authority</guid>
      <pubDate>Wed, 28 Jan 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[The hardest part of being a Staff Engineer is not the technical work — it is changing how an organisation thinks and builds without the authority to mandate it. This is the playbook for doing that effectively.]]></description>
    </item>
    <item>
      <title><![CDATA[Evolutionary Architecture: Designing Systems That Survive Contact With Reality]]></title>
      <link>https://popatkaran.github.io/articles/evolutionary-architecture-systems-that-survive</link>
      <guid>https://popatkaran.github.io/articles/evolutionary-architecture-systems-that-survive</guid>
      <pubDate>Thu, 15 Jan 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[Most systems fail not because of bad initial design but because they cannot change. Evolutionary architecture is the practice of building systems that adapt — without accumulating the kind of debt that eventually forces a rewrite.]]></description>
    </item>
  </channel>
</rss>