[…] actually sorting my ID folders by mtime […]
Now that you spoke/wrote it out loud. I have 2 modi of operandi:
- Standard sorting because I usually know that I want to go to “ID x”
- Sorting by mtime whenever I re-visit a place I haven’t been in a while.
I tried sorting by mtime per default but found that too confusing because the order changed quite often and when I see “21.54” I expect “21.61” to come after that not before, except when I change myself to “last modified mode”
Maybe this is just because the default mode is too hard wired in the brain. 
While I’m always a fan of being as organized as possible (Hence why I’m here lol), my worry with headers is how it ultimately creates yet another layer of organization. It turns an already constrained (by design) system into Area → Category → Header → ID, of which you’re now further constrained to 10 of each. Personally I love the simplicity in the base two-level approach while only expanding it only when needed, as otherwise it’s easy to balloon out of control in one way or another.
Headers certainly make sense for something like the pre-built part of life admin where you already have every ID you plan on creating and you want related things together. I imagine we would all do some kind of similar grouping if we all had that benefit of seeing everything from the start, along with the benefit of having no more than 10 headers (and no more than 9 IDs in each header). Given the complexities of life though, I find it hard to imagine there are a lot of good categories that also divide neatly into 10 more boxes of 9.
I know my system would shift around if I saw everything that was in it now, but in a dynamic growing category, we don’t have that luxury. I wish I could move a document I use often from 25.18 to something like 25.01 for significance, but it was created .18 and will stay .18, and that’s okay as I still know where it fits in the structure and can find it just as quickly.
4 Likes