<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Zohair</title>
    <description>The latest articles on DEV Community by Zohair (@zoh007).</description>
    <link>https://dev.to/zoh007</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4056826%2Fb277df6f-1cdb-413e-8cc2-f5ce13732998.png</url>
      <title>DEV Community: Zohair</title>
      <link>https://dev.to/zoh007</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zoh007"/>
    <language>en</language>
    <item>
      <title>How I Built a No-Execution LLM Eval Judge (75% Accuracy, No API Calls)</title>
      <dc:creator>Zohair</dc:creator>
      <pubDate>Fri, 31 Jul 2026 15:01:50 +0000</pubDate>
      <link>https://dev.to/zoh007/how-i-built-a-no-execution-llm-eval-judge-75-accuracy-no-api-calls-4lna</link>
      <guid>https://dev.to/zoh007/how-i-built-a-no-execution-llm-eval-judge-75-accuracy-no-api-calls-4lna</guid>
      <description>&lt;p&gt;Evaluating LLM outputs is one of those problems that sounds simple until you actually try to do it at scale.&lt;/p&gt;

&lt;p&gt;Most approaches fall into three buckets:&lt;/p&gt;

&lt;p&gt;Run the code — works for coding tasks but requires a sandbox, is slow, and breaks on edge cases constantly.&lt;/p&gt;

&lt;p&gt;GPT-4 as a judge — surprisingly effective but costs money, adds latency, and feels wrong to use one LLM to evaluate another.&lt;/p&gt;

&lt;p&gt;Manual review — fine for 50 samples. Completely falls apart at 1,500+.&lt;/p&gt;

&lt;p&gt;I wanted something different. Fast, local, no API calls, no execution environment, no cost per eval. So I built LLM Judge.&lt;/p&gt;

&lt;p&gt;How it works&lt;/p&gt;

&lt;p&gt;The core insight is simple: semantic similarity between a model output and a reference answer is a surprisingly strong signal for correctness — especially for coding questions where there's usually one right approach.&lt;/p&gt;

&lt;p&gt;Here's the pipeline:&lt;/p&gt;

&lt;p&gt;Model output + Reference answer&lt;br&gt;
          ↓&lt;br&gt;
Sentence Transformers (all-MiniLM-L6-v2)&lt;br&gt;
          ↓&lt;br&gt;
Cosine similarity score&lt;br&gt;
          ↓&lt;br&gt;
Logistic regression classifier&lt;br&gt;
          ↓&lt;br&gt;
Correct / Partially correct / Incorrect + calibrated confidence score&lt;/p&gt;

&lt;p&gt;I trained the logistic regression on a merged Hugging Face coding Q&amp;amp;A dataset, validated on 1,500+ labeled submissions.&lt;/p&gt;

&lt;p&gt;Results&lt;br&gt;
~75% accuracy on held-out coding Q&amp;amp;A split&lt;br&gt;
~58% agreement with human judges on 1,500+ labeled submissions&lt;br&gt;
Runs entirely locally — no API calls, no sandbox&lt;br&gt;
Fast enough for batch evaluation at scale&lt;/p&gt;

&lt;p&gt;The 58% human agreement number is the interesting one. Human judges disagree with each other more than you'd expect on coding questions — so 58% agreement with humans is actually competitive with inter-human agreement on ambiguous cases.&lt;/p&gt;

&lt;p&gt;What I built&lt;/p&gt;

&lt;p&gt;Three interfaces for different use cases:&lt;/p&gt;

&lt;p&gt;CLI batch scoring — point it at a CSV of model outputs and reference answers, get scores back:&lt;/p&gt;

&lt;p&gt;bash&lt;br&gt;
python evaluate_csv.py --input outputs.csv --output scores.csv&lt;/p&gt;

&lt;p&gt;Training your own judge:&lt;/p&gt;

&lt;p&gt;bash&lt;br&gt;
python train_judge.py --dataset your_dataset.csv&lt;/p&gt;

&lt;p&gt;Streamlit UI — visual interface with calibrated scores and 3-tier feedback for each eval:&lt;/p&gt;

&lt;p&gt;bash&lt;br&gt;
streamlit run app.py&lt;br&gt;
Stack&lt;br&gt;
Python&lt;br&gt;
Sentence Transformers&lt;br&gt;
Scikit-Learn&lt;br&gt;
Streamlit&lt;br&gt;
Pandas&lt;br&gt;
What's next&lt;/p&gt;

&lt;p&gt;The open source version handles local evaluation. I'm building a hosted API version next — upload your dataset, get scores back via API, no setup required. If that's something you'd use, let me know in the comments.&lt;/p&gt;

&lt;p&gt;Try it&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/Zoh007/RAG_PRAC" rel="noopener noreferrer"&gt;https://github.com/Zoh007/RAG_PRAC&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Would love feedback from anyone doing LLM evaluation at scale — especially curious:&lt;/p&gt;

&lt;p&gt;Is 75% accuracy good enough for production eval pipelines?&lt;br&gt;
What edge cases do you run into that simple similarity scoring misses?&lt;br&gt;
Would a hosted API be worth paying for or would you always self-host?&lt;/p&gt;

</description>
      <category>llm</category>
      <category>machinelearning</category>
      <category>python</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
