<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Documentation on Adrian Spiridon</title><link>https://adrianspiridon.dev/tags/documentation/</link><description>Recent content in Documentation on Adrian Spiridon</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://adrianspiridon.dev/tags/documentation/index.xml" rel="self" type="application/rss+xml"/><item><title>From Change to State: Preserving Engineering Knowledge</title><link>https://adrianspiridon.dev/blog/from-change-to-state-preserving-engineering-knowledge/</link><pubDate>Sat, 31 Oct 2026 00:00:00 +0200</pubDate><guid>https://adrianspiridon.dev/blog/from-change-to-state-preserving-engineering-knowledge/</guid><description>Requirements, architecture, and code evolve, but their historical rationale is easily lost. This article proposes keeping a historical change ledger alongside living engineering specifications.</description></item></channel></rss>