<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Home on Zenia Hew | zenshin </title>
    <link>http://localhost:1313/</link>
    <description>Recent content in Home on Zenia Hew | zenshin </description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 30 Sep 2026 13:30:19 +0800</lastBuildDate>
    <atom:link href="http://localhost:1313/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>LLM-as-Judge For Contextual Evaluation</title>
      <link>http://localhost:1313/posts/llm-as-judge-contextual-evaluation/</link>
      <pubDate>Wed, 30 Sep 2026 13:30:19 +0800</pubDate>
      <guid>http://localhost:1313/posts/llm-as-judge-contextual-evaluation/</guid>
      <description>&lt;p&gt;In my previous post, I documented moving from fuzzy keyword search (Fuse.js) to semantic vector search (all-MiniLM-L6-v2 + LanceDB). The upgrade felt huge: vector search looks past literal character matches to find conceptual intent.&lt;/p&gt;&#xA;&lt;p&gt;However, as I ran deeper tests with emotional user inputs, I ran into a boundary that vector search cannot cross on its own: &lt;strong&gt;vector search evaluates distance, not appropriateness&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-boundary-vector-search-is-a-mirror&#34;&gt;The Boundary: Vector Search is a Mirror&lt;/h2&gt;&#xA;&lt;p&gt;At their core, transformer-based Large Language Models aren&amp;rsquo;t just text generators. Their fundamental power lies in &lt;strong&gt;context processing and pattern recognition:&lt;/strong&gt; analyzing relationships, organizing unstructured information, and evaluating constraints across high-dimensional token representations.&#xA;When developers build with LLMs, the default pattern is almost always text generation. But when building a retrieval-backed app (like an anime quote finder), generation introduces severe tradeoffs:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building A Retrieval System: Keywords vs. Natural Language</title>
      <link>http://localhost:1313/posts/keyword-vs-semantic-retrieval/</link>
      <pubDate>Mon, 28 Sep 2026 16:49:29 +0800</pubDate>
      <guid>http://localhost:1313/posts/keyword-vs-semantic-retrieval/</guid>
      <description>&lt;p&gt;Imagine a foreign tourist who speaks limited English coming up, making a few hand gestures, and saying: “Train. Airport.”&lt;/p&gt;&#xA;&lt;p&gt;You understand both words, but do you know what he wants to convey? He could be asking where to catch the train to the airport, when the next train leaves, or simply whether a train to the airport exists.&lt;/p&gt;&#xA;&lt;p&gt;This short interaction highlights the fundamental challenge of building a text search engine: keywords carry specific terms, but they omit intent and context.&lt;/p&gt;</description>
    </item>
    <item>
      <title>About</title>
      <link>http://localhost:1313/about/</link>
      <pubDate>Sun, 22 Mar 2026 23:03:15 +0800</pubDate>
      <guid>http://localhost:1313/about/</guid>
      <description>&lt;p&gt;Coming soon!&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
