<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Knowledge Management on Zhanwei Wang</title><link>https://zhanwei.wang/en/tags/knowledge-management/</link><description>Recent content in Knowledge Management on Zhanwei Wang</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 09 Apr 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://zhanwei.wang/en/tags/knowledge-management/index.xml" rel="self" type="application/rss+xml"/><item><title>When Documentation Stops Rotting: From Karpathy's LLM Wiki to Software Engineering Documentation</title><link>https://zhanwei.wang/en/posts/when-documentation-stops-rotting/</link><pubDate>Thu, 09 Apr 2026 00:00:00 +0800</pubDate><guid>https://zhanwei.wang/en/posts/when-documentation-stops-rotting/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Humans write the original documents and make decisions. LLMs handle synthesis, updates, and consistency checks. Documentation is no longer a static artifact that rots the moment it&amp;rsquo;s written — it becomes a living knowledge base continuously maintained by LLMs.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="an-age-old-problem"&gt;An Age-Old Problem&lt;/h2&gt;
&lt;p&gt;Every software engineer has experienced this: you join a project, open the docs, and find the README still describing a module deleted six months ago, API docs with fields that don&amp;rsquo;t match the code at all, and architecture diagrams showing a design from two versions back. You ask a colleague, who says, &amp;ldquo;Don&amp;rsquo;t bother with the docs — just read the code.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>