This sounds like a neat idea, but the implementation looks more complex than for pomodoros, and you’ve provided a big list of upsides with zero downsides. What makes you think this is actually more useful than whatever people are doing right now? I guess that explanation is supposed to come in part 2?
Others would have to report whether they find it more useful than what they do now (eg Pomodoro), but the reason I think it may well be is indeed the fact it fixes the various Pomodoro problems.
Re new downsides Third Time itself introduces, the one I’m aware of is indeed its extra complexity—hence it is best implemented in an app. But if others find other downsides, I’d be interested to hear of them.
(Alas I haven’t got round to finishing Part 2 yet—been busy with other things, notably analyzing the academic research into what the best ways to spend a break are, which I’ll write up in due course.)
This sounds like a neat idea, but the implementation looks more complex than for pomodoros, and you’ve provided a big list of upsides with zero downsides. What makes you think this is actually more useful than whatever people are doing right now? I guess that explanation is supposed to come in part 2?
Others would have to report whether they find it more useful than what they do now (eg Pomodoro), but the reason I think it may well be is indeed the fact it fixes the various Pomodoro problems.
Re new downsides Third Time itself introduces, the one I’m aware of is indeed its extra complexity—hence it is best implemented in an app. But if others find other downsides, I’d be interested to hear of them.
(Alas I haven’t got round to finishing Part 2 yet—been busy with other things, notably analyzing the academic research into what the best ways to spend a break are, which I’ll write up in due course.)