Sunday, April 13, 2008

BLOODY Rambo



When First Blood released in 1982 it was a huge hit and it sparked off two sequels in the next 6 years. The second part was forgettable with an improbable gun totting, pencil thin heroine and part 3 was pure torture. In retrospect its even ludicrous considering that Rambo liberates Afghan Mujaheddin freedom fighters from the clutches of the evil Soviets.

Twenty years after the last sequel comes part 4. Stallone must have been hoping to rejuvenate his waning career. Or may be he is trying to make a lasting impression, his final contribution to cinema. Let's hope its the latter. The first few minutes were the usual. Rambo is leading a retired life in Thailand where he catches cobras for a living. He also drives a boat. The unwilling hero is urged to help a charity mission and after much pleading he reluctantly agrees. I think that pleading scene is the only one in the movie in which a dialogue lasted more than two sentences. The whole time I kept reminiscing the wonderful Hot Shots: Part Deux, which is an excellent spoof of the Rambo movies.

The charity team is caught by the evil Burmese army, they were stupid enough to walk into a war zone so obviously they got caught. If there was a message in the movie it would be: live for nothing or kill everything. Like Rambo tells the terrified missionary lady you cannot change what is. Now its up to Rambo to rescue them. He does that by killing what seems to be the entire Burmese army. There were supposed to be only 100 hundred soldiers in the camp but there were definitely many times that number of dead bodies.

You might ask how this makes it a bad movie. Each killing scene is shot so realistically that after the first few you either go numb or run out of the movie hall or puke. Realistic gore is sometimes required to impress upon the audience the gravity of the scene like in the first 15 minutes of Saving Private Ryan. But when the whole movie is about showing the different ways in which people can be killed, about how blood and entrails can scatter and about how big guns can rip off heads and arms and cut bodies into pieces, it becomes deplorable. In fact violence is a lead character in the movie and it is pictured so well and with such commendable depth that by the end you are accustomed to it and accept it.

There were many people who told me that the movie was good because it was very realistic. Realistic? Really?? In which reality will any one person see hundreds of bodies torn apart in the span of an hour. There are so many shots after shots of shocking, intolerable violence that it grabs your attention and by the end of the ordeal you appreciate the movie forgetting the reason you found it interesting is very base. All the creativity that went into making of this gorefest was intended to shock the audience with socially unacceptable imagery and that makes it similar to porn.

That said there are many other movies with similar or even more morbid violence. The newly released Doomsday has a few scenes that challenge our tolerance limits. The cannibalistic punks of future roast a soldier alive before they cut him to pieces and eat him. But the plot of that tasteless movie is itself asinine and beyond reproach.

Thursday, April 3, 2008

Tale of interviews: Interview Experiences Part Deux

I had two more interviews since the first part of this post. The first one was with NVIDIA. The interview call lasted all of 3 minutes and 34 seconds. The interviewer, a senior executive in the company, called me 11 minutes late. After some preliminaries he asked me what my areas of interest were - whether I preferred mobile or graphics team. I had to pick one and I picked mobile.

Then he said "AHA! But I am from the graphics team. Good bye. Take care." Well it was something like that. But he did mention that he would forward my resume to the other team and now I have got another interview call from the company. I hope it too wouldn't be an anticlimax with the interviewer referring me to yet another team.

And now about the second interview. It seems my performance in the Google interview wasn't that bad after all. I had my second interview round yesterday. Please note that there are usually only two rounds of interviews in Google and if I get through this one I would hit the jackpot. But of course I didn't do it well. Obviously that's the reason why I am posting this. Remember the Shakespearean verse, "All ye, pity not thy fate but blog thy misery till thee plague all ye mates". OK I will cut the non-sense and go right into the questions:

1) Write code to generate spam messages. You are given a passage. Jumble the words from the passage and make a message of arbitrary size. A simple example can make it clear. For example the passage can be "Jumble the words from the passage and make a message of arbitrary size. A simple example can make it clear. For example the passage can be". The generated message should contain words from the passage with each word being followed only by one of the words that follow it in the original passage, like in "passage can make a simple example the words from the passage".
2) Give test cases for this code.
3) What is the complexity of the code?
4) Do you know oops? Good. What is an interface?
5) When you type in an address in your browser what are the steps that results in the web page getting displayed?
 
I am not a cruel person and so won't make you read through my answers. I mean you just might laugh your guts out.

[Update 04/07/2008 : I got a reject from Google. On the bright side now I know that the universe is back to normal]