summaryrefslogtreecommitdiff
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
parentf9679d48e3b8f7d76abb64a456c9062b9c020a99 (diff)
downloadgtdfh.liw.fi-652f31fda22ffe29d15ad586581a880eb32ad737.tar.gz
Added a few notes about how much time doing stuff my way takes
-rw-r--r--journalling.mdwn9
-rw-r--r--news.mdwn1
-rw-r--r--review.mdwn7
3 files changed, 16 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
diff --git a/news.mdwn b/news.mdwn
index bd0e977..6fe9f6d 100644
--- a/news.mdwn
+++ b/news.mdwn
@@ -12,4 +12,5 @@ Since the alpha-2 tag (April 7, 2012):
sidebar.
* Added this news page.
* Added pseudo-code for inbox processing.
+* Added a few notes about how much time doing stuff my way takes.
diff --git a/review.mdwn b/review.mdwn
index 310edac..69148ee 100644
--- a/review.mdwn
+++ b/review.mdwn
@@ -46,6 +46,13 @@ Here's my checklist for doing a weekly review:
* Review areas of focus, goals.
* Re-process inbox.
+It usually takes me a couple of hours per week to do a good review of
+the entire system. Sometimes more, if I do a thorough review of all
+my open bug reports, for example, but I only do that if I have the
+time, and haven't done it in a while. (A thorough review of the bug
+reports tends to mean reading through everything, and sometimes checking
+that bugs still exist.)
+
It's common for me to postpone doing a review, if I'm tired or busy
or have any of a number of other excuses. If it gets really bad,
I postpone the