<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Model Selection on No Semicolons</title><link>https://nosemicolons.com/tags/model-selection/</link><description>Recent content in Model Selection on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 08 Sep 2026 12:26:50 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/model-selection/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Model Routing Crisis: How Smart Model Selection Reduced My Development Costs by 80%</title><link>https://nosemicolons.com/posts/ai-code-generation-model-routing-crisis-smart-selection-reduced-costs/</link><pubDate>Tue, 08 Sep 2026 12:26:50 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-model-routing-crisis-smart-selection-reduced-costs/</guid><description>&lt;p>Ever looked at your monthly AI API bill and wondered if you accidentally funded someone&amp;rsquo;s rocket ship to Mars? Last month, I stared at a $847 invoice from my AI coding assistant usage and realized I had a serious problem on my hands.&lt;/p>
&lt;p>Like many developers who&amp;rsquo;ve embraced AI-assisted coding, I&amp;rsquo;d fallen into the &amp;ldquo;premium model for everything&amp;rdquo; trap. Every single code generation task—from writing simple getter methods to architecting complex distributed systems—was hitting GPT-4 or Claude Opus. It was like using a Ferrari to drive to the mailbox.&lt;/p></description></item></channel></rss>