The short of it is to structure files in four categories:
Projects (with a definable scope and end)
Areas of responsibility (stuff that needs to be done repeatedly or constantly without any defined “end”, like timesheets or budget plans)
Resources (learning material, reusable assets)
Archive (finished / abandoned projects, areas no longer relevant for you, resources you’re not longer interested in)
I suck at the “abandoned project” part, because I refuse to accept when I’m not gonna keep at something any more, and sometimes have stuff lingering in my “Areas” that should long be archived. I also have some things that are kinda perpetually ongoing developments without any clear “end”, although each increment of work does, so they occupy some hybrid space between Area and Project. I’ve put them in Projects anyway, because the point is to help me find things and making “Projects” the place to find “Things I’m working on” is easy enough.
I learned of the PARA method somewhere on Lemmy, and found it (or an adapted version) really well-suited for myself:
https://fortelabs.com/blog/para/
The short of it is to structure files in four categories:
Projects (with a definable scope and end)
Areas of responsibility (stuff that needs to be done repeatedly or constantly without any defined “end”, like timesheets or budget plans)
Resources (learning material, reusable assets)
Archive (finished / abandoned projects, areas no longer relevant for you, resources you’re not longer interested in)
I suck at the “abandoned project” part, because I refuse to accept when I’m not gonna keep at something any more, and sometimes have stuff lingering in my “Areas” that should long be archived. I also have some things that are kinda perpetually ongoing developments without any clear “end”, although each increment of work does, so they occupy some hybrid space between Area and Project. I’ve put them in Projects anyway, because the point is to help me find things and making “Projects” the place to find “Things I’m working on” is easy enough.