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.
Didn’t read the code yet, but stuff like this tend to be brittle. Do you do something clever around stack overflow, function return overwrite or would that just mess up all coroutines using the same stack?
Not only the manual, but Gnus itself. I remember this guy from the university (UiO) when he started working on Gnus. He was a small celebrity among us informatics students, and we all used Emacs and Gnus, of course.
Who knows? I believe you are right that he was forced into action when the Senate pulled him back from Gaul [1] with the intention of bringing him to court. If he did not have a plan to set himself up as a dictator, at least he pivoted beautifully once he saw the opportunity and Pompey folded. That at least was a true startup move. 1. edit: Gaul not Germany
By crossing the Rubicon with his one legion, Caesar put himself on a path of no return and in open conflict with the Senate and Pompey who vastly outnumbered him military. There was no guarantee that he would succeed. Upon crossing he declared "alea iacta est", knowing full well what he set in motion. Edit: My point here, is simply that not everyone would cross the Rubicon. Most would turn around, deeming the risk too high. Related to a startup, the risk for failure is high if you look at the statistics. If it is a "sure thing" you are not really doing a startup or you are conned. A startup kind of by definition has to be a high risk venture. Like PG's example of a merchant ship going to the East Indias in the 17th century.
I don't disagree, once you have crossed the rubicon. When Julius Caesar _actually_ crossed the Rubicon, the risk was immense and there was no guarantee of a successful outcome. That's what I mean, going all in on a risky adventure is not for everyone and if you analyse and think too much about it, few will want to take the jump. However, once you have crossed and are in the "battle" then of course you will use all the tactical advantages you can and try "shifting odds of success".
One trait most successful founders have is not being overly analytical. This correlate with higher education as well, the higher, the more analytical. Creating a successful startup is basically a lottery and it almost does not matter what idea you come up with. In this metaphor, smart and analytical people will not buy a lottery ticket because the cost vs the chance to win is just too small. But if you don't buy a lottery ticket you most certainly cannot win the lottery.
"terminal illness" is the keyword here and what "no code" is associated with in medical terms. A heart attack, a stroke and similar acute traumas should definitely be treated. These patients may live a close to a 100% life afterwards.
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.