Take more screenshots (2022)
&gt; For example, my oldest files were made in Microsoft Word on an iMac G3 running Mac OS 9. I can open them in a modern word processor, and they look similar – but it’s not the same. Some of the fonts and graphics are missing, and I don’t know where I’d find replacements.<p>&gt;  It’s even harder for an undocumented side project I abandoned years ago. Having the code isn’t the same as a working application.<p>The author&#x27;s solution to this is apparently screenshots, I have to respectfully disagree.<p>For software, side project or not, it should probably come with dependency configurations (granted, in early 2000s this isn&#x27;t as mature as it is today) and some tests. My side projects basically all have tests, these tests are vital for picking up years later and for validation while developing.<p>For personal notes, I use this script which upon `$ diary` would create&#x2F;open an entry for the current day in the appropriate folder with vim: <a href="https:&#x2F;&#x2F;github.com&#x2F;Aperocky&#x2F;diaryman&#x2F;blob&#x2F;master&#x2F;diaryman.sh">https:&#x2F;&#x2F;github.com&#x2F;Aperocky&#x2F;diaryman&#x2F;blob&#x2F;master&#x2F;diaryman.sh</a>. Text files will last forever, it has some basic flavoring with markdown, but that&#x27;s it. The folder where this is indexed is without a doubt the most valuable data on my computer, and it stretches back years.<p>I do occasionally take screenshots but never for reasons that author find screenshot to be useful for.