<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bhumi Hirapara - Blog</title>
    <link>https://www.bhumihirapara.com/blog/</link>
    <description>Writing on design, development, AI-assisted workflows and the tools in between.</description>
    <language>en</language>
    <atom:link href="https://www.bhumihirapara.com/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How I Actually Ship 10x Faster With Claude, Cursor and Codex</title>
      <link>https://www.bhumihirapara.com/blog/shipping-faster-with-ai/</link>
      <guid isPermaLink="true">https://www.bhumihirapara.com/blog/shipping-faster-with-ai/</guid>
      <pubDate>Tue, 27 Oct 2026 00:00:00 GMT</pubDate>
      <category>AI &amp; Automation</category>
      <description>The speed does not come from typing less. It comes from eliminating the three things that actually consumed project time: starting from nothing, context switching, and the review-revise loop with someone else.</description>
    </item>
    <item>
      <title>The Design Handoff Is Dead. What Replaced It Is Better.</title>
      <link>https://www.bhumihirapara.com/blog/design-handoff-is-dead/</link>
      <guid isPermaLink="true">https://www.bhumihirapara.com/blog/design-handoff-is-dead/</guid>
      <pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate>
      <category>Design</category>
      <description>Handoff existed because designing and building were different jobs done by different people. When one person can do both at speed, the artefact that survives is not the spec - it is the system.</description>
    </item>
    <item>
      <title>React or Astro: Choosing by What the Page Has to Do</title>
      <link>https://www.bhumihirapara.com/blog/react-or-astro/</link>
      <guid isPermaLink="true">https://www.bhumihirapara.com/blog/react-or-astro/</guid>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
      <category>Development</category>
      <description>The honest rule: if most of the page is content people read, start with Astro. If most of it is interface people operate, start with React. Most arguments about this are really arguments about which kind of page someone usually builds.</description>
    </item>
    <item>
      <title>Driving Elementor With MCP: What Actually Works</title>
      <link>https://www.bhumihirapara.com/blog/elementor-mcp-what-works/</link>
      <guid isPermaLink="true">https://www.bhumihirapara.com/blog/elementor-mcp-what-works/</guid>
      <pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate>
      <category>WordPress</category>
      <description>Model Context Protocol lets an assistant read and edit Elementor pages directly. It is genuinely useful for structure, repetitive layout and content population - and a poor fit for visual judgement.</description>
    </item>
    <item>
      <title>Vibe Coding Is Real, and It Breaks in Exactly Three Places</title>
      <link>https://www.bhumihirapara.com/blog/vibe-coding-where-it-breaks/</link>
      <guid isPermaLink="true">https://www.bhumihirapara.com/blog/vibe-coding-where-it-breaks/</guid>
      <pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate>
      <category>AI &amp; Automation</category>
      <description>Describing what you want and letting a model write the code genuinely works now. It also fails in three predictable places: state you did not describe, the second change to the same file, and anything that was never visible on screen.</description>
    </item>
  </channel>
</rss>