Comments on: GTD, OmniFocus, and Pomodoros Part II: How the Pomodoro Works http://kouroshdini.com/2009/11/30/gtd-omnifocus-and-pomodoros-part-ii-how-the-pomodoro-works/ by Kourosh Dini, MD Tue, 07 Sep 2010 04:46:57 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Kourosh http://kouroshdini.com/2009/11/30/gtd-omnifocus-and-pomodoros-part-ii-how-the-pomodoro-works/comment-page-1/#comment-1619 Kourosh Mon, 30 Nov 2009 16:49:46 +0000 http://kouroshdini.com/?p=2826#comment-1619 The perspective you note is spot on. I hadn't quite thought of it, but you're right: You can decide on the path you're on and more actively decide if it's still a good one. The nature of the break itself then becomes important in that one doesn't run off to do something else, rather more actively lets the mind rest. The perspective you note is spot on. I hadn’t quite thought of it, but you’re right: You can decide on the path you’re on and more actively decide if it’s still a good one.

The nature of the break itself then becomes important in that one doesn’t run off to do something else, rather more actively lets the mind rest.

]]> By: Andrew Ebling http://kouroshdini.com/2009/11/30/gtd-omnifocus-and-pomodoros-part-ii-how-the-pomodoro-works/comment-page-1/#comment-1618 Andrew Ebling Mon, 30 Nov 2009 16:41:50 +0000 http://kouroshdini.com/?p=2826#comment-1618 I've been using the Pomodoro technique for a month or so and have found it to be dynamite when used in conjunction with GTD. Initially I decided to ignore breaks if I was "in the flow", however I've since learned there is great value in always taking breaks (at least when coding): - it restores perspective; it's easy to get bogged down in something that in the bigger picture of things, isn't that important. Or there's another equally valid approach which could be taken. Coming back fresh after a break restores perspective. - it provides a break for your hands and eyes, not just your mind. Anyone making heavy use of a computer keyboard and screen is at risk of RSI and eye-strain. Taking a 5 minute break every 25 mins is an important precautionary step. - it promotes a rhythm of working and also makes you more aware of the passing of time. If time is running away with you on a relatively unimportant task, you notice if you always stop of 25 mins. I’ve been using the Pomodoro technique for a month or so and have found it to be dynamite when used in conjunction with GTD.

Initially I decided to ignore breaks if I was “in the flow”, however I’ve since learned there is great value in always taking breaks (at least when coding):

- it restores perspective; it’s easy to get bogged down in something that in the bigger picture of things, isn’t that important. Or there’s another equally valid approach which could be taken. Coming back fresh after a break restores perspective.

- it provides a break for your hands and eyes, not just your mind. Anyone making heavy use of a computer keyboard and screen is at risk of RSI and eye-strain. Taking a 5 minute break every 25 mins is an important precautionary step.

- it promotes a rhythm of working and also makes you more aware of the passing of time. If time is running away with you on a relatively unimportant task, you notice if you always stop of 25 mins.

]]>