<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Documentation on Gniewomir Świechowski</title>
    <link>https://gniewomir.com/tags/documentation/</link>
    <description>Recent content in Documentation on Gniewomir Świechowski</description>
    <image>
      <title>Gniewomir Świechowski</title>
      <url>https://gniewomir.com/images/papermod-cover.png</url>
      <link>https://gniewomir.com/images/papermod-cover.png</link>
    </image>
    <generator>Hugo -- 0.147.8</generator>
    <language>en</language>
    <lastBuildDate>Sat, 09 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://gniewomir.com/tags/documentation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>You can un-slop code but not documentation</title>
      <link>https://gniewomir.com/posts/you-can-unslop-code-but-not-documentation/</link>
      <pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate>
      <guid>https://gniewomir.com/posts/you-can-unslop-code-but-not-documentation/</guid>
      <description>&lt;p&gt;There is a huge problem I have not seen discussed in the context of AI. Documentation—just like code—can rot when subjected to unrestricted AI use, and this is not something that can be easily, if at all, fixed.&lt;/p&gt;
&lt;p&gt;Missing, misleading or outdated documentation forces rushed explorations focused on how, not why—which tightens competition for resources between research, design, and implementation. Good documentation warns about dead ends and explains constraints, allowing teams to reach better decisions faster. Yet, having a good knowledge base was hard before AI, and I&amp;rsquo;m convinced that it will get even harder with it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
