5 ms·
Since 2012 I've been keeping task files to document all the stuff I work on. Most are job related. This comes in handy when I need to re-visit something I've wo
by NorSoulx 5y ago
Since 2012 I've been keeping task files to document all the stuff I work on. Most are job related. This comes in handy when I need to re-visit something I've worked on previously, sometimes going several years back in time. The task files are plain text files which are quick to create and update, and I use Sublime Text or VIM to edit. I do both development and operational related tasks, and can work on many tasks during a day. The trick is documenting in the task files right away before the details are wiped from my memory. When looking things up, I usually search by file name, or content, or both. Having documented a task previously can save time when returning to a similar task at a later date.
I use a naming format for the task file, including the date and a short task description, e.g:
task.2021.12.23.short.task.description.txt
Number of task files created since 2012:
Task files: 18231
Total size: 350 MB
For each day I also create a worklog of the tasks I've been working on that day (including minutes spent).
Since 2012 I've registered 2540 daily worklog files:
ls -l task.????.??.??.worklog.txt |wc -l
2540
The worklog files are also used to estimate time necessary to complete similar or recurring tasks.