summaryrefslogtreecommitdiff
path: root/journalling.mdwn
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2012-04-17 22:43:14 +0100
committerLars Wirzenius <liw@liw.fi>2012-04-17 22:43:14 +0100
commit652f31fda22ffe29d15ad586581a880eb32ad737 (patch)
tree20d27d4e43a9b0039272d2f695aff1079b575056 /journalling.mdwn
parentf9679d48e3b8f7d76abb64a456c9062b9c020a99 (diff)
downloadgtdfh.liw.fi-652f31fda22ffe29d15ad586581a880eb32ad737.tar.gz
Added a few notes about how much time doing stuff my way takes
Diffstat (limited to 'journalling.mdwn')
-rw-r--r--journalling.mdwn9
1 files changed, 8 insertions, 1 deletions
diff --git a/journalling.mdwn b/journalling.mdwn
index 5a708d4..7b41093 100644
--- a/journalling.mdwn
+++ b/journalling.mdwn
@@ -27,13 +27,20 @@ journal](http://liw.fi/obnam/journal-dump/) for the amusement of
the Internet.)
Journalling can require a bit of effort,
-but it can also be very helpful.
+but it can be very helpful.
The process of expressing thought processes in writing makes them more
explicit, and often more clear.
Anything that's hard to express tends to be unclear in the head, too.
Later, a journal can be helpful to answer things like
"what was I thinking?".
+Apart from effort, journalling requires time. I type reasonably fast,
+so the extra time to write down my thoughts in some detail, as prose
+that's easily readable later, is not a big overhead. Others might prefer
+to keep a handwritten journal, and only jot down the more important bits,
+and stick to keywords. Or record audio, perhaps. Experiment with what works
+for you; maybe you'll find something, or maybe you'll find it's all wasteful.
+
The act of journalling should be as easy as possible.
There should be minimal steps required to start writing,
and the only requirement for the actual text should be that it's expressing