Tuesday, December 13, 2005 

interesting or uninteresting?

Blogging from Neuchatel, Switzerland doesn't feel any different. Hahahahaaaa, I mean should it?


Being in this new job does bring about certain challenges which I never thought would bother me. There are mostly about working with new people, being conscious about team and people dynamics and other stuff mostly concerning people matters. This brings me to the topic of what makes interesting work, and work interesting to me.

I have no doubt that technical challenges is the main factor for making any work interesting for me. But I also know for a fact that I'm also very much of a people person too. Let me rephrase: I am someone who is always concerned about how best to put forth my comments and ideas so that I'm understood and not misunderstood, and simultaneously being as sensitive as I can to how others are feeling about me, the situation and such. Such people-aspects of work, and life of course, has been an on-going effort and thus sometimes is relegated to the sub-conscious.

Thus, it is interesting to me that I'm putting in more effort to take a conscious note of the people dynamics around me than being worried about work challenges, or the lack of it.


Logically, blogging in an entirely different location should not matter that much. But again, it does feel good to being able to look out of the window and see a snow covered field just outside. A difference nonetheless.

Saturday, November 26, 2005 

a milestone

Things come, things go. Everything.
Partings. Reunions. Reflections.


It's been 4 years since I left school. I'm now leaving my first job for another. I've always talked about changing job due to the high stress level, lowly pay, lack of appreciation etc etc etc... the list goes on. But there must be something more to the complaints I have about the job that kept me going and going for these 4 years.

I don't want to go around pretending that everything is rosy and nice. If there'll be something that I felt should have been better, I'd like to make it known and heard. It also helps to relieve the bottled up stress. Friends who know me will understand that; I don't work well under stress.

Several have asked me if I have any plans or targets for the coming years. Frankly, I haven't been thinking too much about it. Given how I am, I know I will make the best of each and every situation to ensure that it helps me grow in the general direction that I wanted. And I think that is enough to see me through for at least a few more months.

Thursday, November 17, 2005 

think different

http://www.sellsbrothers.com/news/showTopic.aspx?ixTopic=1906

Friday, November 11, 2005 

leadership

There was this discussion at work about what makes a good leader and what is good leadership recently. My first thought about this was this is an every-now-and-then discussion topic that surfaces, hundreds if not thousands of books published about it and uncountable articles written. I posted something similar like this in a blog shared among colleagues; this is improved upon the original.

If you ask me for my 2 cents worth, this is what I feel a great leader should be:

He may not be your friend in good times but is your best friend in bad times.
He is whom you will seek advice from when lost; and whom you will follow when instructed, and whom will inspire you to go further than instructed.
A great leader is not really your friend, but can be your friend, and is more than your friend: He is your leader.

What do you think?

Saturday, October 29, 2005 

never mind, as long as it works

I'm sure many of us would have encountered scenarios resulting in such a statement as above. A colleague was trying to figure out why his nested SQL select didn't work. Frankly, I'm also as clueless as he is. I suggested using table joins instead. It worked. Doesn't matter why it didn't work with nested select, as long as we've gotten something that worked. It didn't matter because the SQL statement is only for data analysis.

A more senior colleague was commenting that designers and developers tend to choose the easier way out when implementing new functionalities for the website. The mindset is as long as it eventually gets the new functionality working, who cares if one have to re-create a similar UI feature all over again in different pages. He is trying to have such a mindset changed, but admits that it's not going to be easy; I concur.


Actually, it doesn't matter in which context the "never mind, as long as it works" mindset appears in, it is a dangerous mindset. Dangerous to maintaining the quality of work one delivers. And it is something everyone is guilty of, myself inclusive.

Of course there are scenarios like the former, where lapsing into such laziness would not cause any further "harm". But situations like that latter involves a much more complex problem domain. In such cases, if the improvement towards the better method is certainly desireable and to be pursued, the question to ask is how much would one tolerate more bugs and design mistakes than if one were to stick to the current one-for-one implementation technique?