<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Eval on Tyler Wells</title><link>https://blog-theta-seven-23.vercel.app/tags/eval/</link><description>Recent content in Eval on Tyler Wells</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 26 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog-theta-seven-23.vercel.app/tags/eval/index.xml" rel="self" type="application/rss+xml"/><item><title>Scoring RAG Answer Quality with an LLM Judge</title><link>https://blog-theta-seven-23.vercel.app/posts/rag-answer-judging/</link><pubDate>Mon, 26 Jan 2026 00:00:00 +0000</pubDate><guid>https://blog-theta-seven-23.vercel.app/posts/rag-answer-judging/</guid><description>[RAG Series 3/3] Source URL retrieval tells you whether the right content was retrieved. It doesn&amp;#39;t tell you whether the answer was any good. Adding an LLM judge to the eval harness reveals two failure modes that retrieval scoring alone can&amp;#39;t see.</description></item><item><title>How to Design RAG Eval Test Cases</title><link>https://blog-theta-seven-23.vercel.app/posts/design-rag-eval-test-cases/</link><pubDate>Sat, 24 Jan 2026 00:00:00 +0000</pubDate><guid>https://blog-theta-seven-23.vercel.app/posts/design-rag-eval-test-cases/</guid><description>[RAG Series 2/3] How to write test cases that catch real retrieval problems, why source URL retrieval is a useful proxy metric, and when it isn&amp;#39;t enough.</description></item><item><title>RAG Retrieval: Chunking, Embeddings, Reranking, and an Eval</title><link>https://blog-theta-seven-23.vercel.app/posts/rag-retrieval-quality/</link><pubDate>Thu, 22 Jan 2026 00:00:00 +0000</pubDate><guid>https://blog-theta-seven-23.vercel.app/posts/rag-retrieval-quality/</guid><description>[RAG Series 1/3] Covers chunking strategy, embedding model consistency, reranking, and building an eval harness — including what happened when Voyage AI&amp;#39;s free-tier rate limits forced a more resilient architecture.</description></item></channel></rss>