2 ms·
The argument you’re making is the same reason why we switched from batch processing to multitask processing. Waiting on IO and refocusing is such a slow task t
by kuschku 11y ago
The argument you’re making is the same reason why we switched from batch processing to multitask processing.
Waiting on IO and refocusing is such a slow task that time scheduling other CPU-heavy jobs during that time can optimize performance a lot.
- deanCommie 11y agoA perfect metaphor :)
- falcolas 11y agoThe problem with this argument is that computers take very little time to context switch - a couple of milliseconds at most. Most humans take closer to 30 minutes or an hour to do the same type of context switch. As a fellow ADHD'er, I realized some time ago that while multi-tasking, I was just doing multiple things poorly. I'd lose the stack, forget tasks, lose conversations - basically be a waste of space, except for the very rare times where I could write brilliant code due to hyperfocus. When not on medication, I will be forced multitask, but I do so with "tasks" which require differing amounts of concentration - so I can leave one part of my mind stewing on a problem while looking at cat pictures.
- kuschku 11y agoSame here. The discovery that I should only do one CPU-heavy task at a time was very useful. Also, bosses + coworkers prefer if you always seem busy – so, while planning code, take a block of paper, and draw flowcharts, class diagrams, etc – it helps visualize the thoughts (so you keep them even if interrupted), and it makes you seem more effective.