<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Orchestration on No Semicolons</title><link>https://nosemicolons.com/tags/ai-orchestration/</link><description>Recent content in AI Orchestration on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 05 Aug 2026 10:27:28 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/ai-orchestration/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Multimodel Strategy: How I Use 5 Different AI Models for One Feature (And Why It's Worth the Complexity)</title><link>https://nosemicolons.com/posts/ai-code-generation-multimodel-strategy-guide/</link><pubDate>Wed, 05 Aug 2026 10:27:28 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-multimodel-strategy-guide/</guid><description>&lt;p>Ever find yourself switching between ChatGPT, Claude, and Gemini mid-feature because each one seems to excel at different things? You&amp;rsquo;re not alone, and you&amp;rsquo;re definitely not overthinking it.&lt;/p>
&lt;p>Last month, while building a data visualization dashboard, I caught myself using five different AI models for a single feature. At first, I felt like I was overcomplicating things. But after stepping back and analyzing my workflow, I realized I&amp;rsquo;d stumbled onto something powerful: a multimodel AI development strategy that leverages each model&amp;rsquo;s unique strengths.&lt;/p></description></item></channel></rss>