<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ilko Kacharov — Building AI-native products</title>
    <link>https://kachar.dev</link>
    <description>Field notes from a CTO &amp; co-founder building AI-native products. Essays on AI agents, context engineering, shipping fast, and the craft of building software in the LLM era.</description>
    <language>en</language>
    <lastBuildDate>Tue, 14 Jul 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://kachar.dev/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Loop engineering is verifier engineering</title>
      <link>https://kachar.dev/blog/loop-engineering-is-verifier-engineering</link>
      <guid isPermaLink="true">https://kachar.dev/blog/loop-engineering-is-verifier-engineering</guid>
      <description>Eleven articles, 43 million views, one idea: design loops that prompt your agents. They all agree you need a verifier. Almost none of them are one.</description>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>ai</category>
      <category>agents</category>
      <category>architecture</category>
    </item>
    <item>
      <title>Prompt engineering is over. You&apos;re a context engineer now.</title>
      <link>https://kachar.dev/blog/context-engineering-is-mostly-subtraction</link>
      <guid isPermaLink="true">https://kachar.dev/blog/context-engineering-is-mostly-subtraction</guid>
      <description>Prompt engineering quietly gave way to context engineering. The catch: most teams doing it are doing it backwards.</description>
      <pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate>
      <category>ai</category>
      <category>context-engineering</category>
      <category>agents</category>
    </item>
    <item>
      <title>The AI coworker is a weekend project now</title>
      <link>https://kachar.dev/blog/the-ai-coworker-is-a-weekend-project-now</link>
      <guid isPermaLink="true">https://kachar.dev/blog/the-ai-coworker-is-a-weekend-project-now</guid>
      <description>Viktor and Martoshi make the AI-employee-in-Slack look like a company. We built the same shape on Vercel&apos;s Eve in one session.</description>
      <pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate>
      <category>building</category>
      <category>agents</category>
      <category>architecture</category>
    </item>
    <item>
      <title>Your product is the easy part now</title>
      <link>https://kachar.dev/blog/your-product-is-the-easy-part-now</link>
      <guid isPermaLink="true">https://kachar.dev/blog/your-product-is-the-easy-part-now</guid>
      <description>AI collapsed the cost of building software. The bottleneck moved from creation to adoption, and most founders are still optimizing the solved side.</description>
      <pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate>
      <category>ai</category>
      <category>building</category>
      <category>product</category>
    </item>
    <item>
      <title>The chat UX is the product, not the model</title>
      <link>https://kachar.dev/blog/the-chat-ux-is-the-product-not-the-model</link>
      <guid isPermaLink="true">https://kachar.dev/blog/the-chat-ux-is-the-product-not-the-model</guid>
      <description>shadcn calls it scroll engineering. It is bigger than that. Users don&apos;t churn on your model, they churn on the chat UX around it.</description>
      <pubDate>Fri, 26 Jun 2026 00:00:00 GMT</pubDate>
      <category>building</category>
      <category>product</category>
      <category>design</category>
    </item>
    <item>
      <title>Stop picking npm or shadcn for your users</title>
      <link>https://kachar.dev/blog/stop-picking-npm-or-shadcn-for-your-users</link>
      <guid isPermaLink="true">https://kachar.dev/blog/stop-picking-npm-or-shadcn-for-your-users</guid>
      <description>npm versus shadcn is the wrong fight. How much of your component a team wants to own is their call, not yours. Ship the whole spectrum from one source.</description>
      <pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate>
      <category>building</category>
      <category>architecture</category>
      <category>product</category>
    </item>
    <item>
      <title>We deleted Jira in three weeks</title>
      <link>https://kachar.dev/blog/we-deleted-jira-in-three-weeks</link>
      <guid isPermaLink="true">https://kachar.dev/blog/we-deleted-jira-in-three-weeks</guid>
      <description>Building your own Jira used to be insane. With AI writing the code and an MCP server wiring it to everything, the math flipped.</description>
      <pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate>
      <category>building</category>
      <category>agents</category>
      <category>cto</category>
    </item>
    <item>
      <title>Your homepage should run the product</title>
      <link>https://kachar.dev/blog/your-homepage-should-run-the-product</link>
      <guid isPermaLink="true">https://kachar.dev/blog/your-homepage-should-run-the-product</guid>
      <description>I rebuilt the Prompt Area homepage around the live component instead of copy about it. For a developer tool, the demo is not a section on the page. It is the page.</description>
      <pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate>
      <category>building</category>
      <category>product</category>
      <category>design</category>
    </item>
    <item>
      <title>Build for the model you&apos;ll lose</title>
      <link>https://kachar.dev/blog/build-for-the-model-youll-lose</link>
      <guid isPermaLink="true">https://kachar.dev/blog/build-for-the-model-youll-lose</guid>
      <description>The best coding model in the world lasted three days before a government directive switched it off. The lesson is not &apos;use local models.&apos; It is &apos;never couple your product to a model you are not allowed to keep.&apos;</description>
      <pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate>
      <category>ai</category>
      <category>architecture</category>
      <category>building</category>
    </item>
    <item>
      <title>Agent memory is mostly hoarding</title>
      <link>https://kachar.dev/blog/agent-memory-is-mostly-hoarding</link>
      <guid isPermaLink="true">https://kachar.dev/blog/agent-memory-is-mostly-hoarding</guid>
      <description>Stuffing every past message into context is not memory, it is hoarding. Real memory is knowing what to forget.</description>
      <pubDate>Thu, 11 Jun 2026 00:00:00 GMT</pubDate>
      <category>ai</category>
      <category>agents</category>
      <category>context-engineering</category>
    </item>
    <item>
      <title>Context is the new CMS</title>
      <link>https://kachar.dev/blog/context-is-the-new-cms</link>
      <guid isPermaLink="true">https://kachar.dev/blog/context-is-the-new-cms</guid>
      <description>For twenty years teams ran a content management system. The next era runs on context management: what your AI knows before it writes a word.</description>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <category>ai</category>
      <category>context-engineering</category>
      <category>building</category>
    </item>
    <item>
      <title>Your evals are the moat</title>
      <link>https://kachar.dev/blog/your-evals-are-the-moat</link>
      <guid isPermaLink="true">https://kachar.dev/blog/your-evals-are-the-moat</guid>
      <description>Your prompts are not your moat. Your model is not your moat. The test suite that catches silent regressions is the thing nobody can copy.</description>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <category>ai</category>
      <category>evals</category>
      <category>building</category>
    </item>
    <item>
      <title>A bigger model won&apos;t save you</title>
      <link>https://kachar.dev/blog/a-bigger-model-wont-save-you</link>
      <guid isPermaLink="true">https://kachar.dev/blog/a-bigger-model-wont-save-you</guid>
      <description>Most &apos;we need a bigger model&apos; complaints are context engineering problems in disguise. A smaller model with the right context beats a frontier model fed a junk drawer.</description>
      <pubDate>Tue, 02 Jun 2026 00:00:00 GMT</pubDate>
      <category>ai</category>
      <category>context-engineering</category>
      <category>building</category>
    </item>
    <item>
      <title>Spend your three innovation tokens on the product</title>
      <link>https://kachar.dev/blog/three-innovation-tokens</link>
      <guid isPermaLink="true">https://kachar.dev/blog/three-innovation-tokens</guid>
      <description>Choosing Postgres and a boring monolith looks lazy. It is the opposite. Here is how I think about innovation budget as a CTO.</description>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <category>cto</category>
      <category>architecture</category>
      <category>building</category>
    </item>
  </channel>
</rss>