Sunday, May 30, 2004

New Movie(Tamil)

Aayutha Eluththu (Tamil) rel: May-2004

Stars: Madhavan,Meera Jasmine, Surya, Siddharth,Trisha

Music : A.R. Rahman ; Lyrics : Vairamuthu ; Direction : Mani Ratnam.

I saw this movie twice and as you could guess this is another Mani ratnam HIT. I enjoyed every moment of this movie , especially the editing and how the story is organized. Mani has done wonderful job. Typical "Mani Style" scenes such as night light shootings, his own style of dialogs with short but strong sentences are all over the movie.

The movie is about 3 youngster's life styles and how they come to a interfere with each others by an accident on one of the main bridges in Chennai. Every artist in the movie have performed well. Special note should be given to Madhavan for taking up an anti-hero role. As a typical chennai gangster his acting is fantastic. Meera Jasmine looks exactly like the "Azhaki" movie Nandita Das. wow what a combination. Surya , Siddharth and Trisha have doen their roles nicely too.

For all ARR music is another addition to you hit list. Even thougth there has been some recent critiques about ARR's music quality with his master , mentor Mani .. ARR has done a wonderful job in this movie. The music selection for the 3 heros and the theme music for their scenes on the movie are awesome. I always liked the hummings that appear in his movies and AE has some too. Special ones are the "Jeevane.." one that plays behind when madhavan appears and the humming in between the 'saranam' and 'pallavi' in the "hey good bye nanba...." song. The mixing of fast and slow beats in all the songs proves to the ARR critiques why he is such a star.

screenplay, choreography and arts all gives an extra kick to movie. The sync sound technique is a plus with DTS quality sound.

overall I would give 4/5 rating for this movie.

No.. this is not because I am a Mani ratnam fan :o)

Here is the link for the movie info site

Why a polynomial algorithm is better than exponential algorithm?

a polynomial algorithm is an algorithm if the complexity function of this algorithm has a rate of growth O(n^k). otherwise it's an exponential algorithm. From a basic mathematical point of view we know why a polynomial algorithm is prefered from an exponential one is pretty simple. When the size of the problem, that is, it's input size grows larger the running time of the exponential algorithm grows way too faster than the polynomial algorithm. This is a very basic observation. But there is also another important property in this comparison that does not get noticed very often. That is when the machine power increases for some reason the limit of the size of the problem that the exponential algorithm can solve increases by a smaller factor (ex: PrevSize+10) where as the exponential algorithm's limit of the size of the problem grows by multiple factors (ex: PrevSize x 10 ). This makes a huge impact and deserves mentioning in this fast growing hardware world.

Thursday, May 27, 2004

Lost with Use cases ?!@#$%

Use cases are a wonderful idea that has been vastly overcomplicated. Over and over again I have seen teams sitting and spinning in their attempts to write use cass. Typically they thrash on issues of form rather than substance. They argue and debate over preconditions, postconditions, actors, secondary actors, and a bevy of other things that just don't matter. The real trick to use cases is to keep them simple. Don't worry about use case forms, just write them on blank paper, or on a blank page in a simple word processor, or on blank index cards. Don't worry about filling in all the details. Details aren't important until much later. Don't worry about capturing all the use cases; that's an impossible task. The one thing to remember about use cases is: tomorrow they are going to change. No matter how diligently you capture them, no matter how fastidiously you record the details, no matter how thoroughly you think them through, no matter how much effort you apply to exploring and analyzing the requirements, tomorrow they are going to change. If something is going to change tomorrow, you don't really need to capture its details today. Indeed, you want to postpone the capture of the details until the very last possible moment. Think of use cases as just in time requirements.

This blog is an excerpt from Robert.C.Martin's latest book:UML for Java Programmers, Robert C. Martin, Prentice Hall, 2003.