I’ve gone super organized to absolute dumped folders over the last decade. If you have a NAS, get organized. Everything on your computer, do more loosely.
My rule with hobbies like electronics like PCB design prototyping and breadboarding, 3d printing, roadie bicycle stuff, etc., is that my collection of crap and organization scheme has failed when I forget what I have or can’t find it when I need it. I avoid the rabbit hole of making organization a priority project or taking it too far by only targeting what I need to do in order to prevent these situations of missing items.
The same goes for digital storage. My organization must be intuitive so that a year or more from now, I know where to find the thing at a glance.
One trick I learned from managing multiple connected point of sale systems for a chain of retail stores is to name your files in a way that sorts naturally. For instance, use year-month-day in file naming as opposed to nonsensical date standards. With bikes in the bike shops it was
"Bike-
MTB/RDR/TRI/HYB/KID-
XS/SM/MD/LG/XL
(Brand)-
(Model)-
(Year)"
Without a sales staff performing any searches I wanted bike types and sizes to naturally sort. I needed them to see exactly what was in stock in their store without thinking about the computer. I wanted them to immediately identify the range of choices available so that they could easily tell the customer what choices they have for immediate gratification. This involved me normalizing bike sizing to fit within my naming constraints as no bikes are sized the same way across brands. This is still how I think about naming schemes, they should always have sorting functionality built in. But don’t take it so far that you can’t remember the way you organized stuff without refamiliarizing yourself with the details.
I’ve gone super organized to absolute dumped folders over the last decade. If you have a NAS, get organized. Everything on your computer, do more loosely.
My rule with hobbies like electronics like PCB design prototyping and breadboarding, 3d printing, roadie bicycle stuff, etc., is that my collection of crap and organization scheme has failed when I forget what I have or can’t find it when I need it. I avoid the rabbit hole of making organization a priority project or taking it too far by only targeting what I need to do in order to prevent these situations of missing items.
The same goes for digital storage. My organization must be intuitive so that a year or more from now, I know where to find the thing at a glance.
One trick I learned from managing multiple connected point of sale systems for a chain of retail stores is to name your files in a way that sorts naturally. For instance, use year-month-day in file naming as opposed to nonsensical date standards. With bikes in the bike shops it was
Without a sales staff performing any searches I wanted bike types and sizes to naturally sort. I needed them to see exactly what was in stock in their store without thinking about the computer. I wanted them to immediately identify the range of choices available so that they could easily tell the customer what choices they have for immediate gratification. This involved me normalizing bike sizing to fit within my naming constraints as no bikes are sized the same way across brands. This is still how I think about naming schemes, they should always have sorting functionality built in. But don’t take it so far that you can’t remember the way you organized stuff without refamiliarizing yourself with the details.