Hacker News Reader

Comment by necessary | Hacker News Reader

Nice work! This is very visually pleasing and I think the addition of light task management w/ optional estimates is great!

In general though, does anyone else feel like using a pomodoro timer ruins any chance at intense focus during the workday? I don't doubt the effectiveness for others, but personally, it feels like taking frequent breaks from work lowers my overall productivity because I'm leaving and entering focus so often. This is also the reason I don't like taking walks in the middle of the workday, unless I'm working on a problem that needs more thought than action. The days that I stay in-focus for the full work day are usually my happiest and most productive.

View on HN

From my experience, it's useful when I'm not able to concentrate on a specific task. The feeling of blocking time for a specific task is helpful for my mind to fully focus n that.

Anyway, 25 minutes is just the standard but you can use longer periods. For example, I use blocks os 1 hour where I block all my distractions, knowing that this time is just for that specific duty.

> does anyone else feel like using a pomodoro timer ruins any chance at intense focus during the workday

You don't have to use it for projects where you're naturally in flow and can maintain intense focus without productivity tools.

The Pomodoro Technique is for those who /get out of flow/ easily and can't be productive without taking breaks often.

I've used it, and it was for tasks where I was able to hold the state of a program's structure even when AFK for ten minutes. I've noticed lethargy and fatigue sets in every 10 minutes, since I'm usually chaired and my wrists have mild RSI which needs to be repaired via breaks.

There is a law of diminishing returns the longer you are stationed at a desk doing focused work. Your boss might not like all your breaks, but you can calmly explain 'It's science!' to them.

It's hard to stay in-focus for 8 hours without amphetamines. I find that I have to eat and pee and stretch now and again.

But I've had trouble with 25 minutes being a bit too short for some more technical tasks. Is there any literature about optimal work durations for highly abstract tasks? Programming architecture, super complicated mechanical cad, some physics or math calculations...

It takes a long time to load the model into your working memory, so restarting a lot is very painful. Is it better to actually follow the pomodoro model and do 25/5? Or is 50/5 more productive? Maybe 50/10 or 40/5? A few professions get the autonomy to control their work at that level of granularity, and we'd love more guidance than "do what works best for you, bb."

Reply on news.ycombinator.com