summaryrefslogtreecommitdiff
path: root/doing.mdwn
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2012-04-17 22:46:31 +0100
committerLars Wirzenius <liw@liw.fi>2012-04-17 22:46:31 +0100
commit2a58c9a36e0e4fe5a3772555e8dd53c8260cfc7f (patch)
tree0567af7fbd1dc62cf24495bd5082b74b30c25da5 /doing.mdwn
parent652f31fda22ffe29d15ad586581a880eb32ad737 (diff)
downloadgtdfh.liw.fi-2a58c9a36e0e4fe5a3772555e8dd53c8260cfc7f.tar.gz
Added a note of what to do when you've done something
Thanks, Francois Marier, for the suggestion.
Diffstat (limited to 'doing.mdwn')
-rw-r--r--doing.mdwn12
1 files changed, 12 insertions, 0 deletions
diff --git a/doing.mdwn b/doing.mdwn
index f5751e4..3e6612d 100644
--- a/doing.mdwn
+++ b/doing.mdwn
@@ -29,4 +29,16 @@ so when I tell myself that they've not been there for very long, I
believe myself. That's why I put a date (at least year and month) on
every next action, so I don't believe my own lies.
+After you've done something
+---------------------------
+
+When you're finished with a next action, you can delete it from your list,
+or cross it over, or otherwise mark it as done. This can be a very
+satisfying feeling.
+
+Instead of deleting, you may also want to move the item from your
+next actions list to a list of finished stuff. Such a log can also
+be quite satisfactory to read, later on. I've found that deleting
+things gives me more pleasure, though, and I keep track of what I've
+done using a journal instead.