<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vendor Lock-In on No Semicolons</title><link>https://nosemicolons.com/tags/vendor-lock-in/</link><description>Recent content in Vendor Lock-In on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 09 Aug 2026 08:32:14 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/vendor-lock-in/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Vendor Lock-In Escape Plan: How to Build Model-Agnostic Development Workflows</title><link>https://nosemicolons.com/posts/ai-code-generation-vendor-lock-in-escape-plan/</link><pubDate>Sun, 09 Aug 2026 08:32:14 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-vendor-lock-in-escape-plan/</guid><description>&lt;p>Ever notice how choosing an AI coding assistant feels eerily similar to picking a cloud provider circa 2010? You start with one that works well, build your entire workflow around it, and then suddenly you&amp;rsquo;re stuck when pricing changes, features disappear, or something better comes along.&lt;/p>
&lt;p>I learned this the hard way when my favorite AI model got nerfed in an update, and my carefully crafted prompts stopped working. That&amp;rsquo;s when I realized I needed an escape plan—a way to build AI-powered development workflows that could adapt to any model or platform.&lt;/p></description></item></channel></rss>