<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Model Context on No Semicolons</title><link>https://nosemicolons.com/tags/model-context/</link><description>Recent content in Model Context on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 16 Jul 2026 09:59:36 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/model-context/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Model Memory Crisis: How to Build Features That Actually Remember Previous Context Across Sessions</title><link>https://nosemicolons.com/posts/ai-code-generation-model-memory-crisis-cross-session-context/</link><pubDate>Thu, 16 Jul 2026 09:59:36 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-model-memory-crisis-cross-session-context/</guid><description>&lt;p>Ever fired up your AI coding assistant for day two of a project, only to watch it suggest completely irrelevant code that ignores everything you built yesterday? Yeah, me too. It&amp;rsquo;s like having a brilliant pair programming partner who gets amnesia every time they leave the room.&lt;/p>
&lt;p>This context loss isn&amp;rsquo;t just annoying—it&amp;rsquo;s a genuine productivity killer. You spend the first hour of each session re-explaining your architecture, your naming conventions, and why you chose that particular database schema. By the time your AI is back up to speed, you&amp;rsquo;ve lost momentum and probably questioned whether AI-assisted development is worth the hassle.&lt;/p></description></item></channel></rss>