First Beach Cleanup - an ever lasting impact

Thuppuravu is part of life style since the days of Thirunavukarasar and Thirugnanasambandar and they have strongly belived that cleaniness at first that will take to the godlines. Besides the soft teaching on facts, a hard learning is required for everyone to follow by blood. Here the story goes..

Beach Clean up drive campaign with attractive gifts like a T-shirt and a Cap have pushed to take up the drive in early morning hours on a Saturday. As communicated had reached Anna square busstand around 5.30AM and was trying to locate anna square, it was still dark and one showed a camp building close to the sea. Moving closeby, able to hear the sounds of waves dashing the shores of land.

Before work starts, the gifts were distributed and was quite happy to get the first Cap. When the turn comes, organizers said that they have only T-shirt and no Cap. It had left with bit disappointment.  

Wearing T-shirt and gloves, we are jumping into action by 6AM.

Garbages like papers, polythene covers, empty water bottles and straws were collected from in and around the sand. The food vendors also caused the place unhygenic with leftover food remains. 

It was very painsome to pick up dirts. It touched deeply and raised questions in mind, how much pain it causes to the individual who pickup garbages. Why should we need a garabage collector role. Just because some garbage thrower exists, there is a need for a collector. If everyone does their part, there is no need for one is realized. 

The drive was closed by 7.30 am and the sun was at 45 degree East in full action. 

It becomes an unforgettable experience and pushed hard on not to throw anything on streets or in public places. 

This has given more opportunites in places whereever needs cleaning. More avenues like
Temple suroundings were kept as much clean.
River cleaning by pulling out buried carts/tyres/polythene bags etc. 
Park cleaning by removing invasive species 

Community Service has become essential to build a vibrant community. 

Thirumoolar thiruvaduthurai ADHEENAM BOOKS

 

திருமந்திரம் 1726-ல், 

"மானுடர் ஆக்கை வடிவு சிவலிங்கம், மானுடர் ஆக்கை வடிவு சிதம்பரம், மானுடர் ஆக்கை வடிவு சதாசிவம், மானுடர் ஆக்கை வடிவு திருக்கூத்தே" என்று கூறுகிறது. 

இந்த கருத்து மனித உடம்பை வெறும் உடலாகப் பார்க்காமல், இறைவனுடன் ஒரு தொடர்புள்ளதாகக் கருதுகிறது. மனிதர்கள் தங்கள் உடம்பை மதித்து, அதை இறை வழிபாட்டிற்கு பயன்படுத்த வேண்டும் என்பதை வலியுறுத்துகிறது. 

திருமூலர் சமாதி கோவில் உள்ளது.

திருமூலர் திருமந்திரம் விரிவுரை புத்தகமாக கிடைகிறது. 

விற்பனைக்கு நூலகம் ஃபோன்: 9487713042

DiscoverJava

 

DiscoverJava by practice

With basics of any programming, java can be learnt easily. Links:Do look out java beginners training materials from iit website, also foreign universities mit, Stanford etc. Also java-brains by koushik offering java beginners course.

 Practice is important. Please do share your queries and is happy to clarify. Regards

Tell me Don't Ask

Usuage of one of the principle of object oriented programming Tell, dont' ask was narrated with an example.

In MVC architecture, the controller takes the data input from the model object, process the same and re-directs to a view.

Consider a scenario whereby the server has to kill the expiring client sessions. Each of the sesssion object will have the last accessed time. The controller is the one has to kill the expiring client sessions.

In this context, the computational logic used is (current time - last accesssed time >500). This needs to be placed in following places.

Case I: Controller
If the computation logic is placed in the controller, the contoller takes the input (last accessed time) from the session object and applies the computational logic and decides whether the session needs to be killed. If the condition is true, it sets session timeout(kills).

Case II: Model
Computational logic can be placed at the model object. Whenever the controller asks whether the session is alive or not, controller can just take the computed information and then decides whether to kill the object or not.

But in this scenario, there is question of what would be the ideal choice?

Here comes the oops Tell, don't ask principle as a rescue. It suggests not to expect (don't ask) the controller to do the work of computation of business logic, for the determination of whether the session needs to be kept alive or not. In order to acheive this, let the model object do the computation and maintain the status of isAlive. The object maintains both the last acccessed time and also the isToBeAlive status. For the session who has crossed the cutofftime, will still be alive with the isToBeAlive status as false.

In otherwords, session object will be alive until its killed by the controller. Its only the controller has to decide and act (kill) the session object. Now the controller will not ask for the raw data and compute the results. It straight way asks the model object (Tell) for the computed result (isTobeAlive flag)whether object needs to be killed. Based on the result/info from the object, the controller will kill the object.


Conclusion:

Let the model object do the business logic and controller will be free enough to make actions based on the information provided by the model object. Always it would be easier to test the method/business logic by overriding the methods through junits.

Its always encourageous to see your views/perspectives.