<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: pendingU</title><link>https://news.ycombinator.com/user?id=pendingU</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 23 Apr 2026 04:36:28 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=pendingU" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by pendingU in "Johnny.Decimal – A system to organise your life"]]></title><description><![CDATA[
<p>I'm always impressed by systems like this, but I've personally never understood the point.<p>I'd be curious to learn from others what the benefits of this kind of archiving are for them? And if the time cost is worth it.<p>For me, I feel like I treat most of my documents as very temporal things. I need them for a certain period of time, but then after that, they can be list to the ether. I have never really had a need to reference old content, plans, documents, etc.<p>The only old things I ever need to reference are old code projects and writings. But even that I can usually manage with just a single folder for the project.<p>Everytime I get a new computer, I just start fresh. Keeping only a very small amount of files backed up in cloud services. Which as I mentioned are just a very small collection of code projects and writings. Am I crazy? Haha.</p>
]]></description><pubDate>Fri, 21 Feb 2025 15:54:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=43128949</link><dc:creator>pendingU</dc:creator><comments>https://news.ycombinator.com/item?id=43128949</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43128949</guid></item></channel></rss>