<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Abhijeet Maharana: Blog</title>
    <link>https://maharana.dev/blog</link>
    <atom:link href="https://maharana.dev/blog/rss.xml" rel="self" type="application/rss+xml" />
    <description>Engineering notes from real projects: payments, AI agents and React apps.</description>
    <language>en</language>
    <lastBuildDate>Sat, 14 Nov 2026 18:30:00 GMT</lastBuildDate>
    <item>
      <title>Building a Real-Time Voice AI Agent with Gemini Live and Node.js</title>
      <link>https://maharana.dev/blog/real-time-voice-ai-agent-gemini-live-nodejs</link>
      <guid isPermaLink="true">https://maharana.dev/blog/real-time-voice-ai-agent-gemini-live-nodejs</guid>
      <description>How the parts of an open-source voice agent fit together: 16 kHz and 24 kHz AudioWorklets over a WebSocket to Gemini Live, tool calls run on a Node.js server, and Claude grading the call into a Zod-checked report.</description>
      <pubDate>Sat, 14 Nov 2026 18:30:00 GMT</pubDate>
      <category>AI agents</category>
      <category>Voice AI</category>
      <category>Node.js</category>
      <category>TypeScript</category>
    </item>
    <item>
      <title>A Gemini Live Voice Agent in the Browser, Without Exposing Your API Key</title>
      <link>https://maharana.dev/blog/gemini-live-voice-agent-browser-api-key</link>
      <guid isPermaLink="true">https://maharana.dev/blog/gemini-live-voice-agent-browser-api-key</guid>
      <description>How to stream voice straight from the browser to Gemini Live while the key, the prompt and the tools stay on your server: one-use tokens, server-built setup, tool calls relayed over HTTP, and session resumption.</description>
      <pubDate>Sat, 14 Nov 2026 18:30:00 GMT</pubDate>
      <category>AI agents</category>
      <category>Node.js</category>
      <category>TypeScript</category>
    </item>
    <item>
      <title>Payment Webhooks in Node.js: How to Never Apply a Payment Twice</title>
      <link>https://maharana.dev/blog/idempotent-payment-webhooks-nodejs</link>
      <guid isPermaLink="true">https://maharana.dev/blog/idempotent-payment-webhooks-nodejs</guid>
      <description>Payment providers resend webhooks, and a handler that runs twice charges, ships or emails twice. Signature checks, Redis claims, locks and a reconciliation job that close the gap.</description>
      <pubDate>Sat, 31 Oct 2026 18:30:00 GMT</pubDate>
      <category>Node.js</category>
      <category>Payments</category>
      <category>Redis</category>
      <category>E-commerce</category>
    </item>
    <item>
      <title>Running Claude Code 24/7 on a Mini PC, with Approvals in Slack</title>
      <link>https://maharana.dev/blog/claude-code-24-7-agent-with-approvals</link>
      <guid isPermaLink="true">https://maharana.dev/blog/claude-code-24-7-agent-with-approvals</guid>
      <description>How I run a personal AI agent around the clock on one small machine: scheduled jobs, Slack threads, approval cards before anything leaves the box, and no secrets in the model's reach.</description>
      <pubDate>Sat, 31 Oct 2026 18:30:00 GMT</pubDate>
      <category>AI agents</category>
      <category>Claude Code</category>
      <category>Node.js</category>
      <category>Automation</category>
    </item>
    <item>
      <title>Building an Internal React Component Library That Teams Actually Use</title>
      <link>https://maharana.dev/blog/react-component-library-teams-adopt</link>
      <guid isPermaLink="true">https://maharana.dev/blog/react-component-library-teams-adopt</guid>
      <description>What made a shared React library stick across 5+ apps: small typed APIs, accessibility inside the components, tests that check behaviour, versioned releases, and code splitting that cut load time by 40%.</description>
      <pubDate>Sat, 31 Oct 2026 18:30:00 GMT</pubDate>
      <category>React</category>
      <category>TypeScript</category>
      <category>Accessibility</category>
      <category>Performance</category>
    </item>
  </channel>
</rss>
