https://blog.dev.simpleenough.net/tags/technical-debt/Recent content in Technical Debt on Simple Enough BlogHugoenMon, 20 Jul 2026 13:00:00 +0200https://blog.dev.simpleenough.net/blog/modetransmissions/Mon, 20 Jul 2026 13:00:00 +0200https://blog.dev.simpleenough.net/blog/modetransmissions/<p>In &ldquo;When the last expert disappears,&rdquo; we saw <em>why</em> a team&rsquo;s memory is an invisible form of technical debt. What remains is <em>how</em> to fix it. Pair programming, mob, shadowing, code review, ADRs, on-call rotation: there is no shortage of practices, and that is precisely the problem — you don&rsquo;t know which one to pick. This guide maps them out and gives a simple rule for deciding.</p> <hr> <h2 id="i-two-kinds-of-knowledge-tacit-and-explicit" class="heading">I. Two kinds of knowledge: tacit and explicit<a href="#i-two-kinds-of-knowledge-tacit-and-explicit" aria-labelledby="i-two-kinds-of-knowledge-tacit-and-explicit"> <!-- <i class="fas fa-link anchor"></i> --> <svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512"><use href="#fas-link"></use></svg>&nbsp; </a> </h2> <p>Before choosing a practice, you need to know <strong>what you are passing on</strong>. All team knowledge falls into two families, and they don&rsquo;t obey the same laws.</p>https://blog.dev.simpleenough.net/blog/dernierexpert/Mon, 20 Jul 2026 12:00:00 +0200https://blog.dev.simpleenough.net/blog/dernierexpert/<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&rsquo;t just a colleague walking out: it&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.</p>