4 ms·
>Extending the length of the 25 minute pomodoro. If I’m in the deep work flow, I’ll continue past the 25 minute alarm. Someone told me that its 25 minutes beca
by dominotw 10y ago
>Extending the length of the 25 minute pomodoro. If I’m in the deep work flow, I’ll continue past the 25 minute alarm.
Someone told me that its 25 minutes because it prevents you from building too much context in your head that prevents you from taking a break at 25 min mark. You can't do creative work if your brain is filled with lot of context. eg: TDD goes really well with pomodoro because you are only thinking about the next test and you can break on failing test so you can pick up right back. Is this a reason for 25 min for Pomodoro?
- cpbotha 10y agoI used to advise friends to stick to the 25 / 5 minute break, but more because I thought that this enabled one to sustain this rhythm for longer. However, currently I'm experimenting with longer pomodori, with the reasoning that if I'm in the flow / deeply working, the value of that flow is too great to take the risk that I might break it because of an arbitrary break. I think a better advice now would be to experiment, and see what suits you best in terms of sustainability, output and fulfilment. Today I my pomodori were between 25 minutes and an hour. It's home time now, but I feel great due to a large part of the day filled with flow.
- josephg 10y agoI'll be honest; I've never understood this mindset. The idea of purposefully interrupting my flow every 25 minutes, explicitly dropping my context is ghastly. If you could design an ideal hell for me it would involve hard, interesting programming problems and constant (every ~10-20 minute) seemingly random external interruptions. (Its not an accident that I don't have children.) Most of the work I'm really proud of happens in 1-1.5 week long coding binges, during which I code ~14 hours a day, don't eat well and don't get outside much. During that time my entire being is oriented around the problem. I sleep when I'm too tired to be productive and wake up with the problem spilling out of me. I usually need a couple of weeks recovery time afterwards during which I'm pretty useless for anything thats not light and fluffy. But that time is 100% worth it. If I could work at that intensity for 1 week out of each month I'd be more productive than I have been at any 9-5 job I've ever had. Well, for a given definition of productivity. So I guess I like pomodoros - I just think they should be about 1 week in length.
- ajmurmann 10y agoDo you mind me asking if you are self-employed? The rhythm you describe very exciting, but impossible in most work places. What you are doing though is probably the only work pattern that surely qualifies as "a sprint".
- brachi 10y ago> I just think they should be about 1 week in length. > I usually need a couple of weeks recovery time And exactly like a real sprint (running very fast) a period of resting is necessary after such an effort, usually longer than the execution time spent.
- ajmurmann 10y agoYes! I couldn't agree more. I'm happy to sprint. If do it much rather than a marathon. But only if I get a break after it. Otherwise it's a marathon that you start out running like it was a sprint and fail.
- beat 10y agoI find that approach works best for about three days. I suppose three days of work is all my little brain can hold! Three days of crunch followed by one or two days of downtime is insanely productive for me.
- shamano 10y ago"From a practical standpoint, our research suggests that, when faced with long tasks (such as studying before a final exam or doing your taxes), it is best to impose brief breaks on yourself. Brief mental breaks will actually help you stay focused on your task!” http://psychcentral.com/news/2011/02/09/taking-breaks-found-to-improve-attention/23329.html http://psychcentral.com/news/2011/02/09/taking-breaks-found-...
- KurtMueller 10y agoI would say you should adjust the timer to whatever fits your lifestyle. I've always understood the pomodoro timers as 25 minutes of getting down into the trenches and then taking 5-10 minute breaks to think about whatever you're doing from a high level overview.
- clentaminator 10y ago> You can't do creative work if your brain is filled with lot of context. Intuitively I'd assume that the context and information in working memory is precisely what enables one to do "deep work". Constantly requiring you to rebuild your in-memory cache feels like it would lead to sub-standard work.
- jasim 10y agoTDD is probably not the best way to do deep work. http://ravimohan.blogspot.in/2007/04/learning-from-sudoku-solvers.html http://ravimohan.blogspot.in/2007/04/learning-from-sudoku-so... About context, this is from Programmers at Work by Susan Lammers, interviewing John Page, author of the PFS productivity suite, famous in the late 80s. Lammers: Why are programmers so obsessive? Page: You constantly try to hold the state of the entire system you're working on in your head. If you lose the mental image, it takes a long time to get back into that state. It's like being an air-traffic controller who has nine planes in his mind and knows exactly where they're all going. Distract him by asking him when his shift is over and he loses those planes--the model he had in his head. In programming, a big complicated model is very efficient once you're in the groove. If you get out of it, you've got to work on it quite a while to get back in.
- mrec 10y ago> You can't do creative work if your brain is filled with lot of context I think you can, but the big risk is that what you produce becomes incomprehensible to anyone without all that context filling their brain, including you next week. (Not saying I'm in favour of deliberate interruptions, just that this might be an argument for them.)
- Rainymood 10y ago>Someone told me that its 25 minutes I used to believe this as well, then I tried 50 minutes, 10 minutes break and I like it way better. Try it for yourself and see which one works best for you!
- t594 10y agoBeen pomodor'ing for 5yrs on/off... what i like about the 25, is it makes it a challenge, like a short race. "Can I really get this done in only 25?" It makes me work harder, and its a short enough time that i know i CAN give 100% focus if i start it with the right mindset. Also, I never realized how short 25mins actually was. And working like that helps me estimate programming tasks. It used to be that someone would ask, "how long will it take you to do X?" I would always say, "an hour or two". Then I realized how short an hour actually is... only 2 pomodoros... and wow, that went by fast. If I'm not done with a task, the trick I use for not losing focus between Pomodoros is to leave an easy bug, or purposely break something easy and leave a "//todonext". I can't remember who, but some famous sculptor used this technique. He would purposely mess up an easy part of his sculpture, so that the next day, he had a "softball" to fix that easily got him back into work mode. (anyone know this phenomenon?)