Design Patterns

I was browsing at Kinokuniya the other day on the programming section. Interestingly, I found some book regarding design pattern. Well, I have learned about design for IT in my college years, (Usually about creating forms or database design.) but this topic really catches my eyes. By the way, those books on the shelves at Kino are tightly wrapped and I was lazy to take the book to the counter for unwrap. Therefore, I just read the cover for some brief information and try to remember the book title.

Back at home, I did some research on the internet on what I have discovered. To my surprise, all this information was available back in 1995. Till today, none of these terminology was apply in my working years.

Perhaps I can say that, these design patterns was not that crucial or important enough to practice in real world. So, why do I need read all these stuff and talk about it here? The big advantage of design pattern is that it reduce software maintenance and adapt to change. (In IT world, a software application has to adapt to change else it will die or outdated. This also mean out of job for programmers. :D) Well, I have seen company putting in a lot of investment just to maintain an application and it doesn't adapt to change either. (Maybe that's how I and everybody else could get a job and put the food on the table. I would disagree with this because that means we lose a competitive edge to our competitor due a lot effort was spend in maintaining the software instead of moving forward for new functionality, scalability, usability and improve performance. Competition not in term just for local but applies to global competition as well)

So, what so special about it? Well, for people who interested in the Object-Oriented Programming, here a sample chapter of Decorator Pattern and it was described in Java programming. I believe this also can be done on dot Net technology since it is a OOP also.

If you have started talking in OOP language, that's great. Perhaps you can try out talking in Pattern language, trust me, that's even exciting.

Leaving the comfort zone

It’s been a week I have landed my job on my new company. I remember the first day I started my training, my mood wasn’t felt quite right. I believe that was due to the unfamiliar environment, work and colleagues. From an ERP software environment to the financial credit card system seems to be a lot of changes for me. In addition to that, my mind is still trying to fall back the daily behavior in my previous job and it took me couple of days to adjust my mind to feel a bit of comfort in my current office.

Nevertheless, the external environment still remains the same. My current job location wasn’t too far away from my previous job and I still able to enjoy my lunch hour as usual before. From time to time, I still able meet up with some ex-colleague (different department) on lunch hour or at the LRT station after working hours. Funny thing was, they didn’t know I have left (mind you that I’m just only a small potatoes) and asked me how come I’m wearing casual wear to work. Am I on MC they asked. After clearing up the confusion, a sense of embarrassment runs thru my mind. Well, they have to know it eventually and by the way, we have plenty of chances to meet up at the LRT station.

So, leaving comfort zone was just only the first step and there are many more steps waiting to be explored. Whether those steps are taking to me to higher or lower ground, in my opinion, I hope those steps would take me to more fulfillment and happier experience.