4 ms·

I really like that the author describes work as fitting into two categories: the really focused stuff he uses the Pomodoro technique for, and all the peripheral

I really like that the author describes work as fitting into two categories: the really focused stuff he uses the Pomodoro technique for, and all the peripheral stuff. I think it's a very important distinction and I'm keenly aware of it in my daily work. I've found there are two advantages of Pomodoro that are under-appreciated: 1. At the end of your day you have an integer number of "Pomodoros" done. An integer number is very easy to grasp and compare with other days. So you have a very strong sense for how well you did with your day, or how well you are doing so far in the day. It's a powerful thing and it keeps you honest. 2. After you have used the technique for a while, the timer you use not only serves as a timer, but its start mechanism/button/gesture/whatever actually serves as some sort of psychological "switch" that puts your mind in work mode. On mornings when I am lacking a little motivation, I can just start the timer and I'll get into gear. It's not magic, but when I need a little extra kick the timer does it very well.

redrummr 11y ago
3. You get great at estimating work in 25-minute chunks. Being able to exert that level of control is cool. 4. It directly taps into several other productivity systems like the X Method.
- teleclimber 11y ago
  5. Sometimes when you have just 30 seconds left on your Pomodoro you start blasting away on your keyboard like you're one of those hackers in the movies. It makes you realize how much you can do in 30 seconds.
  - mikekchar 11y ago
    I've actually started to do 5 minute pomodoros. It's insane, but also a lot of fun. Especially when pair programming it's great because you can start discussing an issue and suddenly you look at your timer and think, "Woah... 30 seconds just went by. Let's just try it one way. We can change it later if we want". I also write down what I've done at the end of the 5 minute pomodoro. If it is "nothing", then it's a good flag to say that I have a problem.

redrummr 11y ago

3. You get great at estimating work in 25-minute chunks. Being able to exert that level of control is cool. 4. It directly taps into several other productivity systems like the X Method.

teleclimber 11y ago
5. Sometimes when you have just 30 seconds left on your Pomodoro you start blasting away on your keyboard like you're one of those hackers in the movies. It makes you realize how much you can do in 30 seconds.
- mikekchar 11y ago
  I've actually started to do 5 minute pomodoros. It's insane, but also a lot of fun. Especially when pair programming it's great because you can start discussing an issue and suddenly you look at your timer and think, "Woah... 30 seconds just went by. Let's just try it one way. We can change it later if we want". I also write down what I've done at the end of the 5 minute pomodoro. If it is "nothing", then it's a good flag to say that I have a problem.