Skip to main content

Toy Story 3


It is a great movie. (http://www.imdb.com/title/tt0435761).

Especially love the moments with "The orphans!" at the beginning, and when Mr Potato Head stick his body parts to the wrap and then the pigeon sat near.

But there are some moments that are not smooth. The main fail is too light punishment for scoundrel Lotso after all he did to the toys.
So if the audience is not educated or doesn't have enough personal experience, they might think that if you behave bad to others, betray them using their kindness and providing some extremely inadequate excuse ditch them in danger - nothing is going to happen to you as a result!  
The fair ending of Lotso in the movie would be him to travel all the way to the fire. Because in the situation from the movie, there is no need to wait for good deeds from this sort of creatures or to wait until they do something bad to you.


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