Skip to main content

Movie Review - Sherlock Holmes

Sharadindu Bandyopadhyay would be turning in his grave thinking why Bollywood could not make a movie on Byomkesh Bakshi, inarguably the most famous detective in the country. But Hollywood does not disappoint and makes a grand movie which turns Shelock Holmes from a detective to a hero who kicks, punches, jokes and of course solves mysteries.

Sherlock Holmes is based on the London of 1891. As with movies set in past having mysteries and secrets ingrained in the story, this movie too carries a dark hue. The skies are black, so are the streets. The only thing which shines throughout the movie is the sheer brilliance of acting of Robert Downey Jr., playing Sherlock Holmes. He is very well supported by Jude Law (playing Dr. Watson) with much "bromance" between them leading to speculations whether Sherlock Holmes is gay!

If you are a fan of mysteries, you will be disappointed by the story. You can almost guess how things would unfold in the movie. But what sets the movie apart is the way of story-telling. The scenes which impressed me the most are in which Sherlock Holmes plans every move in a fight and then executes it flawlessly! Or the one in which he guesses correctly the entire past life of a person just by looking at him!

There is not one dull moment in the movie. The entire film is laced with witty jokes which keep you hooked. The way Sherlock Holmes experiments on his poor dog is hilarious. The movie is full of masala quotient as shown in the impressive way Sherlock and Watson dodge through a series of blasts.

Don't go to this movie for a dose of reality because the explanation that Sherlock gives for the events in the movie go right above your head but hey, that's not what you came to theater for! Just go and watch this movie for two hours of complete entertainment.

Comments

Popular posts from this blog

Integrating React with SonarQube using Azure DevOps Pipelines

In the world of automation, code quality is of paramount importance. SonarQube and Azure DevOps are two tools which solve this problem in a continuous and automated way. They play well for a majority of languages and frameworks. However, to make the integration work for React applications still remains a challenge. In this post we will explore how we can integrate a React application to SonarQube using Azure DevOps pipelines to continuously build and assess code quality. Creating the React Application Let's start at the beginning. We will use npx to create a Typescript based React app. Why Typescript? I find it easier to work and more maintainable owing to its strongly-typed behavior. You can very well follow this guide for jsx based applications too. We will use the fantastic Create-React-App (CRA) tool to create a React application called ' sonar-azuredevops-app '. > npx create-react-app sonar-azuredevops-app --template typescript Once the project creation is done, we

Centralized Configuration for .NET Core using Azure Cosmos DB and Narad

We are living in a micro services world. All these services are generally hosted in Docker container which are ephemeral. Moreover these service need to start themselves up, talk to each other, etc. All this needs configuration and there are many commercially available configuration providers like Spring Cloud Config Server, Consul etc. These are excellent tools which provide a lot more functionality than just storing configuration data. However all these have a weakness - they have a single point of failure - their storage mechanism be it a file system, database etc. There are ways to work around those but if you want a really simple place to store configuration values and at the same time make it highly available, with guaranteed global availability and millisecond reads, what can be a better tool than Azure Cosmos DB! So I set forth on this journey for ASP.NET Core projects to talk to Cosmos DB to retrieve their configuration data. For inspiration I looked at Steeltoe Con

Add Git Commit Hash and Build Number to a Static React Website using Azure DevOps

While working on a React based static website recently, there was a need to see exactly what was deployed in the Dev/Test environments to reduce confusion amongst teams. I wanted to show something like this: A quick look at the site's footer should show the Git Commit Hash and Build Number which was deployed and click through to actual commits and build results. Let's see how we achieved this using Azure DevOps. Git Commit Hash Azure DevOps exposes a variable called  $(Build.SourceVersion) which contains the hash of the commit. So I defined a variable in the Build Pipeline using it. Build Id and Build Number Azure DevOps also exposes two release time variables  $(Build.BuildId) and  $(Build.BuildNumber) which can be used to define custom variables in the pipeline. So we have a total of 3 variables defined: Next we use these variables in our React App. I created 3 global variables in index.html and assigned a token value to them. < script   type = "text/JavaScript&quo