3 ms·

Not exactly TODO but I do something similar. I have a directory with text files and images named like: 2022_03_20_1_short_description.txt or 2022_03_20_2_confi

by ajuc 5y ago

Not exactly TODO but I do something similar. I have a directory with text files and images named like: 2022_03_20_1_short_description.txt or 2022_03_20_2_config_screenshot.png The names are mostly to group images with related text files when I grep later. I create the file at the start of each work day, write a few lines of TODO for the task I'm working on, and whenever I copy-paste something that seems relevant - I paste it there and leave it with a few empty lines as separator. If image is better I screenshot only the relevant part and possibly add some notes with paint and save it in that directory. When I investigate some error I paste stacktrace there. And when I find solution - I paste the link or the git commit or JIRA task or description. If I do several unrelated things in the same day I sometimes create several files, but it doesn't matter that much. It saved me A LOT of time. A quick grep and I have all the context of some error that last happened 8 months ago.

nameless_me 5y ago
Some may think it primitive but your workflow is fast, efficient, backups up easily (I write a simple DOS batch file which copies all new or updated files to a USB stick) and backs up to the cloud easily as well. Grepping to find files by date is easy and if a more detailed document had to be generated, you have pandoc or Libreoffice to produce PDFs using those source data files.
anon2020dot00 5y ago
I do something close to this but with even less organization up-front. I label my text file as <day>.txt, like 21.txt, since it is under a month folder. For images, I take screenshots with the Snag-It software which automatically assigns a time-based filename to the screenshot and stores it in a central directory. So, at the start, my text files and screenshots have basic filenames which are time-based. Later-on, I'll create an index for the text files with a Google Doc; an index which is a basic list of the text files with some brief bullet-point comments describing each one. Actually, for text files, I just describe it with a comma-delimited list of tags/titles per file.

by ajuc 5y ago

nameless_me 5y ago

Some may think it primitive but your workflow is fast, efficient, backups up easily (I write a simple DOS batch file which copies all new or updated files to a USB stick) and backs up to the cloud easily as well. Grepping to find files by date is easy and if a more detailed document had to be generated, you have pandoc or Libreoffice to produce PDFs using those source data files.

anon2020dot00 5y ago

I do something close to this but with even less organization up-front. I label my text file as <day>.txt, like 21.txt, since it is under a month folder. For images, I take screenshots with the Snag-It software which automatically assigns a time-based filename to the screenshot and stores it in a central directory. So, at the start, my text files and screenshots have basic filenames which are time-based. Later-on, I'll create an index for the text files with a Google Doc; an index which is a basic list of the text files with some brief bullet-point comments describing each one. Actually, for text files, I just describe it with a comma-delimited list of tags/titles per file.