<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open-Weight Models on Jaiman.org</title><link>/tags/open-weight-models/</link><description>Recent content in Open-Weight Models on Jaiman.org</description><generator>Hugo</generator><language>en</language><copyright>All material on this site is copyright of Ajay Jaiman or Arti Jaiman. Please do not use or reuse it without explicit permission.</copyright><lastBuildDate>Tue, 07 Jul 2026 21:33:02 +0530</lastBuildDate><atom:link href="/tags/open-weight-models/index.xml" rel="self" type="application/rss+xml"/><item><title>What I learned running an AI verification pipeline over 20,000 publisher profiles</title><link>/blog/ai-engineering/ai-verification-pipeline-what-i-learned/</link><pubDate>Tue, 07 Jul 2026 17:31:00 +0530</pubDate><guid>/blog/ai-engineering/ai-verification-pipeline-what-i-learned/</guid><description>&lt;p&gt;&lt;em&gt;This is Part 2 of a three-part series. &lt;a href="/blog/ai-engineering/how-i-was-forced-into-ai-engineering/"&gt;Part 1&lt;/a&gt; tells the story of why this system exists. &lt;a href="/blog/ai-engineering/full-stack-developer-ai-engineering-survey/"&gt;Part 3&lt;/a&gt; collects the rules I now follow. This part is the engineering.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://publishersglobal.com"&gt;PublishersGlobal&lt;/a&gt; runs a verification pipeline over an active directory of ~20,000 publishers and service providers. Every profile needs to be continuously verified and re-verified, because data on the internet degrades very quickly. In the first few months we ran close to 30,000 verification passes. This post recounts some of what I learned building and running the verification system on open-weight models.&lt;/p&gt;</description></item><item><title>A survey of what a full-stack developer learned doing AI engineering on a live production system</title><link>/blog/ai-engineering/full-stack-developer-ai-engineering-survey/</link><pubDate>Tue, 07 Jul 2026 17:30:00 +0530</pubDate><guid>/blog/ai-engineering/full-stack-developer-ai-engineering-survey/</guid><description>&lt;p&gt;&lt;em&gt;This is Part 3 of a three-part series. &lt;a href="/blog/ai-engineering/how-i-was-forced-into-ai-engineering/"&gt;Part 1&lt;/a&gt; is the story of why the system exists; &lt;a href="/blog/ai-engineering/ai-verification-pipeline-what-i-learned/"&gt;Part 2&lt;/a&gt; is the engineering detail. This part is the distillation: the rules I now follow, each one paid for by a specific mistake&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;. I&amp;rsquo;d bet that this list is far from complete and I will have the opportunity to add to it.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I came to AI engineering with decades of full-stack habits. Some transferred directly, some had to be unlearned, and a few new ones had to be acquired at the cost of production incidents. Here are twelve, in roughly the order the pipeline taught them to me.&lt;/p&gt;</description></item></channel></rss>