<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Coding Workflows on No Semicolons</title><link>https://nosemicolons.com/tags/ai-coding-workflows/</link><description>Recent content in AI Coding Workflows on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 19 Aug 2026 08:26:21 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/ai-coding-workflows/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Memory Leak: How to Prevent Context Overflow When Building Large Applications</title><link>https://nosemicolons.com/posts/ai-code-generation-memory-leak-context-overflow/</link><pubDate>Wed, 19 Aug 2026 08:26:21 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-memory-leak-context-overflow/</guid><description>&lt;p>Ever watched an AI confidently generate code that completely contradicts the architecture you established just 50 files ago? You&amp;rsquo;re not alone. I&amp;rsquo;ve been there, staring at my screen as Claude cheerfully creates a REST endpoint when my entire app is built on GraphQL, simply because our conversation had drifted too far from the original context.&lt;/p>
&lt;p>This is what I call the AI Code Generation Memory Leak – and it&amp;rsquo;s one of the biggest challenges facing developers building large applications with AI assistance. Unlike traditional memory leaks that slowly consume RAM, this one slowly consumes coherence, leaving you with a frankenstein codebase that works in pieces but falls apart as a whole.&lt;/p></description></item></channel></rss>