I am not aware of any specific studies that focus on a 30/30 cycle, but there's plenty of research that suggests taking regular breaks is good for you.
The ideal work-break routine is about the work you do, if you control your own time and, of course, what suits you best. For me, I’ve discovered that routine tasks, like writing documentation, do well with a 30-30 cycle. However, when I’m working on problem definition, such as programming and especially debugging, I need more focused time, but I do make sure to take a regular break every hour.
The most important tool for AI-assisted coding isn't an agent framework. It's a timer that forces you to take regular breaks.
Back in 2010 Chetan Surpur introduced the Magic Work Cycle productivity technique. The idea: 30 min focused work, 30 min genuine break.
https://chetansurpur.com/blog/2010/11/magic-work-cycle.html
Regular breaks trigger diffused mode thinking, where the brain subconsciously makes connections that lead to "aha!" moments.
I built a completely free iOS and Apple Watch app for this. Maybe others find it useful too.
Is there anything outside of the origination of the 30/30 idea that backs up the claim, versus something more mainstream like Pomodoro?
I am not aware of any specific studies that focus on a 30/30 cycle, but there's plenty of research that suggests taking regular breaks is good for you.
The ideal work-break routine is about the work you do, if you control your own time and, of course, what suits you best. For me, I’ve discovered that routine tasks, like writing documentation, do well with a 30-30 cycle. However, when I’m working on problem definition, such as programming and especially debugging, I need more focused time, but I do make sure to take a regular break every hour.