Django Unchained

Django Unchained - Review

I have been eager to watch this movie since seeing a trailer a while ago. It was intriguing and I thought the premiere shouldn't be missed.
My curiosity and aspiration was also fueled by the announcement that Tarantino himself was planning to visit the premiere in Sydney.

It was a bit of disappointment to get the announcement just before the session that Quentin was not coming, but it didn't really matter, because the movie was amazing, incredibly fun and thrilling.

Though it's pretty lengthy (2:45) I haven't got bored at all. After a couple of beers I looked for some quiet scene to go to the bathroom and there is such a scene in the movie. Possibly right in the middle, when many people in the cinema decided to pay a very quick visit to the toilet.

Almost entire audience laughed and giggled following the story line on the screen through the movie.
Very saturated, soaked in soulful music, technically perfect, flawlessly played by the great actors - this movie worth watching not just once.

One of my fellows said "Violence is beautiful" during our discussion the next day about it.

As per information from Box Office Mojo it has already earned $189,081,971 as of now.

Other links:
Movie Web site
IMDB
Wikipaedia
Rotten Tomatoes

Comments

Wine - 2011 Brown Brothers Crouchen Riesling

Very nice wine with fruity taste - peach and pear: Consumed with Hungarian salami. Tasting notes .

Scrum - Team Culture and Wall Manifesto

In the Scrum framework one of the key components is the wall and daily stand-up. In some organisations I worked with the whole concept of the wall is not accepted by many developers, because of the stand-up necessity and "time waste". Very often all that methodology is used for the sake of methodology and not to achieve what we actually do - adding or creating value to our customer (usually called "The Business"). I can understand frustration that is caused by the wall and stand-up process. From the software developer perspective it is really a waste of time for the following reasons: 1. In 95% of cases developers are head down working like hell delivering valuable outcomes that they are accountable for. Extra effort to go to the wall, staying there for 15-30 minutes and listening or not listening to what others were doing yesterday and will be doing tomorrow is annoying for them; 2. The mere fact of having to do something mandatory to do that looks like

Mastering The Multitasking

There is usually two distinct perspectives on multi-tasking: 1. Multitasking is counterproductive. We get distracted by multiple tasks that all get our way and fight for our scarce attention, time and resources. This leads to a common fallacy that if you do multiple activities “at a time” you are not doing good work in any of those. 2. Multitasking is a way of getting many things done in a short period of time or in a long run. Indeed it can be either a disaster or a great helper depending on how it is used and practiced. Most recent research shows that we don’t do multiple tasks purely in parallel or simultaneously. That means we don’t purely multi-task, but switch between tasks and execute them one at a time, but by spending very small timeframes on each task. A good example from the history is a story about Julius Caesar capabilities in that area. Plutarch writes, “Caesar disciplined himself so far as to be able to dictate letters from on horseback, and to give directi

Travels etc.

Search This Blog