<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Memory on Simple Enough Blog</title><link>https://blog.dev.simpleenough.net/tags/memory/</link><description>Recent content in Memory on Simple Enough Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 20 Jul 2026 12:00:00 +0200</lastBuildDate><atom:link href="https://blog.dev.simpleenough.net/tags/memory/index.xml" rel="self" type="application/rss+xml"/><item><title>When the Last Expert Leaves</title><link>https://blog.dev.simpleenough.net/blog/dernierexpert/</link><pubDate>Mon, 20 Jul 2026 12:00:00 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/dernierexpert/</guid><description>&lt;p>In almost every organization there is a system people talk about in hushed tones. It has been running for ten years, it is critical, and exactly one person truly knows how it works. The day that person leaves — retirement, resignation, transfer — it isn&amp;rsquo;t just a colleague walking out: it&amp;rsquo;s an entire library closing down without ever having been copied. That lost knowledge is a form of technical debt, the most insidious of all, because it shows up on no dashboard.&lt;/p></description></item></channel></rss>