10am and on. Short intervals, different people, random issues. Phone ringing, interrupting already fragile processes of thought. That mode again: Communicate, collect, write down, forget at least for now. There will be a time to wrap it all up. Later. Maybe.
9am and on. Plan for long, cut things short, and try to figure out what to spend time gained in between. Never running short of tasks to fill these kinds of voids but always overestimating ones on cognitive abilities while dancing in between these. Stories of fog and noise, not always pleasant.
4pm and on. Windows closed. In many ways most likely. The afternoon's all sun and no wind and a bit of tension and way too much coffee again. Still trying to figure out the right moment for now to lay down todays tools and tasks and accept there'll of course be leftovers for Monday. Multitasking, microtasking and the peculiar aspects both has, on productivity and on ones own mental state.
Heading for 9am. Day's filling up quickly, first calls, first head-scratching moments, first counting of breath to slow down a bit. (Wrestling, again, that unsettling feeling of handling too many fragments to really solve the puzzle, or any puzzle at all.)
Been in my playlist this morning, and, though obvious in some ways, still added some points and leaves me pondering that particular issue more than usual:
At the outset, including for the IBM System three sixty, the computer with a single CPU was not actually multitasking. It was doing the same thing that our brains do. It was jumping back and forth between tasks really fast to make sure it was doing them both adequately. So when we kind of figured out that there was a problem with processing, that there were limits to it. We established very quickly something called a processing bottleneck. That, yeah, there is. It's documented humans do not multitask to begin with, and when we try to multitask, the results are terrible.