Skip to main content

Work done with an immature mind(Kidnap review)

The very first question that came to my mind after watching this movie was 'What did the director want to convey with the story?'.
It seemed that our director had not put enough efforts to make the abducted girl feel that she had been kidnapped! Our villain(khal-nayak), in fact has to give her the bad news - 'Maine tumhe kidnap kya hai'? What a poor guy! And when the billionaire papa-the-great came to the rescue of his daughter, he forgot all the law & order. He was thrashing traffic, robbing money, doing everything to turn himself to a full-fledged criminal! I wonder nowhere in the movie anything was shown about the police activity against this criminal. And how a poor boy(who stays in an orphanage) came to learn driving skills at such a little age? He drove a Merc to get his injured pal to the hospital. Another thing was that the director had not given importance to the details. It could be easily noticed if the two persons who played the villains were compared. It was told that our villain had been in the jail for 3 years. Now, how a 12-13 years aged innocent could turn himself into a 23-24 years aged kidnapper in just 3 years of time? Only a miracle could do this! One more funny part was when the villian said that he learnt all computer related stuffs during his stay in the jail. 'Jail mein sirf tumhara dimaag azaad hai'. Something like that he proclaimed. Ok, I understand that you can use your brain to the fullest, but can you name me the jail which provides such facilities like computers to its inmates? The dialog delivery of Imran Khan was poor, Sanjay Dutt delivered a good performance while his better half in the movie Vidya Malvade, was sometimes very weak in her performance and the same about their daughter in the movie, Minissha Lamba seemed ok.
To conclude this review, this movie is a work of immature mind with the sole intention to pull youths by showing water-clad Minissha's curves & tattooed body of Imran Khan.

Comments

Post a Comment

Popular posts from this blog

Working in India

The day I started working in SRA India(Indian arm of Japan's Software Research Associates, Inc ), I never thought that I world become an onsite team member in just one and half years. Because, the branch was very small & it was very illogical for a novice like me to think of an onsite tour that time. But the fact was that they would make you do your work in almost Japanese style. The very first day I started coding in SRA India, I was told that the Japanese were simply put - perfectionists. This simple word had a very large inner meaning. The code that you wrote should be totally bug free, robust, modifiable without introducing regression etc. The first project I was assigned to, it took a hell lot days to prepare only the detailed design(Java Doc) for a very tiny function, every molecular level detail was described on that. But somehow I made myself adjusted to such work environment. My performance was good in my batch. And in one day, one of my managers told me of an onsite a...
Post a Comment
Read more

Java collection series - miscellaneous

Java Vector is a legacy class. And it is significantly faster in comparison to a list obtained through Collections.synchronizedList(). Vector has loads of legacy operations and hence the manipulations in Vector needs to be done through the List interface, otherwise you won't be able to replace the implementation at a later time. Arrays.asList() is better choice if the list is of fixed size and any kind of size mutation of the collection results in UnsupportedOperationException. The underlying array is updated whenever the list is updated (or vice-versa), but the array reference isn't retained. Collections.nCopies() is another convenient mini-implementation which can be useful in two ways - initialize a newly created list with n null values (need not be only null values) -  new ArrayList (Collections.nCopies(1000, (Type)null)  grow an existing list -  lovablePets.addAll(Collections.nCopies(69, "fruit bat")) Collections.singleton()/Collectio...
Post a Comment
Read more

DB transaction ACID properties

DB transaction is a combination of different operations. If not performed in a proper manner, different transactions working on the same data at the same time may leave the data in corrupted state, effecting the application. In this article, I am going to illustrate DB transaction ACID properties through an example of money transfer application between two different accounts A and B. To begin with, lets suppose that accounts A and B both have initial balance of $100. ACID stands for Atomicity , Consistency , Isolation and Durability . Let's try to understand these one by one. Atomicity : This is the property that mandates that if a transaction is started, either all the operations which are part of the transaction need to be completed by end of the transaction completion as a single unit of work or none of the operations needs to be completed. It is maintained by transaction management component. If a debit of $10 is made from account A, then the corresponding credit of $10 al...
Post a Comment
Read more