<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>GSD on Kd05</title>
        <link>https://kd05.com/tags/gsd/</link>
        <description>Recent content in GSD on Kd05</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en</language>
        <lastBuildDate>Mon, 06 Apr 2026 11:00:00 +0800</lastBuildDate><atom:link href="https://kd05.com/tags/gsd/index.xml" rel="self" type="application/rss+xml" /><item>
        <title>My First Experience with GSD: Solving the Context Rot Problem in AI Coding</title>
        <link>https://kd05.com/p/gsd-context-rot-solution/</link>
        <pubDate>Mon, 06 Apr 2026 11:00:00 +0800</pubDate>
        
        <guid>https://kd05.com/p/gsd-context-rot-solution/</guid>
        <description>&lt;img src="https://kd05.com/p/gsd-context-rot-solution/gsd.jpg" alt="Featured image of post My First Experience with GSD: Solving the Context Rot Problem in AI Coding" /&gt;&lt;h2 id=&#34;introduction-the-context-rot-dilemma&#34;&gt;Introduction: The Context Rot Dilemma
&lt;/h2&gt;&lt;p&gt;Recently, while exploring AI-assisted coding tools, I discovered &lt;strong&gt;GSD (get-shit-done)&lt;/strong&gt;, a specification-driven development system. The name itself is refreshingly direct—no pretense, just getting things done. But what really caught my attention was its approach to tackling &lt;strong&gt;context rot&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;ve been using AI coding assistants for a while, you&amp;rsquo;ve probably noticed this phenomenon: conversations start off great—the AI&amp;rsquo;s responses are precise and helpful. But as the session progresses and context accumulates, quality starts degrading noticeably. This isn&amp;rsquo;t a model limitation; it&amp;rsquo;s what researchers call &amp;ldquo;context rot.&amp;rdquo;&lt;/p&gt;</description>
        </item>
        
    </channel>
</rss>
