Your kids collect stones and sticks. You collect emails, and probably browser tabs and desktop icons. When you move to new PC, all your desktop files ends up in a directory called New folder on the new pc’s desktop and the journey to fill the new desktop starts over before you have New folder and New folder 2 on the upcoming pc.
It's beautiful. Thanks to Moore's law, you can always fit all historical data in half your latest disk space. Though I personally tend to call them "Stuff" or "Junk".
But don't do
Stuff
Junk
That's a rookie strategy, do
Stuff /
Stuff / Stuff
Stuff / Stuff / Junk / ...
When you need to find something old, just go down the folders until you start finding files from the right decade.
You should only organize things as you actually use them. The things you use are then generally organized and you haven’t wasted a bunch of time organizing stuff you never use.
If you do decide to organize a bunch of stuff you never use, that decision is then totally aesthetic, so you should choose a method of doing it that you find aesthetically pleasing.
Source: obsidian user who spent a bunch of time organizing stuff he never uses.
I largely agree, that's why I've still got all of it stored away, but I guess I'd like to keep track of what is it that I'm not using, what can I delete and what can I deduplicate.
I moved my SSD from my old computer into my new one. Because I'm a masochist who manually sets up my partitions with custom labels, it literally worked the first time I booted it. (The only change I did was swapping to the AMD microcode from the Intel microcode because of the processor in my new machine being different). When upgrading SSDs, I just replicated the same partition structure on the new disk and copied everything over with rsync, which also "just worked".
I still can't decide whether these strategies are obvious and intuitive or if they go against literally everything I've learned about what should be feasible. Can't argue with the results though!
That is sadly often true today, but not inevitable! When you are overwhelmed with complexity, a natural defense mechanism is to restrict choice. But with better tooling, you can better manage and reduce complexity, which allows you to say "yes" to developers without compromising on reliability and security. That is what we are trying to enable with Dagger.
