<?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 Nalar</title>
    <link>https://nalar.dev/tags/adr/</link>
    <description>Recent content in ADR on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/adr/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Architecture Decision Records That Stay Useful</title>
      <link>https://nalar.dev/architecture-decision-records-that-stay-useful/</link>
      <pubDate>Wed, 02 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/architecture-decision-records-that-stay-useful/</guid>
      <description>&lt;p&gt;Software systems accumulate decisions that are obvious at the time and mysterious six months later. A database was chosen for a reason, a synchronous call became asynchronous for a reason, and a service boundary exists because some trade-off mattered.&lt;/p&gt;&#xA;&lt;p&gt;Architecture Decision Records, or ADRs, preserve that reasoning in small documents close to the code.&lt;/p&gt;&#xA;&lt;h2 id=&#34;record-decisions-not-meetings&#34;&gt;Record decisions, not meetings&lt;/h2&gt;&#xA;&lt;p&gt;An ADR should answer a future engineer&amp;rsquo;s practical questions:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;What problem were we solving?&lt;/li&gt;&#xA;&lt;li&gt;What constraints mattered?&lt;/li&gt;&#xA;&lt;li&gt;What did we decide?&lt;/li&gt;&#xA;&lt;li&gt;Which alternatives were considered?&lt;/li&gt;&#xA;&lt;li&gt;What consequences did we accept?&lt;/li&gt;&#xA;&lt;li&gt;Has this decision been replaced?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;It does not need to reproduce a design meeting transcript.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
