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?
Each coroutine is running on its own stack. They are fixed size stacks, at least for now, so that could be a tender point, but I place some sentinel values at the end to try to capture it in an assert() instead of just letting it crash. I did not think it worth the effort and speed penalty to implement growing stacks yet. However, I do catch any coroutine function returns safely instead of letting them fall off the end of their 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.
I'd forgotten that! Yeah, I believe Lars also wrote a huge chunk of the current Gnus. I stopped using it a while back and maybe someone else came along and rewrote it again, replacing all his code, but I don't think that's the case.
Gnus was absolutely delightful back in the day. I moved on around the time I had to start writing non-plaintext emails for work reasons. It's also handy to be using the same general email apps and systems as 99.99% of the rest of the world. I still have a soft spot in my heart for it.
PS: Also, I have no idea whatsoever why someone would downvote you for that. Weird.
They added the addictive "superior" to describe mysqls implementation in their docs. That's the entire change. No code changes. Seems like a petty change antithetical to good documentation.
The effect of globalization is that the west is bringing the rest of the world over the poverty line at the cost of deteriorating ourselves. Hard to say how this will end.
Really cold weather doesn’t have much wind. It’s metrology. Without long term storage, wind power during the winter in the northern hemisphere is just meh. Same with any variable renewable energy source. Instead of celebrating the few times renewable energy actually produces energy when it’s needed we should celebrate every time a new Nuclear power plant comes online.
Generally speaking extreme temps don’t coexist with wind for very long. Wind, after all, convects air around, and fundamentally you’ll have the extremes mixed with non-extreme air.
Like a heat dome, for example, is only possible when there’s no wind to push the dome away.
Exactly this (plus floating point types and unsigned qualifier) and done. It’s standard C, there is no need to invent yet another unnecessary “type” system for standard C native types. I do like bool though.
Isn’t this the whole point of John Searl’s “the Chinese room” thought experiment? But does it matter what is actually going on inside the room, if the effect and function is indistinguishable? Edit: after conferring with ChatGPT, Searle’s point like yours is that the man in the room doesn’t understand Chinese, he is just manipulating symbols, but from the outside, the man in the room seems to speak fluent Chinese.
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.
reply