hmm... shame on me today... i went to office at 9:30. supervised the status of my module and component. Then i analysed my offshore delivarable. Then some one called for a team lunch to an indian restaurant. We left at 12:00 PM and then after lunch my developer instinct said it needs some rest. so I left for the day. It is an irresponsible move. I got to compensate tomorrow to overcome my guilty feeling. But i enjoyed the time in evening.

Ok. So todays lesson is:
1) Respect your work. If you know something is going to prevent you doing it, stay away from it.

Technical lesson:
I planned to use the builder pattern for a class which exceeded 3000 lines of code in java. The purpose of the class is to map a big chunk of data from the host system to Object model. The whole mapping is handled by a single class. After reading through the builder pattern yesterday, I guessed my class is an apt candidate for applying builder pattern.

* The Builder Pattern assembles a number of objects to make a new object, based on the data with which it is presented. Frequently, the choice of which way the objects are assembled is achieved using a Factory. It constructs a complex object from simple objects step by step.

My plan is to build all the composite objects by using separate builder objects and finally assemble it using a super builder object. This way, the code is more organised and more maintainable.