<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>adr on Kuldeep Pisda</title><link>https://kdpisda.in/tag/adr/</link><description>Recent content in adr on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 27 Nov 2025 12:38:46 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/adr/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Software Architecture Documentation Is Lying to You</title><link>https://kdpisda.in/your-software-architecture-documentation-is-lying-to-you/</link><pubDate>Thu, 27 Nov 2025 12:38:46 +0530</pubDate><guid>https://kdpisda.in/your-software-architecture-documentation-is-lying-to-you/</guid><description>&lt;p&gt;&amp;ldquo;The documentation is in the code.&amp;rdquo; I can&amp;rsquo;t count how many times I&amp;rsquo;ve heard this, usually from a well meaning senior engineer right before I spend the next three days spelunking through a codebase just to figure out what a single microservice is supposed to do.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s be honest with each other. Most software architecture documentation is a ghost. It&amp;rsquo;s a pale, outdated echo of a system that once existed, haunting your Confluence space or a forgotten Google Drive folder. You follow the &lt;code&gt;README&lt;/code&gt;, and it breaks. You look at a diagram, and it shows services that were decommissioned a year ago.&lt;/p&gt;</description></item></channel></rss>