Pomodoro Technique Breaks

2 points·CaveStoryTeller··4 comments

1. I never know what to _do_ during the breaks. Any suggestions? 2. When I code software, the break may come when I am just ever so close to figuring out a bug or coding the last line of a procedure. It is irritating to have to take a break and then remember in 5 or 15 minutes what did I mean to code just there. Any thoughts on working with these two problems I have with Pomodoro? Maybe a different method? Thanks!

View on HN

Don't take the break if you don't want to. If you think of the break will make you more productive take the break. Sometimes pomodoro tells me to take a break and I tell pomodoro to STFU. Then I finish the freaking work! Remember this is a technique to make you more productive, not hold you back!

Exactly. Breaks aren't for when you're "in the zone" but "in the grind." They're best for breaking out of a haze when you're just spinning your wheels or for reminding you to refresh your batteries a bit (physically, mentally) when you are slogging through some tedious work.

You'd be surprised how often breaks hit reset when you are mindlessly "working hard" but not working effectively. You come back with new energy and perspective.

YMMV, but I try to drink a bit of water, maybe do some pushups if I'm at home, fix my eyes by looking out the window for 20 seconds, maybe munch on something. Basically, all the sensory and bodily stuff you don't do when you're coding. It's also a good time to top up your coffee, if that's your thing.

When Pomodoro says its time to take break, treat it as a signal. If you are not in the middle of a task, take a break. And if you are in the middle of some task then complete that task / bug but don't move to another one, just take a break.

Reply on news.ycombinator.com