Skip to main content

Frozen (2013)

Watched Frozen in cinema today. Really enjoyed it. All evil guys were punished properly this time. I was happy! Though as usual there was a couple of scenario glitches, but in general very positive and interesting story.

The only thing that disappointed - 30 minutes of ads with addition of some irrelevant Disney short cartoon before the movie. 30 fucking minutes! However it's not related to the movie itself.

I have read some reviews and opinions about the movie so far and some of the quite interesting. One of them in particular is that it is the first movie that teaches girls they don't need to be dependent on a male to resolve the problems. Well, this is not very accurate to say the least. Though indeed in the movie girls try to resolve the issues themselves, but it doesn't go very well without extra help no matter whether it comes from a male or a female.
What has truly amazed me was the idea that Disney explicitly portrayed true love in this movie not just as a path to marriage and a long happy life afterwards, which I personally find a bit outdated and even children today don't find it credible, but that love is sacrificing yourself if required for the people you feel close connection with.

Comments

Popular posts from this blog

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