<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title> - Machine Learning</title>
    <link rel="self" type="application/atom+xml" href="https://sysrex.com/tags/machine-learning/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://sysrex.com"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2025-07-22T00:00:00+00:00</updated>
    <id>https://sysrex.com/tags/machine-learning/atom.xml</id>
    <entry xml:lang="en">
        <title>What LLM Evals Actually Are (and Why &#x27;Looks Good to Me&#x27; Isn&#x27;t a Strategy)</title>
        <published>2025-07-22T00:00:00+00:00</published>
        <updated>2025-07-22T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://sysrex.com/posts/what-are-llm-evals/"/>
        <id>https://sysrex.com/posts/what-are-llm-evals/</id>
        
        <summary type="html">&lt;p&gt;A lot of teams building on top of LLMs ship a prompt, look at a handful of
outputs, decide it &quot;seems good,&quot; and move on. That works right up until a
model update, a prompt tweak, or an edge case quietly breaks something
nobody&#x27;s testing for. Evals are the fix — the same instinct that gives you
unit tests and regression tests for regular code, applied to something
that doesn&#x27;t produce the same output twice.&lt;&#x2F;p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>LLM Quantization, Explained in Plain English</title>
        <published>2025-03-12T00:00:00+00:00</published>
        <updated>2025-03-12T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://sysrex.com/posts/llm-quantization-explained/"/>
        <id>https://sysrex.com/posts/llm-quantization-explained/</id>
        
        <summary type="html">&lt;p&gt;If you&#x27;ve tried running a large language model on your own hardware, you&#x27;ve
probably run into the same wall everyone does: the model is huge, your GPU
memory is not, and downloading a &quot;7B&quot; or &quot;70B&quot; model suddenly feels like a
math problem. Quantization is the main trick the community uses to close
that gap.&lt;&#x2F;p&gt;</summary>
        
    </entry>
</feed>
