welcome 2009! starting out, somewhat similar to 2008...

well, 2008 waited till the oft-absent date of february 29th.  2009 didn't have to wait at all.  my contract with my employer was axed at the end of the calendar year 2008 and after a week of consulting and providing knowledge handoff, i'm officially unemployed again.

i was a victim of an across the board termination of all IT contracts, coming from "up up above".  the result was a nondiscriminatory wiping of jobs.  some were expendible.  others were not.  my boss did pretty much all he could to keep me around, but the economy took a nose dive starting in september and my employer was, let's just say, not exactly immune to market conditions.

and not to blow my own horn, but i'm valuable to them.  when you write the backend of the app that was created from ground up -- designed the database schema, created the object model, and wrote all associating data and web services exposing the model -- you possess a heavy amount of what's called "domain knowledge".  normally and in general, domain knowledge translates to job security.  not so much in my professional experience over the past 12 months.

alas, the tides of life.  if you haven't ascertained by now, i'm relatively unconcerned about my current employment status.  sure the economy sucks, but i've got a lot going for me.  i have an excellent early track record with glowing references to use, my undergrad work was rock solid and i'm currently persuing a master's degree in software engineering at one of the top programs in the nation.  (shameless plug)  plus, i have been putting aside money pretty aggressively this past year, albeit for tuition and a new vehicle (go little '91 honda accord!  go as long as you can, baby!!), but enough to easily keep afloat for a month or two with little overall dent to my financial situation.  (never underestimate the value of being a bachelor and living with a roommate.  i can reduce my expenditures to "survival level" pretty easily.)

school starts in a week and a half.  thank whoeverShouldBeThanked for the 5 week winter break from school.  i feel almost fully recharged and ready to attack a new semester.  i'm looking forward to my classes as well and that never hurts.  in continuation of my apparent "never took networking as an undergrad so lets take an assload of it as a grad" trend, i'm taking a class called "communication networks" which, for all i can tell, will be a semester studying instant messaging algorithms.  (i kid?)

the other class i'm particularly interested in: formal methods in distributed programming.  sex-ay.  the textbook is entitled "concurrent programming".  in december, i received a just-released tech book i had pre-ordered for a good six months entitled "concurrent programming in windows".  in my personal opinion, concurrency and distributed programming, manifested in multi-core desktop chips, cloud computing, or both, is where you're going to see massive growth in the commercial software development.  i'm eager to get as much formal chops as i can this next semester and use it to springboard myself into a deeper commercial understanding and skillset for concurrency and distributed programming.

*deep breath*

now, to update my damned resume...