Re:Calendar.txt
by bArray on Friday February 28, 2025 @09:44AM
(#43206160)
I think the format I suggested would parse in markdown, but I created it pre-markdown.
For me the best parts are:
1. You could write a parser very quickly.
2. It's very easy to edit and add to as a human.
3. It can easily be tracked in git or via a diff-based tool.
I did already think about the repetitive tasks, a long time ago I used to have a tool that would look at the past tasks and recommend future tasks (with appropriate distributions). One example was booking a dentist appointment every 6 months, even if I forgot to schedule something it would remind me to book one in, dismiss it or push it back.
For me the best parts are:
1. You could write a parser very quickly.
2. It's very easy to edit and add to as a human.
3. It can easily be tracked in git or via a diff-based tool.
I did already think about the repetitive tasks, a long time ago I used to have a tool that would look at the past tasks and recommend future tasks (with appropriate distributions). One example was booking a dentist appointment every 6 months, even if I forgot to schedule something it would remind me to book one in, dismiss it or push it back.