Daily Archives: 1/3/2006

I feel useful today…

There is an old joke about what men are good for: the punch line reads something like killing spiders, barbecue and oil changes.   I’d like to pretend that I’m a handy person, but when the truth comes right down to it, I pretty much consider myself a software guy, not a hardware guy.   Still, I think the software mentality teaches you to think about debugging in a more general sense, and occasionally it pays off.

Like today.  I mentioned briefly that my right windshield wiper had failed during my trip to Truckee over New Years.   While occasionally the wiper would twitch, it wouldn’t move very regularly, but would occasionally catch and flop all the way over to the left side, and then get in the way of the left wiper blade.   I was going to take it into a garage to have them charge me $50, but as I was waiting for my wife to get showered, I decided to give it a couple of minutes of my own attention.

I felt that it must be something minor, rather than a motor failure.  Had the motor failed, it would have been likely been catastrophic: the wiper blade wouldn’t twitch at all.  I felt it must have been in some part of the linkage that connects the wiper motor.  I had no idea what that linkage might be, having never really examined this stuff before, but it was a working hypothesis.

I marched out to the car, undid the rubber bands that Carmen had set up to keep the blades from flopping around during our trip home (while still moving I might add, a splendid McGyver moment for her) and stared at it for a moment.  I picked up the blade and tried to move it along its normal motion.  It moved easily, freely.   I then did the same to the one that worked.   It didn’t move at all.  Ahah!  I next popped the small plastic cap off at the base of the wiper arm, revealing a 5/8 inch nut.  It was finger loose.  Ahah!   Back to find a 5/8 socket.   A simple bit of tightening, and it worked.  For a minute.   Then it was loose again.   This time I really tightened it.  And voila!  It appears to function.

Saved myself a trip to the garage and some annoyingly large amount of money for a simple bolt tightening.

I feel useful today.

King Kong

Last night was the first opportunity that Carmen and I felt we could spare the three hours necessary to view Peter Jackson’s latest blockbuster film, his remake of the classic 1933 film King Kong.    It’s a colossal film, much in the same visual style of Jackson’s earlier Lord of the Rings trilogy, with many big, sweeping vistas, extended action sequences and a fair amount of just just showing off.

It’s a good film, mind you, but it is just a bit much at times.   It’s not actually boring, but you can see that there are entire scenes, entire plotlines, entire subtexts that really aren’t very central to the story.  We’d expect that in Lord of the Rings, where the plotlines and subtexts are really part of the joy of the story, but they aren’t really necessary in King Kong, and actually seem a bit like showboating: “I’m Peter Jackson, and I’m adding an hour of footage just because I’m Peter Jackson“.

By way of example, consider the roles of Hayes and Jimmy (played by actors Evan Parke and Jamie Bell).  They are crew members on the boat, and Jackson spends a fair amount of time creating a level of backstory for these characters, yet in the end, there is no real payoff: the role that the characters play is entirely incidental to even the secondary plotlines of the film.

Then, consider the extended “brontosaurus and raptor stampede”.  The only thing that really accomplishes is we get to see a lot of extras (in the Star Trek universe, all these guys would have red shirts) get trampled by CG dinosaurs, while the major characters somehow karate kick their way to safety.

The spider pit is a bit over the top as well, and again only serves to thin the heard of red shirts.   If any of these scenes were incompetently done, they’d really detract from the movie, but even though they are well done, I think as a whole the movie feels a bit self-concious and over the top.

I also thought that there were some continuity problems: the natives initially are protrayed as brutal savages, and yet somehow after the initial encounter, they are nowhere to be seen.   Other, more minor discountinuities seemed to jar me at 20 minute intervals.

Still, overall I’d rank it about a B+.   It delivers a lot of what you expect, even if it is a bit slow out of the gate, it keeps you interested and excited.  Naomi Watts does a great job as Ann Darrow, and while I think that Jack Black was reaching a bit beyond his grasp, he did a credible job as movie producer Carl Denham.  Adrien Brody takes what is essentially a pretty minor role as Jack Driscoll, Denham’s screenwriter, but looks great on screen, and gives a good performance with minor motivation.

It’s kind of gruesome in spots, you might wish to consider carefully whether to take younger kids.