<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Documentation on No Semicolons</title><link>https://nosemicolons.com/tags/documentation/</link><description>Recent content in Documentation on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 17 Jun 2026 12:11:02 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/documentation/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Knowledge Transfer Crisis: How to Leave Projects Without Creating 6-Month Developer Nightmares</title><link>https://nosemicolons.com/posts/ai-code-generation-knowledge-transfer-crisis/</link><pubDate>Wed, 17 Jun 2026 12:11:02 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-knowledge-transfer-crisis/</guid><description>&lt;p>You know that sinking feeling when you inherit a project and the previous developer is nowhere to be found? Now imagine that project was built heavily with AI assistance, and suddenly you&amp;rsquo;re not just missing the human context—you&amp;rsquo;re missing the entire conversation history that shaped the codebase.&lt;/p>
&lt;p>I learned this the hard way last month when I had to emergency-transition an AI-generated microservice to a teammate. What seemed like well-structured code became a archaeological dig into prompts, iterations, and AI-assisted decisions that existed only in my head (and my ChatGPT history).&lt;/p></description></item></channel></rss>