<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Coding Context on No Semicolons</title><link>https://nosemicolons.com/tags/coding-context/</link><description>Recent content in Coding Context on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 29 Aug 2026 13:30:17 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/coding-context/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Model Switching Protocol: How to Train 3 Different Models on Your Codebase Without Context Chaos</title><link>https://nosemicolons.com/posts/ai-code-generation-model-switching-protocol/</link><pubDate>Sat, 29 Aug 2026 13:30:17 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-model-switching-protocol/</guid><description>&lt;p>Ever started a coding session with Claude, switched to GPT-4 for some tricky logic, then jumped to Gemini for documentation, only to find yourself explaining the same context over and over again? You&amp;rsquo;re not alone. I&amp;rsquo;ve been there, watching my productivity tank as each model struggled to understand what the others had built.&lt;/p>
&lt;p>After months of juggling different AI coding assistants on the same projects, I&amp;rsquo;ve developed what I call the &amp;ldquo;Model Switching Protocol&amp;rdquo; — a systematic approach that keeps all three major models (GPT-4, Claude, and Gemini) aligned on your codebase without the context chaos.&lt;/p></description></item></channel></rss>