<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Technical-Debt - Tag - vo.rs</title><link>https://vo.rs/tags/technical-debt/</link><description>Technical-Debt - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 06 Aug 2024 09:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/technical-debt/" rel="self" type="application/rss+xml"/><item><title>Technical Debt in a Home Lab: When to Refactor and When to Let It Rot</title><link>https://vo.rs/story/technical-debt-in-a-home-lab-when-to-refactor-and-when-to-let-it-rot/</link><description>&lt;p&gt;Somewhere in my homelab there is a service running in a container I built by hand in 2021, configured by SSH-ing in and editing files directly, with no Compose file, no documentation, and a startup command that lives only in my shell history. It has not gone down once. I am terrified of it, and I have decided to leave it exactly where it is.&lt;/p&gt;
&lt;p&gt;This is the dirty secret of running infrastructure for fun: technical debt is real here too, but the economics are completely different from a workplace. At work, debt compounds across a team and a roadmap. At home, it compounds across exactly one person — you — and the only deadline is your own patience. That changes the calculus enormously, and it means the professional instinct to &amp;ldquo;do it properly&amp;rdquo; is sometimes the wrong instinct.&lt;/p&gt;</description><pubDate>Tue, 06 Aug 2024 09:00:00 +0000</pubDate></item></channel></rss>