<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Developer-Experience on Panditha</title>
    <link>https://panditha.com/tags/developer-experience/</link>
    <description>Recent content in Developer-Experience on Panditha</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 26 Jul 2026 17:42:37 +1000</lastBuildDate>
    <atom:link href="https://panditha.com/tags/developer-experience/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Documentation Is Not a Story</title>
      <link>https://panditha.com/posts/documentation-is-not-a-story/</link>
      <pubDate>Sun, 26 Jul 2026 17:42:37 +1000</pubDate>
      <guid>https://panditha.com/posts/documentation-is-not-a-story/</guid>
      <description>&lt;p&gt;There&amp;rsquo;s a quiet assumption baked into most technical documentation: that someone will sit down and read it. Start at the top, work through to the bottom, arrive at the other end understanding the system. We write as if we&amp;rsquo;re authoring a textbook, taking a reader on a careful journey from ignorance to competence.&lt;/p&gt;&#xA;&lt;p&gt;Nobody reads documentation like that. They never really did, and in the age of AI they definitely don&amp;rsquo;t. So it&amp;rsquo;s worth asking what documentation is actually for, and whether the way we write it still matches the way it gets used.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
