Add future work to readme

1 files changed, 11 insertions, 1 deletions

diff --git a/README.md b/README.md
index 3fa3017..656590c 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,7 @@
 # Todoist Repeater
 
+## Background
+
 I use Todoist as my todo app. I add tasks to my Inbox, sorted descending by date added. However, repeating tasks in Todoist don't work with my workflow: they stay in a fixed position in the list, and just refresh the due date.
 
 What I want is a task that appears on a given interval, disappears when it's completed, and, when it's time to do it again, reappears at the top of the list.
@@ -13,6 +15,8 @@ Some examples of tasks that I want to recurr in this way:
 - every six months, wash and condition the leather sofa
 - every three months, do a reflection on how I'm feeling about work
 
+## Design
+
 The idea for this program is to:
 
 - have a list of tasks that specifies the task name and the recurrence (interval, start and end date)
@@ -43,4 +47,10 @@ At program start, and every minute thereafter:
 - if we have not seen it, add the line to the hash of seen lines; then, add it to the scheduler
 - if there were any lines that we did not see during this read of the file, but that we saw previously, remove them from the scheduler
 
-The lines will be formatted like a cron file, but instead of a command, we will simply have the name of the task to be created.
\ No newline at end of file
+The lines will be formatted like a cron file, but instead of a command, we will simply have the name of the task to be created.
+
+## Future work
+
+It turns out jobs can be added AND removed by an ID that is returned from the Add function. It could be interesting to add/remove based on the last seen map (with the job IDs), instead of completely recreating all the jobs if the input file changes.
+
+We should probably retry failed network requests. It would not be great to have a temporary connectivity issue lead to missing an important task!