Is it too early to plan for vacation... in December?

Since it's been all work so far this year (see previous post), I am really looking forward to a nice, long, uninterrupted, disconnected (from work that is) vacation. I don't think i can skip going back home (HK) - after all, that is where i do my main shopping, but perhaps I will venture out a bit this year and pack a 3-4 day trip to some other places. I'll see how that go.

On the other hand, my sabbatical most likely will not happen this year. For those who don't know, my company offers a 4-weeks sabbatical leave for every 5-years of service (Sometimes, i can't imagine having worked here, the same company, for 5+ years already. Many college/high-schools friends have switched jobs, even multiple times. In certain sense, I think I'm quite lucky that I found a company that matched quite well with me. Oh, back to sabbatical). They would also pay for airfare (include a companion) and up to 20-days (or 21... forgot the exact number) of lodging cost (i think it's 150/day). England is a front-runner for me at the moment, but not 100% sure yet.

I could also break the 4-wk into two 2-wk trips (taken 18-months apart). So that's another question i have to think about. Should i take it all at once, or two mini-trips instead? Um...

Finally another blog entry in 2+ months

Well, blogging definitely took a back seat so far this year. This is like, the 3rd/4th post of the year.

First off, let's blog about work - since the work/lift balance scale is heaviliy tilted toward the work side. Things have been extremely busy in the previous months. Endless requests + Limited resources = Lots of OTs. Hopefully as this development cycles in wrapping up (still got couple more issues to fix), and new ones won't start until mid-summer/fall (please, no "surprise" in between), things should start to get better (finger-crossed).

Another exciting news from work is having a new developer on the team. For a loooooong time, I've been the only full-time developer on my product (and i do claim the title of THE XXXXXX developer in the company... hahaha). With the re-org late last year, my team had to give up the other half-time developer, but luckily got a full-time in exchange (can't imagine developing on my own for this release - well, actually I could, but i don't want to think about it). That brought the number up to 2. Still means I had to scramble for resources for each of our projects - which always causes headaches and frustrations.

On May 4th, another developer joined our team. I think the whole was pretty excited. As for me, not having to worry about finding additional resources is always a plus (well, my TL actually should be happier - since she wouldn't have to hear me complaining... XD). I could definitely see projects flow a lot smoother and quicker in the next cycle. Might be a headache for QA; but for now R&D is happy. :D