<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Context Transfer on No Semicolons</title><link>https://nosemicolons.com/tags/context-transfer/</link><description>Recent content in Context Transfer on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 17 Aug 2026 08:33:30 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/context-transfer/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Model Context Switch: How GPT-4 to Claude Handoffs Are Costing You 23 Minutes Per Feature</title><link>https://nosemicolons.com/posts/ai-code-generation-model-context-switch-cost/</link><pubDate>Mon, 17 Aug 2026 08:33:30 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-model-context-switch-cost/</guid><description>&lt;p>Ever find yourself copying code from a GPT-4 session, pasting it into Claude, then spending 20 minutes re-explaining what you&amp;rsquo;re building? You&amp;rsquo;re not alone. I recently tracked my own AI model switching patterns for a week and discovered something eye-opening: every time I switched models mid-feature, I lost an average of 23 minutes to context reconstruction.&lt;/p>
&lt;p>That&amp;rsquo;s nearly half an hour of pure overhead, every single switch. For a typical feature that touches 3-4 files, I was switching models 2-3 times, burning over an hour just on context handoffs. The worst part? I didn&amp;rsquo;t even realize I was doing it.&lt;/p></description></item></channel></rss>