<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Model Version Control on No Semicolons</title><link>https://nosemicolons.com/tags/model-version-control/</link><description>Recent content in Model Version Control on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 04 Sep 2026 12:23:47 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/model-version-control/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Model Switching Massacre: How I Lost 2 Weeks of Work When GPT-4 Updated (And the Version Lock Strategy That Prevents It)</title><link>https://nosemicolons.com/posts/ai-code-generation-model-switching-massacre-version-lock-strategy/</link><pubDate>Fri, 04 Sep 2026 12:23:47 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-model-switching-massacre-version-lock-strategy/</guid><description>&lt;p>Picture this: You wake up on a Tuesday morning, grab your coffee, and fire up your AI-powered development workflow that&amp;rsquo;s been humming along perfectly for weeks. You run your usual code generation pipeline, and suddenly everything is&amp;hellip; wrong. The output format is different, the logic patterns have shifted, and your carefully crafted prompts are producing completely different results.&lt;/p>
&lt;p>Welcome to the AI Code Generation Model Switching Massacre of 2024. Or at least, that&amp;rsquo;s what I&amp;rsquo;m calling the two weeks I spent rebuilding workflows after an unannounced GPT-4 update silently broke everything I&amp;rsquo;d built.&lt;/p></description></item></channel></rss>