November 2013

Book Reviews

On Richard Phillips’ A Captain’s Duty (a Book Review)

Most of you know the story.  In 2009, the merchant vessel Maersk Alabama was hijacked by four Somali pirates off the coast of Somalia.  Her captain, Richard Phillips, was taken hostage and was not freed until several days later when a Navy SEALs team shot and killed the pirates.  It became a national story almost immediately:  the first American vessel hijacked by Somali pirates, a miraculous and brave rescue by the U.S. military (always a hit with the news), and a new-found hero in the figure of Captain Phillips, who, we’re told, risked his own life to keep his crew safe. A Captain’s Duty:  Somali Pirates, Navy SEALs, and Dangerous Days at Sea is Captain Phillip’s personal account of the events.  Beginning days before the hijacking, Phillips lays out a populist account of the politics of coastal Somalia, life on merchant vessels, the history of the merchant mariners, and the personal struggles he and his wife endured during and, to a lesser extent, after the hijacking.  As a work meant to educate and entertain, it is at times quite dull, and at other times quite fascinating, though not necessarily for the reasons you’d expect. What I found most compelling about this book were its sections on life in pirate-heavy seas.  Many of the chapters are preceded by quotes highlighting previously successful hijackings, and the chapters themselves provide a fair amount of detail about the procedures for dealing with piracy and the knowledge sea captains like Phillips must acquire before and after they traverse the seas.  These sections were the most interesting in the book, as they highlighted the real problem piracy poses and provided Phillips’ personal perspective on the issue.  If anything, these sections do far more to describe who Phillips is than any of the chapters about the hijacking of the Maersk Alabama.  They likewise provide a somewhat populist view of the issues in the Somali region, which do certainly add sympathy to an already sympathetic figure. However, these chapters are sometimes overloaded by excessive description.  The book was clearly written for a general audience, yet some sections of the book obsess over the minute details of ship life, most of which have no direct bearing on the events yet to unfold.  One section on the captain’s duty to inspect the ship could easily have been left as a short paragraph explaining what the inspection is for.  I’m sure someone who finds ship life idyllic — or, perhaps, romantic — will find value in these sections, but I personally felt they drew away from the more pressing concern:  piracy.  Truthfully, I was far more interested in how an actual ship captain views life in dangerous waters than in everyday ship life, as it is difficult to form an objective opinion on such matters from the safety of my computer chair.  Regardless, though there are some rather dull sections in the book, the overall thrust of the first few chapters is worth reading, if only for the reasons I have already stated. Unfortunately, Phillips’ account of the actual hijacking strains credulity.  While one can forgive him for making assumptions about his attackers, mis-remembering details, or even conjuring some up in an apparent dream-like daze, his assessment of his own behavior from the beginning of the hijacking makes one wonder why the U.S. Navy was all that concerned about Somali pirates in the first place.  For example, Phillips reminds us more than once that the Somalis have been enormously successful at hijacking ships and earning ransom as a result.  At no point are we to believe these pirates are completely inept at what they do, even if they are poorly armed, trained, and supplied.  Phillips spends considerable time, as I’ve noted above, describing how Somalis perform hijackings, their success rate, the politics, and so on, painting a fairly clear picture of just who we’re about to deal with; that picture offers credence to the threat of hijacking. But once the hijacking occurs, the Somalis are presented as dimwitted to the extreme, completely inept at just about everything; they are described like children who only just figured out how to turn on the boat.  They seem utterly perplexed by the boat’s machinery, despite clearly having at least a basic understanding of radar equipment.  Worse, throughout the ordeal, Phillips claims to have been in continuous contact with hidden members of the crew via a handheld radio he “snuck away.”  Only he repeatedly uses this radio right in front of the Somalis, or at least within sight, such that it’s really quite impossible to believe that they haven’t noticed.  This is made more unbelievable when we’re reminded that the Somalis are rather annoyed that Phillips doesn’t know where the rest of his crew is.  One problem:  clearly he does, and even if he didn’t, he’s clearly in contact with them. This particular issue doesn’t get better over time.  Frequently, Phillips is shown giving away tactical information to the crew — numbers, weapons, positions, etc. — while looking straight in the eye of the hijackers.  It’s as if we’re supposed to believe these Somalis are not only really bad at what they do, but completely disinterested in the fact that their captive is sharing sensitive information with the very people they wish to find (or, in some cases, with the military itself, as Phillips communicates with the U.S.S. Bainbridge while trapped in the cramped lifeboat).  All of this is dropped from the film adaptation — probably for the exact reason that bothered me:  it just doesn’t make sense. The book’s other flaws are in its contradictions.  For example, Phillips tells us that the Somalis let him swim in the ocean to cool off after kidnapping him and fleeing in the lifeboat.  But several chapters later, Phillips tells us the Somalis never let him out.  One of these two statements is true; they both can’t be.  These details draw into question other aspects of the narrative, such as Phillips’ claim that a Somali boat came to

SF/F Commentary

Updatery and An Interview w/ Me: Postmodernism, Comics, SF/F, Podcasting, and Larry Nolen

Two quick things for readers of this blog thing: I’ve not been active on the blog throughout much of November for one very simple reason:  this is the busiest month of the year for me, and more so because I’ve been working almost non-stop on exam materials throughout the month and the three months preceding it.  I’m getting a PhD, after all. I also have a lot of other stuff to deal with:  I’m grading a lot of papers (teaching three classes), I have three exams to write up and administer, and I’m teaching a bunch (four days a week).  Add all that in with holidays and so on and you’ve got a not-very-active Shaun person.  Granted, I’ve also been playing a bit of Starcraft 2 as a stress reliever, so… But there’s one interesting thing going on, and that’s this: Larry Nolen of OF Blog of the Fallen just posted a 5,500-word interview with me!  I think it will be of interest to readers of this blog, as Larry asked me questions about blogging, podcasting, comics, postermodernism, fandom, and much more.  I think it’s a pretty darn good interview.  Feel free to read it and leave a comment over there. And that’s that!

SF/F Commentary

A Plea for Universal Free Wireless (in airports, at least)

I am currently sitting in Houston’s magnificent airport after leg two of my four-leg flight to Sacramento.  The things I do for family… Anyway.  A few hours before, I was in Tampa, FL, whose airport not only has a pretty impressive view of the skyscrapers in a gorgeous dawning sun (I have a picture that I can’t share right now for reasons that will become apparently shortly), but they also had wireless.  Gorgeous wireless.  It was relatively swift, allowed all of my normal functions (blogging, Twitter, Facebook, general searches, etc.), and was all around just good.  Before that, I was in Gainesville, FL, whose airport barely deserves the title, but also includes at least usable wireless — it’s not all that quick, but compared to the public wireless at the community college where I am employed, it is like night and day. Houston, however, has none of these things.  Right now, I’m snatching wireless off one of the airline desks nearby; they apparently have never heard of passwords.  This service only allows me to access Blogger and general search, but Twitter and all of my apps (even the ones that have nothing to do with social media, but require Internet to function) are blocked.  I can’t even search for ebooks on this thing… The only other public option around here is one run by one of the hotspot companies.  It costs $4.95 for an hour, which is the only time I can use anyway (your only other option is $7.95 a month, but since I don’t fly all that much, let alone to or from or around Houston, it’s really not worth it).  I think this price is basically extortion.  In other words, there is no viable Internet option here. This is not the first time I’ve been trapped in an airport without free wireless.  You’ll forgive me for demonstrating my privilege, but I think all airports should have free wireless by default.  There are a lot of good reasons for this, from simple convenience and customer satisfaction to the fact that social networks allow information to move quickly within airport terminals (just in case something has happened inside and you don’t know what’s going on — Tweeting, after all, is quiet; then again, maybe this is a stretch).  Ultimately, I think customer satisfaction is the one that will matter most, as giving us access helps us pass the time doing something we apparently enjoy, whether it’s chatting with friends online, reading online newspaper articles, searching for an ebook to read, or something else. So this is my plea for universal wireless in airports.  I’d love it if Internet access were universal in general, but I think this is a good place to start. Go wireless, go wireless, go, go, go wireless!

SF/F Commentary

Star Trek: a Worf TV Show? (Some Thoughts)

A few weeks ago, the Huffington Post released an interview with Wil Wheaton and Michael Dorn, who played Wesley Crusher and Worf (respectively) on Star Trek:  the Next Generation.  I recommend reading the whole thing, but for now, I’m only concerned with one quote from Dorn: Business things got in the way in terms of the JJ Abrams movie coming out and CBS/Paramount and their relationship with JJ Abrams. I don’t think they wanted to step on his toes by putting a new series on, but it’s not dead yet. I’ve finished the script and hopefully someone will take a look at this and say “we can do this.” Basically, we’re not that far off from seeing a Captain Worf TV show.  Let me say that again:  a Captain Worf TV show.  By “not far off,” of course, I don’t mean “next year.”  This is Hollywood, after all, and even getting into talks with the studios still means you’re about as far from production as we are from going to Mars.  Still, in production terms, that’s a lot closer than “I’ve got the rights” or “I wrote something” or “someone answered my phone call.”  In other words, yeah, we’re really not that far off from a possible show. The big questions are these: How exactly are they going to fit this show into the universe everyone now knows (Abrams’)?  And if they’re not going to integrate Worf into this new universe, how can they justify the character to a new viewing public? First, there are big problems with sticking Worf into the Abrams universe.  Even taking into account the ridiculous time travel changes that have occurred, the character of Worf doesn’t appear until well after the events of the first two ST films.  He’s from an entirely different era, and his character is so defined by that era that to try to artificially shove him 100 years forward would entail an entirely different set of political conditions, most notably the fact that the Federation and the Klingons haven’t even begun their war in the Abrams universe.  Star Trek Into Darkness takes place in 2259 — eight years before the Federation-Klingon war took place in the original universe.  And the film makes clear that war is pretty much inevitable, as it was in the original universe.  Since Worf’s character is partly defined by the post-war period, after which the Klingons eventually sue for piece (as in The Undiscovered Country), it doesn’t make much sense to shove him into the immediate universe of the Abrams film.  That said, I wouldn’t be surprised if they did just that, since this film series seems incapable of inventing new characters; instead, they borrow liberally from everything that came before. One of the other problems has to do with which ST TV shows people are most likely to remember.  The Abrams ST films are probably more popular with casual or non-Trek viewers than with the traditional Trekkie crowd.  As such, its primary audience likely knows about TOS, TNG, DS9, and Voyager, but their most recent ST experience would have been with Enterprise.  The good news:  STE doesn’t violate Abrams’ new canon, since its events, more or less, take place before Kirk’s birth (in fairness, I haven’t finished STE yet, so there may be stuff in there that contradicts this).  You could easily suck STE into Abrams’ canon without much problems, which is not something you can easily do with a Worf TV show which springs off of TNG and DS9 (as the title, Captain Worf, suggests). A show set in the Next Gen universe will also have a hard time competing with the film universe precisely because its characters aren’t the dominant representation of ST anymore.  They may be some of the most recognizable non-TOS characters in the ST canon, but the universe we’re playing in now would, by its very nature, have to diverge significantly from the world we learned about in TNG.  After all, the Vulcans aren’t really there to help out anymore.  They’re a decimated species who might, in 100 years, get some semblance of interstellar control back, but they’re basically out for the count right now.  And that means Abrams has to take into account that the Klingons will likely have more of an influence on the Federation than they would have had before — they’re minus one formidable opponent. Right.  Wandering.  This is the problem.  The Abrams universe has become, in my mind, *the* ST universe.  It’s the one we’re all really talking about as a culture.  As much as I want a Captain Worf show set in the TNG universe, I worry that it will only confuse new fans of ST.  After all, part of the reason the new ST movies are so action oriented is to snatch up younger viewers.  It’s not designed for Trekkies, as much as they might hate the idea.  And the worst thing you can do to a newer, younger (and, hey, possibly older-but-never-been-into-ST-before) crowd is confuse them with ST stuff that doesn’t fit.  Well, maybe not the worst thing, but it’s a legitimate concern. But who am I to say it won’t work?  I’ll watch the show regardless, as will most Trek fans.  Worf is a beloved character, and watching him grow as a formidable captain would be pretty awesome. Bogh tlhInganpu’, SuvwI’pu’ moj, Hegh!

SF/F Commentary

Top 10 Posts for October 2013

Here you go: 10.  Crowfunding Links of the Week:  Kaleidoscope (a Diverse YA Antho) & War Stories (a MilSF Antho) 9.  Draft Post Bingo:  What should I finish?  You Decide! 8.  Top 10 Science Fiction and Fantasy Movies Since 2010 (Thus Far) 7.  Ideological Rigidity (With a Side of Genre)(Adventures in Teaching) 6.  Top 10 Cats in Science Fiction and Fantasy 5.  Top 10 Blog Posts for September 2013 (ha!) 4.  Pixar Feature Films (from the worst to the best) — A List That Will Get Me Killed 3.  Top 10 Overused Fantasy Cliches 2.  Movie Review:  Riddick (2013) (or, I’m Going to Mega Rant Now) 1.  Link of the Week:  Judith Butler Explained with Cats!

Scroll to Top