Context Switching

For the non-computer geek a quick lesson on computer architecture:  Context switching is a process used to make sure that a single program does not monopolize your computer’s processor.  Each application is given a time slice, if the end of the time slice is reached that application has to release the processor and allow another application to use it.  The “interrupted” application then gets back in line to wait its turn to use the processor again.  (Learn more)

It occurred to me on the drive home this afternoon that my day typically consists on one context switch after another.  I am working along on something when an email arrives that steals my attention.  I then put down what I was working on to take care of the email.  While I am answering that email I get a reminder that I am supposed to be in a meeting.  So, I leave the email half completed and go to the meeting.  It never fails that the meeting runs into lunch so I go from the meeting to lunch.  Upon returning from lunch I start to work on the new things I have to do based on the pre-lunch meeting.  Then the phone rings.  After the call I realize I never finished the email I started before lunch.  By the end of the day I am back to trying to complete the task I started the day with before I go home.

Maybe I am just an uber-geek to think of my life in computer terms but it was interesting none-the-less.  Maybe I will change my name to Shane “Windows XP” Kenny.  In this case I will want rename all the to-dos on my list “svchost” since for some reason this process can ignore the common context switching rules and hog the processor.  Maybe this way I would feel like I am getting something done!