3 ms·
Projects go in <year>/<name> Every year I move the currently active projects forward as I touch them. Unless it makes sense to leave them in the old year. They
by natch 6y ago
Projects go in <year>/<name>
Every year I move the currently active projects forward as I touch them. Unless it makes sense to leave them in the old year. They aren’t archived, can still be worked on, they just aren’t necessarily cluttering the current year. And I have a script (bash function) for navigating them. ‘work’ cd’s me to the current year. ‘work ——-‘ (3 dashes) goes 3 years back. ‘work 2016’ goes straight to that year.
Projects are created at the drop of a hat. Super lightweight, no need for it to be important, formal, or even mine. Cloning something from github? Goes right into the current year.
The current year is in dropbox. Everything else is not. There’s also a special directory that holds stuff that doesn’t go in the cloud.
Also have a script for labeling the current directory with tags for easy grepping.
It works ok. There are a few rough edges. Like I might be playing with markdown one year and then again a few years later and end up with two markdown directories, in different years. Whatever. I can usually find old work for reference pretty easily.