Month: April 2009

  • Time is Like Modern Art – Primeval – Series 3, Episode 2 – Review (spoilers)

    If mythological creatures are manifestations of anomalies, are haunted houses, also?

    Synopsis

    14 years ago a magnificent house stands empty. Teenagers break in, but they don’t get out.

    Back in the present, Cutter has used the data from Dr. Page’s research to build a new model of the anomalies, with it, he is able to make a prediction of a location for an anomaly. Jenny, Conner and Abby go to investigate. The site is the same house, still abandoned and now in disrepair. Something is still in the house, something fast and able to camouflage itself at will.

    Adding to the mystery, a hard-nosed copper tries to keep the ARC team from researching the house.

    Meanwhile, Helen steals Dr. Page’s access pass to the ARC and sends one of her clone troopers to steal Cutter’s clothes. The intruder is detected and killed. Cutter begins to get a glimmer when he recognizes the dead man as the same guy who was killed in the Silurian desert in series 2. And why does he want Cutter’s clothes?

    Abby discovers a little girl who is feeding the creature back at the house. The girl does it so the creature won’t eat the neighborhood pets – or people.

    A showdown happens at the house, just as an anomaly opens and, at first, the creature finally goes home – then it decides to come back and kill people, so the cop pops a few caps in its ass.

    Analysis

    There’s a lot going on in this episode, little of it good.

    But first, let’s digress for a few moments and discuss brilliance. Brilliance is tough for some writers – perhaps most writers – because, by definition, brilliant people are difficult to follow for the average person. It follows that, if the writer cannot think brilliantly, it would be difficult to put thoughts in the head of a brilliant character. Difficult, but not impossible. Arthur Conan Doyle’s Sherlock Holmes is a classic example. Holmes’ brilliance is apparent in his almost magical ability to discern things others cannot see, but ultimately, they are explained as reasonable and understandable manifestations of human capabilities, used more effectively.

    Sadly, Dr. Cutter’s character isn’t done this justice. The writer’s have confused preternatural clarity of vision with “anything unexplained thing Cutter says must be brilliant because it doesn’t make sense.”

    Case and point, his new 3D model of the anomalies is just idiotic. What does it represent? Are we really supposed to believe that bending a few plastic rods around the room yields a meaningful model? What are the X, Y and Z axes in that sculpture? Surely, if time and location are factored in, it would have to have four (or more) dimensions, something that would have to be done in a computer to conceptualize. Certainly a three-dimension model would be wholly inadequate. The writer’s throw a bone to the audience when Jenny asks if it couldn’t be done on a computer. I suppose that was their way of justifying the real-world model, trying to stave off critics like me, but Cutter’s reply shows they gave the concept of the model no thought at all, they just wanted to give him a set-piece to brood over visually. (Another writers’ short-cut for portraying brilliance.)

    New rule at the ARC: All employees must be shown a picture of Helen Cutter as a condition of their employment. (Obviously, they don’t have that rule, but I think they should.)

    Even after Dr. Page’s badge is stolen and used to infiltrate the ARC, it doesn’t appear that (a) she either put two and two together and realized the woman that knocked her over was the pickpocket that stole her pass or (b) anyone at the ARC was remotely interested in how her pass ended up in the bad guy’s hands.

    Cutter even deduces that Helen was the culprit, but doesn’t bother to show her picture to Page after the fact. Sloppy. Really sloppy. I hope that doesn’t mean Dr. Page will encounter Helen again and still not know who she is, thus allowing other needless plot complications.

    Let’s turn our attention to the anomaly in this episode. Cutter’s model “predicted” this anomaly, but not when it would arrive – or so they stated. Did his model predict that it would reoccur? That would have been something worth mentioning.

    We’re given no information about where this anomaly is connected to, but it seems reasonable to assume that the creature was a future-creature. At times, it seemed to speak English. Certainly, I thought I heard whispery sounds that were like, “not time yet” presumably referring to the return of the anomaly. This would imply that the creature was intelligent in the human meaning of the word. If so, it was pretty dumb and animalistic in its behavior. Surely an intelligent creature could do a much better job of hiding and waiting for the anomaly to return. Being lured out like a trained animal by the little girl to get food was completely foolish.

    Here’s another problem with Primeval – the things from future seem to be intelligent and menacing. The bat creatures were once even described as possibly the predators that evolved to prey on humans. In the last episode, we saw them slaughter a squad of soldiers who were on a “suicide mission” to the future. Was anyone else unconvinced by that? One unprepared squad of soldiers might be wiped out, but these creatures aren’t immune to our technological weapons. Bullets kill them, and we’ve got lots better weapons than bullets. They aren’t a credible threat, unless, of course, you’re a writer and you’re not going to let the human characters win by making them not try their best.

    What about this cop? He’s obviously been setup as a future character. Will he be ally, foe or wild card that Helen doesn’t know about that ultimately saves the day?

    At the end of the episode, Helen succeeds in stealing Cutter’s DNA. What ever could she want that for? Wasn’t it clever of her to risk so much, steal Page’s pass, send one of her minions (to his death) into the very heart of the high-security ARC just to get Cutter’s shirt to get some DNA, when all she had to do was slip into his unprotected home and get some out of his his brush? (Couldn’t she have done that during the day and had even less chance of getting caught?

    I’ve got to stop know, my head hurts.

  • Talent Show

    It’s time for the kids’ Spring Show at school.

    Seating is strictly first-come, bring your own chair.

    We arrived one hour early and this is the view from our choice seats.

    Guess next year we’ll need to arrive an hour and a half, or more, early.

  • Book Recommendation – iPhone Development

    Since I started programming computers a scant 31 years ago, I’ve had to learn many different programming languages – from ancients like COBOL, FORTRAN and RPG to more modern languages like Java. It’s all part of the game, but undeniably the programming paradigm has shifted beyond all recognition since I wrote that first TRS-80 Basic program all those years ago. They are increasingly more complex.

    What I’ve found is that, with each language, there’s usually a key concept or concepts that “flips the light switch” to understanding. My latest endeavor, iPhone programming, involves learning both XCode development methods and Objective C. Objective C being an extension of C and a cousin of C++ – neither language is one that I’ve had much call to use. So, I’m really starting from scratch on this one.

    Now, this “flip the switch” concept is probably different from one person to another, and, of course, it reflects certain cognitive biases towards certain forms of language and means of explanation – in short, your mileage may vary.

    I was struggling trying to use Apple’s documentation, and even some of the other books on the market were not doing whatever it was that I needed. My latest acquisition, though, Dave Mark and Jeff LaMarche’s “Beginning iPhone Development – Exploring the iPhone SDK” has finally done what I needed to do, and the light has finally dawned.

    Therefore I’d recommend this book to others looking to get their start with iPhone development. They do a nice job of explaining the (frankly bizarre) drag and drop use of Interface Builder to link the nib files to the Objective C code, which was one concept that was really giving me grief. (It all seems almost logical, now.)

    Pity my plans for an iPhone Duckworth-Lewis calculator were scuttled to trade secrets. It’d be a handy tool for non-professional teams for use back in the pavilion.