It’s 3.00 AM in the morning. I can’t sleep. I can’t eat. I can’t stop working. It’s ‘early’ in the morning and I have a paper in the coming few hours. Big risk? Yes.
I found myself, yet again, doing something that I had been doing (quite successfully) over the past few months. I had been working day-in and day-out not knowing when that I would finally come to that light at the end of that proverbial tunnel.
I had been multitasking, not the kind of multitasking that managers learn how to do, but rather, in a fashion similar to that of my laptop’s CPU. Fascinating? Confusing? That’s me spewing out all that computer-related jargon. Don’t fret, you’ll get used to it.
I do multitasking ‘round robin style’. My task description is as follows:
for (int i=0; i < (amount of work to be done); i++)
10 minutes: Facebooking
15 minutes: Thesis correction
5 minutes: Checking the news
3 minutes: Googling
} //process iterates (amount of work to be done) number of times.
Total time per cycle: 35 minutes.
Work efficiency: 15/35 minutes = 42.86%
Works well at times no?
When the workload grows, I even work in sync with my computer. Here’s how I do it:
1. Starts Microsoft Word (4 seconds to load)
2. While waiting for Word to load (during the 4 seconds), I start the Google Chrome browser. (Takes 1.5 seconds to load)
3. Once the browser has loaded, Word still has 2.5 seconds more to load into memory.
4. Remainder 2.5 seconds is used to load Facebook, takes 5 seconds to load.
Total time taken to do tasks 1 to 4: 6.5 seconds.
Not bad at all…that’s three CPU cores at work (including my head).