| (07.26) | Lady in the Water  |
| (05.21) | Da Vinci Code, The  |
| (05.06) | United 93  |
| (02.05) | King Kong  |
| (01.29) | Syriana |
| (01.24) | Walk the Line |
| (01.05) | Chronicles of Narnia, The: The Lion, the Witch and the Wardrobe  |
| (01.02) | Harry Potter and the Goblet of Fire |
| (12.30) | Jarhead |
| (12.27) | Wallace & Gromit in The Curse of the Were-Rabbit |
| (12.05) | randy: Polar Express, The |
| (12.02) | Geoff: Polar Express, The |
| (07.27) | Jen: Lady in the Water |
| (07.27) | Justin: Lady in the Water |
| (07.12) | Sarah: Da Vinci Code, The |
| (05.25) | Chris: Da Vinci Code, The |
| (05.25) | Acceler8: Da Vinci Code, The |
| (05.21) | Mr Plow: Da Vinci Code, The |
| (05.11) | Sarah: United 93 |
| (05.11) | Bread: United 93 |
Tim Burton can be really frustrating sometimes. There's no doubt that he's one of the most imaginative visual filmmakers out there, and Corpse Bride certainly fits that bill. The stop-motion animation is really incredible, and the art- and character-design are truly unique. What's frustrating is that, despite the wonderful look of the film, the writing and story are basically just 'okay', and the music (which, being something of a musical, takes up a significant portion of the film's running time) isn't very memorable. The music isn't bad, but in light of other recent films like Charlie and the Chocolate Factory or Team America: World Police, it's just not quite up to par.
That's all you have to say about it? Every other review is in depth this was just, well, unacceptable...tisk...tisk...tisk.
Yeah, I know. But I think I'm going to pare my reviews down a bit for a while. I remember when I originally started doing them that they were really short, and that was nice because I could spit them out pretty quickly. They've sort've been expanding in length ever since, however, to the point where it takes a lot longer than I usually want to write.
So, I think I'll be more frequently than I have been lately, but they'll be a bit shorter.
This movie totally kicked ass.
Many many quliaty points there.
Blocking code rwieevs are used at a big online retailer once known for selling books. It was mainly a turf war with massive egos. Changes were nitpicky but mandatory- you might write code in 4 hours but spend 10 days making various teams happy with your decision to use certain variable names, methods, etc.At one time they had a system that sent email when code was checked in. That was essentially a nonblocking code review- and if poeple paid attention to the files coming in, you might get an email for the right reasons: not commenting the code, forgetting a case that would break the code, etc. Eventually that became unweildy- too much mail, people were pressured to work harder, which meant reviewing others’ code became a lower priority.Knowing that email would be sent to interested parties worked well- even if nobody looked at the code, you knew someone else would see it, so you acted like a good citizen.
lntREu rxavvzdalmbo
kTVfQS jqwdelamyokk