<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>DocumentationPractice on emsenn.net</title>
    <link>https://emsenn.net/tags/documentationpractice/</link>
    <description>Recent content in DocumentationPractice on emsenn.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 07 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://emsenn.net/tags/documentationpractice/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Architecture Decision Records</title>
      <link>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/software-engineering/domains/structured-work-paradigms/texts/architecture-decision-records/</link>
      <pubDate>Sat, 07 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/software-engineering/domains/structured-work-paradigms/texts/architecture-decision-records/</guid>
      <description>&lt;p&gt;Architecture Decision Records (ADRs) are short text documents that&#xA;capture a single architectural decision, its context, and its&#xA;consequences. Michael Nygard introduced the format in a November 2011&#xA;blog post titled &amp;ldquo;Documenting Architecture Decisions,&amp;rdquo; published on&#xA;the Cognitect blog (Nygard, 2011). The post argued that agile projects&#xA;need lightweight documentation that stays close to the code, rather&#xA;than large design documents that fall out of date.&lt;/p&gt;&#xA;&lt;h2 id=&#34;format&#34;&gt;Format&lt;/h2&gt;&#xA;&lt;p&gt;Nygard&amp;rsquo;s original ADR format draws on the structure of Alexandrian&#xA;patterns. Each record contains five sections:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
