<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Portable Workflows on No Semicolons</title><link>https://nosemicolons.com/tags/portable-workflows/</link><description>Recent content in Portable Workflows on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 12 May 2026 10:25:37 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/portable-workflows/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Vendor Lock-in Trap: How to Build Portable AI Workflows That Work Across Any Platform</title><link>https://nosemicolons.com/posts/ai-code-generation-vendor-lock-in-portable-workflows/</link><pubDate>Tue, 12 May 2026 10:25:37 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-vendor-lock-in-portable-workflows/</guid><description>&lt;p>Ever had that sinking feeling when your favorite AI coding tool suddenly changes their API, pricing model, or just&amp;hellip; disappears? I&amp;rsquo;ve been there, and it&amp;rsquo;s not fun watching months of carefully crafted workflows crumble overnight.&lt;/p>
&lt;p>The AI coding landscape moves fast. Really fast. What feels like the perfect tool today might be yesterday&amp;rsquo;s news in six months. Yet somehow, we keep building our entire development workflows around single vendors, creating invisible chains that get stronger every day.&lt;/p></description></item></channel></rss>