Reading too deeply into these things since 1981
Header

I, PartridgeAs you know, I’ve been reviewing self-published books on this blog recently. As you also know, I’m currently writing a novel of my own. So allow me to pass down something that’s done me a great deal of creative good.

Here’s the single hardest lesson I had to learn as a writer. Are you ready? It’s a pretty brutal one:

I sound ridiculous.

And guess what? So do you.

We all sound ridiculous…at least by default. That’s why literature, in all of its forms, has evolved a set of conventions. Romance, comedy, tragedy, mystery, memoir…anything you read will have associated with it a whole host of expectations. Conventions exist for a reason, and that reason is this: they double as the contract between author and audience.

When you read a piece of literature, it’s often fun to point out the tropes and conventions as you go. If you’re especially well-read in a particular genre you might even be able to map out what’s likely to happen next. The big mistake we all make is to surrender to a sort of cynicism that implies this to be a bad thing. It isn’t.*

Conventions exist because people like to know what they are reading. It’s similar to ordering meals in a restaurant…you like to have some sense of what it contains. You don’t necessarily need to know exactly how much of what is in it, or how it was brought together, or how it’s going to taste…but it’s not out of line to want some knowledge of what you’re about to eat. After all…you’ve been eating for your whole life. You know that there are certain things you simply don’t enjoy, and other things you enjoy very much.

When writing, those unspoken conventions serve the same purpose. We should be able to know if mysteries, on the whole, appeal to us without having to read every single one of them. Some will be better than others, sure, but that’s a given. We know that, and conventions don’t at all suggest anything in a qualitative sense. What they do tell us is a list of the ingredients the work is likely to contain. For instance, maybe you read Raymond Chandler and didn’t like the terseness of his writing. In that case, you may simply not be a Chandler fan. However if you read some Raymond Chandler and didn’t like the violence, the red herrings, the alternating seduction and cruelty, or the seemingly silly pursuit of some relatively minor object, then you can pretty much count on the fact that you don’t enjoy detective fiction.

That’s fine. That’s why those conventions exist. Those of us who like it know where to find it, and those who don’t know to look elsewhere.

They also exist in order to give writers direction. The greatest literary artists know how to elasticize them, distort them, give them new and interesting ways to work, but, ultimately, they are there, and they function as signposts. The author may then choose to pull toward those sign posts, to loop mischievously around them, or to deliberately drift as far from them as possible. In any case, they are still there…and if they weren’t, we wouldn’t be able to appreciate what the artist is doing.

You — yes, you, if you intend to write — need to understand this, because it’s what’s going to keep you from sounding ridiculous. These structures and conventions and signposts exist, all of them, explicitly so that you won’t sound like a fool. Because if you just allow yourself to write, without being well-versed in the conventions and expectations of your genre of choice…that’s exactly what you will sound like.

I, Partridge is the rarest of all possible comedy tie-in books: it’s the comedy tie-in book that is also, front to back, a work of art.

It’s the ostensible memoir of Alan Partridge, a fictional character who has appeared in multiple British television and radio programs, as well as stage shows, specials, and pretty much everything else. I, Partridge is that character, recounting his life experiences. And it’s a brilliant work of incredible unreliability.

Granted, if you’ve seen and heard Partridge’s earlier misadventures then I, Partridge doesn’t have to work quite as hard. You’ve seen him shove a piece of cheese into a BBC superior’s face and use the hand of a dead man to sign a contract that would put him back on television, so when Alan narrates these events differently, you understand very clearly the humorous disconnect.

However I don’t think you have to have seen any of that in order to enjoy — and as a writer learn from — the book. It functions within its own reality brilliantly, with Alan’s suspiciously too-careful recitation of details giving away the fact that something is being clearly fabricated.

Throughout the book he misunderstands social cues and signals that the readers pick up on, leaving his narration and the reader’s experience of that narration to diverge wonderfully. Alan continues down a road of doubled self-delusion (as he certainly believes that his readers are taking his lies as gospel) while we are able to parse and inspect the text in order to determine just how far from reality his narration really is.

It’s every bit as fascinating as anything Nabokov — the unrivaled master of unreliable narration — has ever done, but is infinitely more accessible. And for that reason, I think I, Partridge should be required reading for anyone who believes themselves to be a writer.

Alan’s ridiculousness is palpable, and it’s palpable simply because he believes he’s being anything but ridiculous. He couldn’t begin to entertain the fact that anything he’s saying would be suspect…and that’s exactly why it’s so suspicious. His readers stop paying attention to what he says, and start paying attention to how he says it.

Your readers will do the same thing. Because you sound ridiculous.

When reading A Soul’s Calling, there was a similar disconnect. Scott Bishop — or his textual avatar — fancied himself an educated, spiritual humanitarian…but he came across on the page as a foolish, selfish weirdo. When he says that demonic spirits interfere with his life and make people dislike him, he believes it…yet the narration diverges from the experience of the reader, who sees instead that people dislike him because he’s an actively insufferable human being. And when he — in an act of paramount dickishness — finds a prayer note left at base camp by a woman before him, he burns it instead of leaving it under the rock where she left it. Why? Because he knows how this prayer needs to be handled, and she obviously didn’t. In his mind, he did her a favor. Any reader in their right mind, however, would see this as a tremendously rude gesture, and the anonymous woman would be no less hurt by it than Scott himself would be if someone came along and kicked over his pyre because they personally didn’t think that was the right way to pray either.

Similarly, when Lawrence Fisher positions himself as an unfortunate misfit wrestling with the game of love, we as readers see clearly that he’s not alone…literally every woman he dates, whether or not that date goes well, is in the exact same situation, meaning it’s a bit harsh for him to expect us to both feel bad for him and laugh at them when he says they’re annoying, not pretty enough, or just plain undateable. Lawrence wants us on his side as narrator, but he spends so much time pushing away those who are already on his side that we end up distanced as well.

What’s more, he keeps distracting himself from his ostensible topic to quote irreverently from films and television shows, or discuss historical intricacies of his religion, or wonder how people can be rude enough to speak through BlueTooth headsets in a restaurant. There’s nothing wrong with that, but the book is only around 130 pages and he’s spent so much time on tangents that he’s left himself no room to getting around to his actual topic.

What writers need to learn, whether they intend to employ the method or not, is how unreliable narration works. And they need to learn that lest they start narrating unreliably against their will.

I, Partridge features exactly the same failings as the two self-published books I mention above, but with a difference: here, they are failings by design.

Alan assumes the applause for a crippled veteran are directed at himself, a low-level radio personality. He gets lost discussing technical details about headsets and cars and radio frequencies when he’s meant to be relaying interesting anecdotes about important people in his life. His “big breaks” for other up-and-coming performers typically leave them embarrassed, disgraced, and broke.

But Alan doesn’t realize any of this. He is the central comic figure in his own farce, but sees himself as a hero, overcoming tragedy after trial. He uses his complete command over his own memoir to rewrite history, and to paint himself in colors he could never achieve in real life.

Writers do that all the time. And that’s okay.

But they need to do it deliberately, and they need to do it well.

Because if they don’t, they’re just writing their own unintentional comedies.

It doesn’t take much to turn your heart-warming tale of spiritual awakening into a showcase for self-importance and silliness. It’s just a shift in perspective…and it’s the shift in perspective that comes automatically from giving yourself an audience.

I honestly would recommend I, Partridge to anyone who wants to be taken seriously, because the absolute best first step on that road is to see, first-hand, why nobody would.

—–
* At least, it isn’t automatically a bad thing. If that’s all an author is doing, then that’s bad. But an author who uses convention as a framework upon which to build his or her unique story around it is simply doing his or her job as a writer. Railing against convention for the sake of railing against convention is something else many writers find it difficult to grow out of. But mark my words: the longer you spend fighting the form, the more you’re postponing the moment when you learn how to make the form work for you. In short, you’re delaying your own creative growth. So don’t do that.

Retro City Rampage

Good gosh!
The hero has arrived.

Last month, a game called Retro City Rampage was released for download on the Wii. By this point, the Wii is already dead, its place in the console market usurped by the WiiU. This was a too-late release for the system in another way as well: other versions of the game on competing systems were released in 2012. The game itself was announced in 2010…and development began all the way back in 2002. That’s an extremely long journey for anything on its way to a dead platform.

I remember the announcement well, because I decided more or less immediately that I didn’t want it. It seemed like a nice idea — retro-style games such as Mega Man 9, the Bit.Trip series and VVVVVV had a pretty high success rate as far as I was concerned, and I’d take a simplistic, difficult romp over a modern-day talky slog every time — but early screen shots, and then the eventual trailer, were enormously disappointing.

Or, rather, there was one specific thing about those screenshots and trailers that was disappointing: the sheer number of references.

Retro City RampageI’ve written about this before. I’m simply not a fan of references for references’ sake. I don’t like the modern tendency for the snake to wink as it swallows its tail. I want to see art that carves out its own space to inhabit…not lazily inhabit the spaces carved out by those who came before.

There’s a place in the world for parody — of course there is — but that place is not front and center. That place is not in the spotlight. When parody becomes the dominant form of expression you end up with garbage like Epic Movie, which ends up spoofing Nacho Libre because there simply isn’t enough straight-laced material to serve as fuel anymore, and comedy has to begin eating itself.

Personally, I’m happy to blame Family Guy for the glut of lazy references and recreations masquerading as something new. Parody has existed long before Family Guy, of course, and lazy parody has existed exactly as long. But only Family Guy seems to have found more success the lazier it gets, to the point that entire sequences and acts consist of word-for-word reenactments of other programs, films, music videos, or anything else the writers might have watched earlier that week.

It’s lazy, and it’s not creative. But people eat it up. Prior to its first cancellation, Family Guy knew how to pull off its warped style of twisted comedy. Since its revival, it’s circled ceaselessly toward a lazy singularity, replacing jokes and cleverness with joyless recreations. It’s not funny, it’s not interesting, and it even drifts into the territory of insult when they decide to lift wholesale scenes from other parodies, such as Airplane! Perhaps the Family Guy staff simply can’t tell the difference anymore. Certainly its audience can’t. And that’s beyond disappointing…that’s irresponsible.

Retro City RampageRetro City Rampage appeared to be following in those footsteps. One of the areas resembled the first stage of Metal Gear for the NES, complete with on-screen mocking of that game’s infamous Engrish. Two of the characters are named Bill and Lance, who we remember from Contra. A store called WonderHats uses the ThunderCats font. A dessert parlor is called Vanilla Ice Cream. Tee hee hee.

Even its title is a triple reference: Grand Theft Auto, River City Ransom, and Rampage. This is all before you get to the clear Back to the Future homage of its cover art. The entire thing just screamed out that it was pieced together from bits and fragments of better things.

It felt cheap. It felt lazy. It felt like it was attempting to coast on the goodwill engendered by its source material, rather than any merit that it could have possibly earned on its own. It wanted the laughter of recognition. And that’s quite possibly the least satisfying kind of laughter there is.

The game boasted a huge world to explore, but if all I was doing is finding cutesy puns on the signage and identifying bland references to better games, then it didn’t feel worth exploring. At least Family Guy delivers its own personal blend of offensive laziness to you passively…Retro City Rampage required interaction. It wasn’t enough to just groan at what you were seeing…you first would have to make the effort to track it down.

And I wasn’t interested in that.

But I learned something from Retro City Rampage. Specifically, I learned that Family Guy has done even more damage than I thought. Because not only does it train me to see references like this — even in things that I enjoy — as unnecessary and annoying, but it made me forget why people started making references like this in the first place: love.

At Nintendo Life, Featured Editor and all-around great guy Thomas Whitehead interviewed Brian Provinciano, essentially the single man responsible for the entire game. And it was a good interview, but here’s what really stood out to me:

It became public knowledge on Gamasutra in 2009 that a sales threshold is in place, whereas, if you don’t sell enough copies [as a WiiWare download], you don’t get paid a cent. [...] Many developers became unable to sell enough units, and this became a reason for so many cancellations of announced WiiWare titles. The publishers knew they wouldn’t make a cent and needed to cut their losses. Between the office rent, hardware, insurance, game ratings and other costs, had I not done the WiiWare version, I could’ve saved around $20,000 – not even including my salary in porting it. And as it stands, virtually no games hit the threshold these days, so it’s only being released as fan service. A $20,000 gift to the fans.

There’s no chance — and I say this in the nicest possible way — that Retro City Rampage will hit that sales threshold. Most games released through the WiiWare service never made it, and that was definitely one of Nintendo’s major missteps with the Wii. Far from encouraging developers to put their best work into the console, it encouraged them to put it anywhere else. Releasing through WiiWare was expensive, and as more developers and games failed to turn a profit, fewer developers and games went near the service at all.

Retro City RampageWith fewer games, the audience simply drifted away. A sales threshhold that was already near-impossible to hit just got shoved that much further out of reach.

Additionally the Wii is dead. And, with it, WiiWare. Retro City Rampage comes long after most Wii owners will have upgraded to the WiiU, and the ones that stayed behind aren’t likely to be in the habit of checking the shop channel anymore. On top of that, just about anyone who was dying for Retro City Rampage would have simply bought it somewhere else over the course of the past year.

And yet, here it is. Not because it’s expected to make any money…in fact, Provinciano is convinced it will lose him money. And I agree.

But he released it because he could. Because he made enough money from its other versions to put this one out there on a Nintendo console, as a gift to the fans. A “$20,000 gift to the fans,” to be exact.

And that’s love. That’s love, and that’s nothing short of love.

That’s also what made me buy Retro City Rampage. I know this version of the game won’t make a dime, but I bought it anyway. Because that’s the least I can do. Far from the smorgasbord of lazy references and winking visual recreations of classic games, Retro City Rampage was made with love. How do I know that? Because nothing but love could make you shovel twenty thousand dollars into a release you already know will be totally unprofitable.

It’s what I remembered about references, about why people make them, and why they took such an easy foothold in parody and pop-culture: making them betrays, or should, a love for that source material. It’s a form of flattery, a form of tipping one’s hat, respectfully, to those that laid the groundwork for what you are now able to do.

Family Guy doesn’t express love. It can’t, because it feels none. Its references are lazy at best and outright mean-spirited at worst. Robot Chicken feels very much the same way. It lives to deflate the cultural ephemera of days gone by. By contrast, when Futurama incorporates the lore of other science fiction works into its universe, it feels like the show saying thank you…no matter how they subvert the character, idea or object. Futurama exists because its creators and writers love the genre, and want to play with the same toys. Family Guy might have existed at first because Seth MacFarlane loved the golden age of television, but it continues to exist just to feed more meat into the grinder. It all comes out the same. A joyless, tasteless, inconsequential mush.

Retro City RampageRetro City Ransom, which I can say now that I’ve played it, is great. But I almost missed it, simply because I forgot that references aren’t always lazy…they’re often, when done right, admirable. They’re a familiar seasoning in a new and exciting dish. At least, again, when done right.

Many years ago, in 1999 or so, I made two video games myself. They were both part of the same series. The first was called Larry Vales: Traffic Division, and its sequel was Larry Vales II: Dead Girls Are Easy. I haven’t thought about them in a long time, though certainly at the time I was working on them they were everything to me. I invested a lot of creative effort into two games that, for all their faults — and there were faults, boy howdy — people enjoyed. That was all I really wanted. I wanted to make people laugh, and I wanted people to have fun.

A couple of years ago I found a video on YouTube of somebody playing through the first game. I watched it, and re-experienced the game for the first time in around a decade. And I was overwhelmed by the number of references I crammed into it. Whereas Retro City Rampage mainly pays homage to classic NES games like Super Mario Bros. and Bionic Commando and Teenage Mutant Ninja Turtles, Larry Vales paid homage to The Simpsons, and 1984, and Pink Floyd. In short, it was everything that had inspired me, at some point…just as Provinciano refers back to everything that inspired him.

Watching that video, I cringed. I felt lazy. I felt as though I had every opportunity to make something interesting and unique, but I fell back on mindlessly referring to other things that I enjoyed, hoping that others would share in the nostalgia, and that would be enough. I was being a bit harsh on myself, I think now, but I also believe there’s some truth to that.

But that’s just the Family Guy effect. I felt guilty for making those references because the practice of paying gentle homage to your inspirations has been dragged through the muck and become something dirty, something lazy, and, above all else, something to be avoided.

Retro City RampageWhat I forgot — or, perhaps, was in no condition to remember — when watching that video, someone else playing through a game world of my own construction, was that I made those references out of love. They may have been lazy. They may not have been funny. But they were my way of saying thank you…of openly expressing my gratefulness for the so many wonderful things that made me want to create.

That’s a lesson Retro City Rampage taught me, all over again. There are a few bad apples that have poisoned the practice…but, in doing it right, it’s still as noble a way to tip your hat as it ever was.

References are a way of saying thanks. That’s something I’m going to try to remember again. Perhaps, one day, I’ll even give those thanks right back to Retro City Rampage, for showing me that someone, somewhere, still knows how to make them for the right reason, in the right way.

Hell, releasing Retro City Rampage at all, with the complete foreknowledge that it will only lose money, is a way of saying thanks. Provinciano is using Retro City Rampage as a sort of double-sided note of appreciation…he’s thanking the industry that inspired him, and the players who’ve been inspired right along with him.

It’s an admirable thing to do. And I really do hope he ends up turning a profit, against all odds, because it’s nice to see goodness rewarded in the world every now and again.

And the game is also, to put a fittingly obscene button on it, pretty fucking incredible.

Detective FictionSo it’s been quiet around here lately, and there’s absolutely nothing noteworthy about that fact. But I did want to pop in to let you know that, unlike every other time, I haven’t been totally unproductive. In fact, I’m writing a book.

It’s a project that I started for National Novel Writing Month a few years back. For those of you who aren’t familiar, the idea is that you are supposed to write an entire novel between November 1 and November 30. I’ve participated a few times now, and I’ve nearly always succeeded, but it’s very much worth noting that they define “a novel” as “50,000 words.” So you can very easily hit that number without bringing your story to a close, or even getting anywhere near an ending.

For many it’s just a writing exercise, which is great, but for me…I’ve always tried to do something more. 50,000 words of anything is a useful workout for a writer, but I feel a little let down at the end if I don’t have something I can share. Rework, rewrite, edit, extend, sure…but I at least need to come away with something I can show for my investment.

My first completed novel that I owe to National Novel Writing Month is Afterbirth: The Comedy of Miscarriage, which took me two years to write and another five to really shape into what I needed it to be. It’s a piece of work I’m immensely proud of right now, a book that manages to be clever and complicated enough that I can’t believe some schlub like me wrote it. In fact, it’s so good that nobody wants to publish the thing, and it’s sitting around doing absolutely nothing.

Detective Fiction was a deliberate response to Afterbirth. The former is massive in scope and scale, scrambling up scenes across generations and narrated by a self-serving trickster, leaving the reader to fend for himself or herself from paragraph to paragraph, trying to piece together the story that lies beneath what’s actually being said. It was hard to write. Heck, it’s hard to read.

So for my next project, my next real project, my next big novel attempt that I could actually spin into a finished manuscript at some point down the line, I went intentionally simple. It’s a straight-forward story without any significant leaps through time, with a manageable cast of characters, and with a clearly defined beginning, middle, and end. I didn’t want it to get too big. I didn’t want it to get too complicated. Because…well, I already had one of those. And it went–and continues to go–absolutely nowhere.

Detective Fiction, I reasoned, could make for an easier sell. It’s a simpler pitch, its first few chapters won’t scare people away, and I can make an effort to be a little more overtly funny. It should still be good, but it could be good in a way that plays more nicely with its readers.

My plan was to write a sendup of the detective fiction genre, starring a young man in the fictional Palmwood City, Florida, who decides to operate as an unlicensed private eye in order to draw focus away from a few other things in his life. I delved into some classic examples from Raymond Chandler to Arthur Conan Doyle and realized, shockingly, that these books were actually a lot better than I gave them credit for being. In fact, my attempt at a joke very quickly turned into a love letter, as I realized the reason that these stories endured: they only pretended to be about the mystery. They were always actually about the detective.

But I never finished the book. I wrote most of it, hit the 50,000 word goal, but never brought it to a conclusion.

And it languished for two years. While I did absolutely nothing with it. Honestly, I was afraid to go back. As simple as I wanted the book to be, I was still trying to provide three things at the same time to the reader: a good read, a genre pastiche, and a satisfying mystery…in roughly that order. And the more time passed, the easier it became to just assume that I had failed, that it was a scattered mess, and it wasn’t worth revisiting.

Recently, I revisited. And it was far, far better than I remembered it being. So I thought I’d dig back in, and give young Billy Passwater the conclusion his story so specifically deserves.

I have one chapter left to write. I intend to do that tonight. I will then spend months (at least months) rewriting, and rewriting, and rewriting, and rewriting.

And before long, I hope to have something I can send out to agents. Something I can be happy to have my name on, and something they can be happy to have their names on as well.

I know I’ve been quiet, but I haven’t been unproductive. I hope you understand why I’ve decided to focus my energies elsewhere for a time…it’s now or never for Detective Fiction.

Noiseless Chatter isn’t dead. Detective Fiction doesn’t represent me having nothing to post here anymore. If anything, as the man himself once said, “Things should start to get interesting right about now.”

(Kudos to the friendly Ridley for that banner.)

A Soul's Calling, by Scott BishopFTC Disclosure: I received a copy of this book in exchange for review. No money changed hands and all opinions presented here are my own.

When I was a boy, I used to go camping with my father. During one of these trips, my brother and I decided to take a little walk together. We didn’t think we walked very far, but trying to find our way back to the campsite was difficult. Everything looked the same and the return trip took at least five times as long as the journey out. Ultimately, though, we found our way back.

That which you have just read is true. But it is not, I absolutely hasten to add, a story. It might be an anecdote, but I doubt it’d be a very entertaining one. More likely it’s the sort of thing I might bring up with a group of friends, all of whom are exchanging brief, inconsequential narratives on the same theme (being lost, childhood memories, camping with kids…). But even in the right context, it doesn’t become a story. It’s just something that in some (but certainly not all) cases might be worth repeating.

I could drag it out, certainly. I could add reams of accurate detail that may well make the recitation more vivid for my listeners, but the compounding of unnecessary detail doesn’t turn it into a story either, and without a great deal of fictionalization, it never could be one.

There’s nothing wrong with fictionalization. At least, not within the context of fiction. (That’s kind of where the word comes from.) Fictionalization is a good thing for stories. In fact, I’d go so far as to say it’s the single most important thing. Storytelling is an art, and art lives and dies by the talent of the artist. We might be fine listening to a close friend tell us about a personal experience, and in that case we might feel cheated if we later found out he was embellishing it excessively.

However when we pick up a novel, we don’t want to read a dry recitation of something that the author did. First of all, that’s not what a novel is. And secondly, the novelist needs to demonstrate, in some way, a mastery of his art. This can take many forms, of course; it can be the active and deliberate bafflement of Joyce or the intense simplicity of Hemingway. It can — even better — be one of numberless possibilities in between those two extremes.

But an artist has to do something, otherwise he isn’t creating art. He’s just saying things.

A Soul’s Calling, a novel based on author Scott Bishop’s experience of hiking to the base camp at Everest, just says things.

It’s admittedly difficult to issue this as a universal criticism, especially since the writing in A Soul’s Calling isn’t uniformly bad, but this is essentially a long, long first-draft that is in dire need of a more compelling rewrite. As it stands it reads no better than my camping anecdote, but takes around 1,700 times as long to finish saying nothing. And that’s the problem. Some of my favorite pieces of writing “say nothing,” but they say it in so moving, amusing, or thrilling a way that the act of saying nothing becomes a kind of art unto itself. It takes — or, rather, is sculpted into — a shape, a series of shapes, patterns within patterns that compose themselves into larger movements and statements. That’s what fiction is for.

A Soul’s Calling doesn’t do that. It presents copious details in the hopes that obsessive accuracy will eventually conjure up its own kind of interest in the reader. But it does not.

To be honest, I’m not even sure I should be judging this book as a novel. Its back cover refers to it as a novel, yes, but it also refers it as a memoir…and those two things are mutually exclusive. You can’t actually be both. You can be a Nabokov-esque memoir of a fictional character, or you can be a Vonnegut-like fictionalized memoir, but in each case you’re still writing a novel, and the format (or intention) of memoir becomes a utility…a filter through which that novel is read.

That is not what we have here, and though I’m making a bit of an executive decision by calling it a novel, I think the presence of spirits and talking mountains and a main character who receives visions of an apocalyptic future that he alone can avoid somehow by making this journey all seat the book firmly in the category of “fiction.”

If any of that seems to be out of place for a story about a journey to Everest, then you might be disappointed to learn that it’s also completely unnecessary, and — to be honest — nonsensically handled. When Kurt Vonnegut takes us away from the real-life horrors of World War II to make comical digressions to an extra-terrestrial zoo, or Thomas Pynchon sees it fit to insert a sentient mechanical duck into the surveying party of Charles Mason and Jeremiah Dixon, they do so in order to make colorful points about the things we think we’re familiar with…in order to slant our perspectives enough that we can view the familiar in a new and unexpected way.

However when Bishop employs these strange intrusions, they serve only to confuse his intentions. What’s more, they ring loudly as artificial and empty gestures. After all, when George Mallory was asked why he intended to climb Mount Everest, he famously (and maybe apocryphally) replied with three words that have been connected with the mountain ever since: “Because it’s there.”

Everest is, within our cultural landscape, a mountain whose conquering legendarily requires no justification. It is in itself a justification. If reaching its peak is understood universally as being entirely free from — and separate from — mere human reasoning, then I’m not sure why we need urgent entreaties from the Spirit Realm to justify the comparatively minor trek to its base camp.

The real problem, though, is that this unnecessary justification fails to even justify itself. There’s nothing inherently wrong with making the protagonist the “Chosen One” who alone can prevent massive calamity on a universal scale; this has been the backbone of everything from The Bible to The Hitchhiker’s Guide to the Galaxy. There are countless places you can go with the idea, which is what keeps it from feeling stale in the right hands. It may come across as somewhat trite, but it’s an acceptable triteness that we expect will pay off in some interesting flourishes along the way.

In A Soul’s Calling, however, the protagonist / narrator (who shares a name with the author) some emissaries from the spirit world turn up, tell “Scott” that he needs to journey to the base camp at Everest, and then essentially disappear from the novel entirely. We do hear from them again, but they never actually explain what the issue is, what exact function “Scott’s” journey will serve, or why “Scott” was chosen at all. In fact, every time the narrator describes these conversations or visions, he lapses into an evasive textual shrug, admitting that he can’t really explain what he saw or heard…so, I guess, we just have to trust him when he says that his ethereal Princess Leia assured him he was our only hope. Whether or not he was qualified to shoulder the burden of universal salvation I can’t say, but as a reader I’m absolutely positive he’s not qualified to narrate if he can’t tell us about the most interesting things in the book.

Part of me wants to see this as a deliberate evasion. It wants me to read these moments — and there are many of them — as evidence of unreliable narration. That would indeed go a long way toward turning A Soul’s Calling into a work of art, as opposed to a collection of pages. But that part of me easily loses the war against another part of me: the one that read the book. Bishop’s inexplicable and unexplained forays into a spiritual justification for the trip are simply a baffling obstacle lost in the midst of so many other baffling obstacles, and it becomes an unintentional running joke that the narrator preemptively defends himself against the logical faculties of his audience, assuring us openly that these spiritual visitations — which occur when he’s in bed with his eyes closed — are not dreams. Why are they not dreams? Because they’re not dreams. That’s why. Well, that’s me told I guess.

Even if I could accept that “Scott” were the only hope for both this world and the spiritual world, and that his trip to and back from the base camp at Everest would somehow avoid The Biggest Apocalypse Ever, I absolutely cannot accept that, as a writer, Bishop so eagerly buries the lede.

If you were personally visited by spirits who told you that you needed to perform some earthly task in order to prevent the Alleged Cosmic Implosion of All That Ever Was and Will Be, and you did that thing, you’d then be pretty eager to tell everyone about it. Right? I know I would. But I also know that I’d spend a lot of my time talking about the spirits and the apocalypse, and probably wouldn’t spend nearly all of 340 pages methodically documenting that earthly task instead. And I suspect your narration would have a similar bent. “Scott,” on the other hand, waives away interest in the spirits, and thinks we’re more interested in how many times he stops for Pringles along the way to base camp.

The story here is that “Scott” was visited by ambassadors from another realm — a realm most human beings don’t even know exist — and assigned an urgent task that alone can avoid total intergalactic destruction…but Bishop thinks the story is that he took a difficult walk through the Himalayas. And I simply cannot abide that oversight. After all, that’s what prevents this from being a story, and restricts it to being instead a sloppily-framed and long-winded anecdote.

There are lots of other issues at play here, as well, including a massively problematic relationship at the book’s core. “Scott” and his guide Tej feud constantly on their way to Everest. To his credit, the narrator understands that this relationship is strained. To his much larger debit, he never realizes that the reason it’s strained is that he keeps arguing with Tej, childishly overriding his experienced council, and insisting that they do things “Scott’s” way. After all, Tej has only spent a lifetime physically guiding people along this exact route…and “Scott” has done several nights’ worth of reading on the Internet, so clearly he should be stubbornly disregarding everything his guide is so emphatically trying to tell him.

I was absolutely astounded by the way this played out between the narrator and Tej. All along I was expecting “Scott” to learn his lesson, but no, A Soul’s Calling wants us to believe that the moody American was right all along, and Tej was out of line for questioning him.

I’ve never seen anything like this. I kept expecting “Scott” to receive his comeuppance in some way and realize that the rich and beautiful world he’s so desperately trying to make conform to his expectations is actually the world he should be opening himself to. I find it hard to imagine a version of The Darjeeling Limited in which the Whitman brothers learn that it was smart of them to cling to their possessions and petty grievances, and I find it impossible to imagine that that would work at all as a film. When you fight against accepting another’s culture, the audiences laugh at you because they know better. When you stop resisting, the audience is on your side because you learned your lesson. In A Soul’s Calling however the opposite happens, and the audience is meant to be glad that “Scott” had the willpower to resist the foolish guidance of his (ahem…) guide. And I’ve never seen anything like that before. It genuinely hurt to read.

There’s more I could talk about at this point — such as the narrator’s explanation that every person who’s ever disliked him in life was actually being manipulated by evil spirits (which must be pretty nice, as everyone who’s ever disliked me in my life has done so because I was a dick to them in some way…you know, something that I’m actually responsible for as a human being and therefore must learn a lesson from) — but I think I’ve said enough.

A Soul’s Calling could have had some value, at least potentially, as a dry yet meticulous travelogue, but it ultimately fails there as well because the travel comes across as dead and routine. The narrator arrives somewhere, Tej tells him to go one way, the narrator throws a tantrum and goes another, the narrator gets exhausted, the narrator leans on a rock, the narrator tells us about something he read on the internet, and the narrator goes to sleep in a lodge. It’s just a simple, cyclical repetition of the same few ideas, with no substance or character at all, making this magical and important journey feel more like a boring car ride during which nobody feels like looking out the windows.

I’d like to read a version of A Soul’s Calling that makes something of its own components. I want to know what the spirits are talking about, exactly, rather than getting a spill of vague gibberish about them every one hundred pages or so. I want to see the narrator grapple with the possibility that the spirits aren’t real, and that he might actually be losing his grip on reality, just as any human being would. And most importantly, I want to see the narrator face some consequences for his behavior toward other people, without simply being able to handwave their disgust as being due to the interference of some invisible boogey man.

Because what we have isn’t a story. It’s a recitation of things that happen, yes, but it’s not a story. And it’s not a novel, and it’s not a memoir, and it’s not a travelogue. It’s a numbered collection of pages, and it’s waiting for somebody to give it shape. I hope somebody does; it’ll undoubtedly be for the better.

FTC Disclosure: I received a copy of this book in exchange for review. No money changed hands and all opinions presented here are my own.

On the eleventh day of Christmas, Zach Kaplan gave to us…

How the Grinch Stole Christmas!

Every nerd has something they collect. Some try to track down every issue of their favorite comic book, some relish rare video games, and others are simply satisfied with collecting themselves after a brutal de-pantsing. I collected the work of Dr. Seuss.

Growing up, my bookshelves were filled with all number of works by Seuss, both under his usual monicker and pseudonyms Theo LeSieg and Rosetta Stone. I had rare books like his risqué adult novel The Seven Lady Godivas, collections of his World War II-era comics and advertisements and a copy of his terrible movie, The 500 Fingers of Dr. T. My father would back-order out-of-print works for me, and my favorite place to visit was the book store. So, needless to say, How the Grinch Stole Christmas! was the only special that fully suited my youthful Christmas needs.

Like most of Seuss’s books, How the Grinch Stole Christmas! outlined an important message: Christmas doesn’t come from a store; it comes from the warm feelings of those we care about, and a sense of fun and togetherness. Christmas day is in our grasp, as long as we have hands to clasp (sorry, stump-o’s).

On its surface, it’s a sentiment that doesn’t look like much. Of course, with the wonderful rhyming patterns, made-up words like “chimbley” and winning illustrations, it wasn’t hard to make the message a more appealing one. But as a Seuss-o-phile, this resonated to me on a different level. Seuss’s stories were generally allegories for big, important things – Yertle the Turtle is Napoleon or Hitler, Horton Hears a Who is about the bombing and occupation of Japan (and dedicated to “My Great Friend, Mitsugi Nakamura of Kyoto, Japan”), The Butter Battle Book is about the Cold War. Why place the meaning of Christmas alongside such incisive analyses?

Religiously, I grew up in a household that none of my largely Christian schoolmates could fathom without a few questions. My mother was raised Episcopalian, but I don’t remember her ever being religious. My father is Jewish, but again, not very religious besides observing the high holy days and Hanukkah – though even the former practice began in my adolescence. Every year, we celebrated both Hanukkah and Christmas. I have fond memories of decorating our Christmas tree and lighting our menorah, illuminated as it was by an array of Christmas lights.

How the Grinch Stole Christmas!

I called myself a “reform Jew”, but I think all along I knew I was atheist. No matter how hard I tried to convince myself, I did not believe in God. Even without going to church every Sunday, God was assumed to exist by everyone around me – and, thus, that I believed as well. I sat by while friends called other friends “stupid” for not believing in Him before I was out of the atheist closet myself.

I was surrounded by Christianity in my suburban Texas town. Churches were everywhere. A girl that I liked was baffled by my disbelief in the miracles of Jesus. I uncomfortably sat through an assembly that was described as a talent show for teachers, where one instructor gave a brief but passionate Evangelical sermon. The Daily Show came to my hometown to interview members of a group who, in reaction to the building of a mosque, held pig races on Friday nights. A barbecue restaurant I drove past every day was in the news a few years ago for its refusal to take down a graphic image of an Iranian man being lynched. It wasn’t hard for me to develop some mixed feelings about religion, and subsequently about Christmas. Doctors told me that my heart was dangerously close to shrinking three sizes.

How the Grinch Stole Christmas!, the TV special, brought the wonderful world of Dr. Seuss straight to America’s sets every year, and that was a special thing for me. Without having something like that, I may have become a much more bitter person than I did. It brought the story to life, and it didn’t need Jim Carrey’s signature jumping and screaming to get it done.

It only expanded on the kernel of goodness that was the original novel, along with the memorable voice acting of Boris Karloff and the chasm-deep tones of singer Thurl Ravenscroft, also known for his famous portrayal of Tony the Tiger. It also gave color to the world of the Whos, whose existence in the book was originally limited to Seuss’s stylistic choice of only including the color red. For the budding literary geek I was, turns of phrase like “you’ve got termites in your smile,” “your heart’s a dead tomato splotched with moldy, purple spots” and “your soul is an appalling dump-heap overflowing with the most disgraceful assortment of deplorable rubbish imaginable, mangled-up in tangled-up knots,” stuck in my memory and inspired me to create fiction of my own.

How the Grinch Stole Christmas!

But let’s return to my original query – why would a Christmas special be written by Dr. Seuss, whose most accomplished pre-children’s work was his co-authorship of Design for Death, a 1947 Academy Award-winning documentary about World War II and the occupation of Japan? As a child, however, my reverence for Seuss assured me that I ought to trust him on this one, to enjoy Christmas in spite of my schoolmates’ bemused bafflement at what they considered a devastating personal flaw in me.

I was reminded to not get too annoyed by the constant barrage of carols every time I went to a store, and to remember that Christmas doesn’t have to be about religion – it can be about togetherness and love. And it reminded me that not everyone who had faith was the barbecue bigot down the street.

Today I fully identify as an atheist. And yet every year, my wife and I set up our Christmas tree, deck our halls and watch Christmas special after Christmas special. The Grinch may have tried to steal Christmas, but he gave me a very important gift – an understanding that even though the world isn’t perfect and that there will always be closed-minded people, Christmas should be a celebration of what we have in common, not a magnification of our differences.

Thank goodness I have hands to clasp.

Tomorrow: Spend Christmas Eve with Ebenezer. No, not that one.

The final season of The Office began last week, with the lowest-rated premiere the show’s ever had. Even lower than the premiere of the first season, which I’m pretty sure was only watched by people so that they could give it a voodoo curse. As far as season 9′s premiere? I think more people witnessed the birth of Christ. So I thought it would be fitting to look for the silver lining on the cloud of crap, and highlight each of the 10 times that the US version of the show succeeded in not being utter shit.

I know I’ll be accused of exaggerating here, but, honestly, I think I’m totally justified in saying that there were, in fact, ten distinct times that The Office rose above the level of “outright garbage” and succeeded in being “arguably watchable.” You may think I’m being too generous, but I think it’s quite fair.

So join me now as we look back at the ten times The Office managed to narrowly beat the odds, and become something that didn’t reflect poorly on viewers everywhere.

“The Fire,” Season 2, Episode 4

Why It’s Not Shit: Whenever anybody tells you Ryan is their favorite character, they’re unquestionably referring to the Ryan of the first few seasons. It didn’t take The Office long to undo what could have been their richest and most interesting character, reducing him to a generic hipster stereotype and robbing him of his complicated brilliance. This episode sees the Ryan and Michael dynamic at its best, with a truly well-handled and ever-shifting sense of power: first Michael attempts to mentor him, then ridicules him for the vast knowledge he already has, then humbly appeals for guidance himself, and finally, with irrelevant triumph, puts Ryan back in place by taunting him about a small fire he accidentally started. It’s a great, real, character-driven story that shows these two characters being the flawed — often awful — human beings they are, without resorting to caricature or cartooniness.

Why It’s Actually Still Kind of Shit: Jim leads the rest of the office in a few time-killing games during the evacuation. That’s fine, but one of them is the rather baldly intentional “Who Would You Do?” The rest of the desert-island exercises are fun, but openly asking “yo who do you want to stick your genitals in” to coworkers he barely knows comes off as perverse, and a bit revolting. Additionally, it’s odd that Kevin gets yelled at for saying “Pam” before Jim finishes telling everyone how the game is played. This makes it seem as though Kevin behaved inappropriately, which is funny, but ultimately, no, that pretty much is how the game is played…so it’s puzzling that his response was treated with disgust, as though anyone else’s later responses shouldn’t be.

Ending on a High Note: A great, early character study showing Ryan and Michael both behaving like actual people, and Dwight showing real — not overtly manufactured and instantly undone — weakness. Enjoy it while you can.

“Take Your Daughter To Work Day,” Season 2, Episode 18

Why It’s Not Shit: It’s not exactly an episode that weaves several plotlines together, but its central conceit of introducing children to the office gives nearly everyone at least one great moment, and it also provides a good example of how to sketch out the personal lives of these characters without OH I DONT KNOW SENDING THE WHOLE OFFICE TO THEIR HOUSE FOR SOME SOCIAL FUNCTION NONE OF THEM WOULD ACTUALLY GIVE A SHIT ABOUT. We also see Michael at his most vulnerable, Pam displaying a humanizing (as opposed to irritating) kind of neediness, and Stanley yelling at Ryan…which is indeed genuinely scary.

Why It’s Actually Still Kind of Shit: Everything about Michael’s appearance on the children’s show works fine, until the writers seem to think we need everyone in the room to decide for us what it means. The short moment between young Michael and the puppet should be an act of devastating restraint, but instead it’s followed up by variations on “Hey, that thing you wanted is something you never got, huh?” A little too on-the-nose, and it hurts the moment substantially. Also, it ends with Michael and Dwight singing “Teach Your Children,” which works within the episode but lays the groundwork for every future episode in which the employees sing and dance for no fucking reason whatsoever, and otherwise remind you that the show was never as good as you thought it was.

Ending on a High Note: The interactions between Michael and Toby’s daughter are a series highlight, and this is a great way to give so many characters a fun spotlight without it feeling like the isolated sketch comedy of season eight.

“Grief Counseling,” Season 3, Episode 4

Why It’s Not Shit: The death of Michael’s old boss is met by the rest of the office with a notable lack of emotion, but an opportunity to discuss, explore, and accept death comes in the form of an unfortunate bird who flies into the glass doors downstairs. “Grief Counseling” is a strange episode that manages to be sombre without losing sight of the comedy, and manages to be funny without sacrificing some genuine insight into the human condition. It’s certainly a chance to explore Michael, whose emotional responses drive the action of the entire episode, but it’s also a fine showcase for Pam, who plays into Michael’s depressive fantasies by designing a respectful casket for the bird, and delivering a monologue to her hurting boss under the guise of eulogy.

Why It’s Actually Still Kind of Shit: MEANWHILE JIM CALLS SOME PEOPLE TO FIND POTATO CHIPS IN THE LEAST RIVETING SUBPLOT THIS SIDE OF TOBY DANCES FOR COOKIES.

Ending on a High Note: The meeting in which Pam, Ryan and Kevin relay the plots of popular movies rather than share their own stories of death is an all-time great. Also, the conclusion of this episode has a great payoff in “The Return,” when Oscar asks about Dwight and Creed replies, “You didn’t hear? Decapitated. Whole big thing. We had a funeral for a bird.”

“Traveling Salesmen,” Season 3, Episode 13

Why It’s Not Shit: Episodes that pair up characters in interesting ways and give them each a chance to shine, in the case of pretty much any show, tend to be quite good. During season 3 of The Office, the writers still remembered how to do that in a way that was organic to the situation, and realistic in terms of the work environment. While the sales calls themselves are brief we learn a lot about how these people operate day to day, while the cameras are off. We see normally suave Ryan falter, learn that the obstinate Stanley has actually built up a valuable network of business relationships, and we see newcomer Andy scheme his way to success, despite demonstrating a complete lack of aptitude. This was back when Andy alternated between conniving and frightening…two very interesting modes for the character that the show has abandoned in favor of making him sing all the God damned time.

Why It’s Actually Still Kind of Shit: The Phyllis / Karen sales call is really just an excuse for a sight gag, and Angela’s glower during Andy’s final talking head is a bit obvious. But, to be honest, those are minor complaints, and this is a pretty great half hour of television.

Ending on a High Note: The entire thing is a high note, catching the office (and The Office) in a state of flux. New characters have been introduced, and the show is shaking up and developing existing relationships. These are both trends that would continue, but with conclusively diminishing returns. For now, the rewards are great.

“The Return,” Season 3, Episode 14

Why It’s Not Shit: “The Return” sees multiple plotlines — and ongoing dynamics — pay off in a single episode: Oscar’s “vacation,” Dwight’s resignation, Angela and Dwight’s relationship, Jim and Karen’s relationship, Jim and Pam’s flirtation, Andy’s angling for promotion, the dickishness of Jim’s pranks, and Andy’s anger issues. It’s a simple episode in which not much happens, but relationships are changed and characters are further defined. It’s a watershed episode in a show that at the time cared about what it meant when its characters said and did things, and Andy punching the wall is still as shocking a moment now as it was six years ago…only now it’s shocking because we’ve spent so much time with him as a defeated doormat that it no longer seems feasible.

Why It’s Actually Still Kind of Shit: The party for Oscar and Dwight is a collection of unnecessary visual gags (Meredith in a mustache, Phyllis shaking her breasts around), but the amount of wasted time in this episode can be measured in seconds, and that’s all we can really ask.

Ending on a High Note: It’s about time there was a consequence for Jim’s immaturity, even if he’s not the one facing that consequence. Andy would return, emasculated, but we do get one truly brilliant moment with him before he’s changed forever, as he intends to apply his upwardly-mobile aggressiveness to anger management training itself, intending to complete it in half the allotted time.

“Product Recall,” Season 3, Episode 21

Why It’s Not Shit: The list of Office characters that haven’t become overplayed through the years is a short one, certainly, but Creed manages somehow to be both a continuing highlight, and consistent in his characterization. “Product Recall” is the closest thing we’ve ever had to a Creed episode, and even here he’s used sparingly. His off-camera shirking of his job responsibilities drives the plot, and he only really pops up to descend — beautifully — rung by rung into the levels of despicability. It’s a great and fittingly dark episode from an era in which the writers didn’t feel the need to soften blows and humanize monstrous behavior. We also get a great Andy and Jim pairing, and probably the only genuinely funny prank on Dwight, with Jim imitating his nemesis…and then receiving some payback in kind at the end of the episode. “Product Recall” took a lot of things that The Office so frequently got wrong, and then did them right.

Why It’s Actually Still Kind of Shit: A Kelly subplot is never a good sign, but this one has a great moment of Oscar / Kevin bonding that more than redeems it. It’s disappointing that the cartoons look nothing like Mickey Mouse and Donald Duck, and Andy pining for a high school student is beyond creepy, but there’s enough great stuff here to warrant its inclusion, right down to the perfectly awful moment at the end, when Creed pockets the money he collected for the woman he got fired.

Ending on a High Note: Michael’s apology video may go literally nowhere, but it’s nice to see a crisis situation in this show that isn’t resolved by the staff hoisting him onto their shoulders and singing “We Shall Overcome.”

“Dinner Party,” Season 4, Episode 13

Why It’s Not Shit: It’s all kinds of not-shit up in here. If I were to single out just one episode of The Office to be spared from a nuclear blast, and I do look forward to that day that I am put in such a position, this would be the one. It’s brilliantly acted, terrifyingly raw, and unrelentingly dark. What’s more, it gives the audience credit. While some of the Jan / Michael bickering is a bit heavy handed, we’re left with a lot of blanks to fill in on our own, and even the talking-head moments don’t bother to hammer home the obvious…they’re legitimately funny, perhaps due to the genuinely unsettling atmosphere of Michael’s desperate dinner party. There’s a real feeling of entrapment and helplessness there, and none of the characters involved know quite how to act. It’s true to life and it’s human, even down to the surprisingly moving climax that silently follows each of the characters home for the night. Until this entry, we haven’t had any episodes on this list that feature the staff leaving the office for anything other than work-related (ie: understandable) reasons. Dinner with the boss, however, is a situation both rooted enough in reality to work, and rife enough with awkwardness to make horrifying. The cameras follow the staff for good reason here…not like when they decide to have a charity run for rabies, or Michael gets lost in his hometown (huh?). Like “Product Recall,” it’s an episode that takes a lot of the ingredients of the show at its worst, and reassembles them into a thing of beauty.

Why It’s Actually Still Kind of Shit: Michael ran through a sliding glass door because he thought he heard the ice cream man. For that tiny detail, he must have shifted from well-intentioned-but-a-bit-dumb to Benjy Compson levels of retardation. Also, Jan’s character change (competent executive to raving lunatic) lays the groundwork for all too many other characters to do the same thing…with severely diminishing returns.

Ending on a High Note: Almost nothing but great lines in this one, though the standout goes to asskissing Andy, when Michael half-heartedly asks him and Jim if they’d like to think about investing $10,000 in Jan’s home-made candle business. “Thought about it. I’m in.”

“Prince Family Paper,” Season 5, Episode 13

Why It’s Not Shit: As many of the episodes on this list are turning out to be, this one is a great character showcase: in this case, Dwight. The show doesn’t always know what to do with Dwight. He’s a psychotically-devoted businessman, an ignorant farmboy, a sensitive romantic, a violent maniac, a playful child, a sycophant and a flailing comic boob, cycling through those roles as any particular script dictates. In this case, he’s firmly in the first category, and that’s good, because that’s what should drive him as a character. In “Prince Family Paper” he pairs up with Michael for some reconnaissance work at a small rival firm. What they find there, though, is a small family running an honest business, more interested in securing their own futures than in taking down the competition. Michael, of course, goes soft when the family extends the sort of human kindness to him that he wishes he could always expect from others. Dwight, however, has a different view. “It’s not personal,” he says, and as callous as he is he has a point. “It’s business.” This is why Dwight is the most successful salesman. This is why Dwight is so devoted to his work. This is why Dwight is almost always capable of being a more interesting character than he usually gets to be. He will sink a family as long as it’s business, just as quickly as Michael would spare one in spite of it being business. It’s a great and appropriately heavy episode which more than earns its bittersweet resolution.

Why It’s Actually Still Kind of Shit: Unfortunately around a third of the episode is given over to a pointless and unfunny office debate about whether or not Hillary Swank is hot. It’s garbage. Fuckin’ trust me.

Ending on a High Note: While the episode would have been far better as a Dwight / Michael adventure with little or no input from the rest of the staff, the A plot is more than strong enough to carry the episode. Also, Michael’s “bittersweet” speech at the end of the episode is one of the only times the show truly nailed the mix of comedy and pathos that should end an episode like this.

“Dream Team,” Season 5, Episode 22

Why It’s Not Shit: The Michael Scott Paper Company arc is not only the last truly great thing the show ever did, it’s arguably the single best thing the show ever did. New boss Charles Miner lends such an air of uncomfortable change to the familiar surroundings that pretty much any arc that sprung from it would have been welcome. But Michael crashing hard against reality when he tries to start his own rival paper company is both a perfect fit for the character, and an excellent way to ground a show that was already becoming a bit cartoony. “Dream Team” may or may not be the best episode of the arc — it’s hard to say, because this particular storyline is more heavily serialized than anything else — but it’s a great distillation and exploration both of Michael’s tendency to dream too big, and why one needs to feel satisfied in his or her own life. Everything from Michael’s panicky overcooking of French toast for breakfast to Ryan stealing shoes from a bowling alley to Nana’s lucid refusal to invest in the company fills in the blanks in such a way the The Office really should have been doing since day one. And Pam’s emotional collapse toward the end of the episode leads to a genuinely moving conversation between herself and Michael. It’s a mixed moral — the fact that she quit her job is never quite presented as a good decision — but it feels like its own kind of happy ending. After all, if we have to go down, we might as well go down together.

Why It’s Actually Still Kind of Shit: Ryan popping up for this arc makes perfect sense. Ryan sticking around after this arc makes no motherfucking sense whatsoever.

Ending on a High Note: Charles Miner installing Dwight as his number two, making Kevin the receptionist and keeping Jim at arm’s length makes for some great character comedy, as our perspective is tweaked just enough to make familiar situations feel fresh. Also, the fact that Pam ultimately returns to the company as a salesperson leaves the reception desk wide open for the last great character the show ever created: the infectiously bubbly and adorably daft Erin.

“Counseling,” Season 7, Episode 2


Why It’s Not Shit: Toby’s role in the show as Michael’s foil so rarely got a chance to shine, as Michael was always fast to dismiss him cruelly and Toby — we see clearly — was fast to believe he deserved such dismissal. In this episode, however, Michael is forced to undergo a marathon six-hour counseling session with his nemesis, and it results in probably the last truly interesting character interaction this show’s had. Michael cycles through refusal, fabrication, anger, abuse, and finally acceptance in a script that feels like it could have been written for a two-man stage show. Toby never quite gets a handle on the situation the way he wishes he did, but he means well, and even has a genuine moment of breakthrough with Michael…though, of course, once Michael’s aware that he’s opening up to Toby, he shuts it down immediately, and storms out of the session. It’s a way for both characters to have a mutually-fulfilling experience, without sacrificing the inexplicable one-sided hatred that’s fueled the dynamic between these characters all along. In the end, they bond briefly over the uselessness of Gabe in a conversation that would seem at least slightly meta, if the writers could be counted on to realize that these two are right, and there’s really no reason for that guy’s continuing presence. Oh well, at least he dressed as Lady Gaga in the Halloween episode and oh boy was that fucking funny my God this show sucks.

Why It’s Actually Still Kind of Shit: Dwight’s Pretty Woman subplot genuinely feels like a rejected idea from Everybody Loves Raymond. It’s absolutely terrible, and probably a pretty good indicator of what a Dwight Schrute-centered sitcom would look like. THANK GOD NOBODY’S DOING THAT RIGHT. The better subplot revolves around Pam bluffing her way to Office Administrator. Why they felt they needed the Dwight garbage when they already had plenty of stuff going on in this episode is beyond me.

Ending on a High Note: Dwight’s idea for a daycare center in the building is kind of worthless, but I do like the sight-gag of an Insane Clown Posse poster on the wall, with “Insane” and “Posse” crossed out. It’d be a lot funnier if the camera didn’t obnoxiously zoom in the make sure we got the joke but what can you do.

Were there any other episodes that weren’t shit? If not, let me know in the comments below. And also you’re wrong.

It’s not uncommon for a television comedy to lose steam as the years go by. Sometimes it finds a second wind, and usually it does not. There’s nothing remarkable about the fact the The IT Crowd went from critical darling to such a mess that creator Graham Linehan chose to pull the plug rather than drag it on any further. What is remarkable is that it only took 24 episodes to get from that dizzying high to a show-killing low.

I rewatched the fourth and final series recently, and was struck all over again by how lifeless and dull it felt. It’s nothing to do with the performances as the cast makes the best of what they’re given, and any laughs that we do get come from an effective delivery rather than any particular cleverness in the line…there just seems to be a sloppier approach to the comedy, and perhaps an ultimately-destructive assumption — however correct — that the cast could be relied upon to make up for any shortcomings in the writing.

Nowhere is this more apparent than in the series’ de-facto finale, “Reynholm vs Reynholm,” which takes ostensibly humorous detours into a silly restaurant. Series one’s “Fifty-Fifty” did the same thing, and I thought it might be interesting to focus only on those detours, and discuss their levels of success.

The Setup

In “Fifty-Fifty” the setup is simple, and completely organic to the plot. (Or, in this case, and in notable contrast to “Renholm vs Renholm,” the plots.) Specifically, a restaurant is recommended by Moss, separately, to both Jen and Roy.

Jen is looking for a nice restaurant in order to make amends for lying about having specialized knowledge of classical music — a lie which leads her romantic interest to use her as his Phone-A-Friend when he appears on Who Wants to Be a Millionaire? — and which, of course, causes him to lose.

Roy is looking for an edgy restaurant with a tough atmosphere, because he has a date with a girl he met online, during an experiment he was conducting to see if women are actually more attracted to men that treat them poorly. He creates an antagonistic and disinterested persona, and is looking for a restaurant that will make him seem even tougher for hanging out there.

The restaurant Moss recommends to each is called Mesijos…or, at least, that’s how Moss pronounces it. Here, the visit to the comedy restaurant comes late in the episode, well into the third act, and it’s organic to the twin plots we’ve been following all along.

In “Renholm vs Renholm,” there is no plot by the time we get to the restaurant, because barring a brief introductory scene during which Douglas discusses his ex-wife and is then immediately accosted by his ex-wife, we’re dumped right into it.

This, in itself, is not a problem. There is no requirement, unspoken or otherwise, that every location the characters visit must be fully and completely justified by a logical progression of the script. That being said, there is some sense of satisfaction when that visit is justified, and arises naturally out of the story we are being told…especially when compared to “Renholm vs Renholm,” which has a character we’ve never seen before barging through a door, Matt Berry making a funny face, and then an immediate and unexplained teleportation to a new setting.

When we arrive at the restaurant in “Fifty-Fifty” it’s less abrupt. We know where these characters are going, we know why they’re going, and we know what they hope to accomplish by going. With such narrative groundwork laid, we get an immediate laugh when we see the restaurant for the first time, as in the screenshot above. It’s neither conducive to Jen’s apologetic dinner nor Roy’s attempt at passing himself off as a cold-hearted bastard.

But what’s more, it’s not an unfair subversion. What’s happening here to Jen and Roy is not just a comedy writer putting his characters through hell, it’s absolutely true to what we know about Moss, who recommended the restaurant…more on which later. Suffice it to say that this choice of restaurant — and therefore the episode’s reasons for taking us there — is a natural outgrowth of the story we’ve been following. It’s a bad decision for the characters, but a sound one for the writer.

“Renholm vs Renholm” dumps us into this comedy location for no narrative purpose whatsoever. It simply wants us to laugh.

What’s so bad about that in a comedy program? Nothing; it’s a great impulse. Where this scene falters (or these scenes falter, rather, as we pay not one but three visits to this restaurant) is the fact that it’s not really funny.

In “Fifty-Fifty” we cut from measured conversations about where to go for dinner to a loud, frantic, busy scene that’s immediately funny out of sheer contrast, and continually funny because the madness only ratchets up from there. In “Renholm vs Renholm” we cut from Douglas having one measured conversation about his ex-wife to…Douglas having another measured conversation about his ex-wife.

There’s no contrast. As you can tell from the screen grabs, there’s no shock here. One neutral colored room to another, one woman to another, with Douglas reacting in no particularly humorous way to either conversation, unless you count each of the times the script wants him to make bug eyes.

There’s no reason for Jen and Roy to go to that restaurant in “Fifty-Fifty,” so the script makes sure it creates a reason. There’s no reason for Douglas and Victoria to go to this restaurant in “Renholm vs Renholm,” so the script doesn’t bother discussing it and just hopes we won’t notice. There’s a huge gulf in writing quality there.

The Joke

The joke in “Fifty-Fifty” is evident from the first frame, seen above. Moss has mispronounced “Messy Joe’s,” and both Jen and Roy are stuck on their respective dates in a wholly inappropriate restaurant.

This steadfast mispronunciation is in-line with Moss’s character — he’s similarly misguided when it comes to pronouncing the word “tapas” — and the fact that he both enjoyed himself at this restaurant and doesn’t see that it wouldn’t be appropriate for his friends’ needs suits him as well. Moss is severely lacking in social skills, and his perception of the world around him occurs through psychological filters that the rest of humanity simply does not have.

The sign in itself makes for a great joke without need for comment, and the snap-cut to the madness inside reinforces just how ludicrous the scene is…and yet, it’s not an inherently funny place. There are families there enjoying themselves, after all. The restaurant in itself isn’t a joke…the situation is the joke. Many background characters are perfectly content with their visit to Messy Joe’s. What makes it funny is that the foreground characters are not, and that’s an important distinction to make. The comedy comes from the contrast, not from the fact that Messy Joe’s exists at all.

In “Reynholm vs Reynholm,” however, we find ourselves at the other end of the spectrum. Again, we find ourselves oriented by a still frame of the sign, but if anyone can tell me how “The Flappy Duck” works as anything other than a limp — ahem — dick joke, please do so.

Messy Joe’s manages to function as a series of jokes immediately. The name of the restaurant borne of a mispronunciation, the logo giving away the type of establishment it is, and then the immediate cut to the clowns and screaming children.

The Flappy Duck on the other hand doesn’t get a logo. Neither the sign nor the building have any character whatsoever. It’s a phrase that I guess somebody might chuckle at, somewhere, but The Flappy Duck as a name has nothing to do with the restaurant itself, which appears to be a riff upon trendy establishments with non-traditional dining experiences.

Perhaps, then, The Flappy Duck could use some more personality in its set construction, because the joke doesn’t land. The wine looks like milk, which could lead to some kind of joke, but instead we’re just meant to laugh at the fact that it doesn’t look like wine. That’s not effective comedy, that’s not something that says anything about the characters, and it’s not even a joke with a clear target. I suppose I could hand you a cracker and say “Please hold my shoe,” if I really wanted to, but I don’t suppose anybody would be singing the praises of my wit afterward.

In the first scene at The Flappy Duck, Douglas is eating what looks like a small radio and Victoria has a piece of somebody’s lawn on her plate. Only it’s just sitting there. The actors don’t engage with it, they don’t comment on it, and they don’t see anything strange about it. Whereas the Messy Joe’s debacle was a conflict borne entirely of — and heightened satisfyingly by — immense contrast, The Flappy Duck just has people talking quietly about not-particularly-funny topics while not-particularly-funny things sit baldly and blandly on their plates.

That might work in a Spot the Difference puzzle in the Sunday paper, but it doesn’t make for a particularly well-constructed scene in a sitcom.

“Fifty-Fifty” keeps the jokes coming by simply highlighting how uncomfortable the characters are. Most great comedy is on some level generated from somebody’s discomfort, and that’s why the visit to Messy Joe’s is funny. Having Douglas and Victoria — and later Jen and Victoria — sit comfortably at ease with whatever minor absurdities may be sitting on their plates isn’t funny. That’s a lesson that The Simpsons seems to have forgotten as well; when the family doesn’t fit in, it’s funny. When the family not only fits in but qualifies as global celebrities with people of great fame and power at their beck and call, it’s not.

Jen is here in order to apologize to the man whose chance at fortune she ruined with her lies. All around them balloons pop, children bleat and sparklers fizz. These two characters don’t need to tell jokes, because — all at once — they are the jokes. The world has turned and left them in a position of ridicule. They became, ironically, the most ridiculous thing in Messy Joe’s.

Ditto Roy. His ill-conceived bid at being taken for a tough guy may have been destined to fail, but by meeting his date in this environment it’s already unraveled before it even gets started. When a child next to him dances around with his shirt over his head, Roy needs to call a clown in to keep the peace. When a waitress hands him his milkshake, he too politely thanks her for it. These are jokes that come from characterization, and ones that rise organically from tight and skillfull writing. This scene didn’t need to be set at Messy Joe’s in particular, but what Linehan managed to do was graft one great and escalating joke onto a situation that was already funny in itself. In short, he took a good thing and made it better.

At The Flappy Duck, he’s making it worse. Bored, perhaps, of the aimlessness of this dinner, he has Victoria rise and address the camera like a character in a soap operas. Of course, the other diners wonder what she’s doing, and that in itself is a pretty good joke. It’s oversold here by having Victoria engage with the other customers and ask what they’re eating — drawing attention to an absurdity that she should probably not be aware of in order for the joke to work — but it’s something.

It’s also, however, not related to the setting at all. Whereas the Messy Joe’s stuff could have taken place elsewhere, it’s funnier because of where it’s set. The Flappy Duck material could still keep us in Douglas’ office, and work no less well for it. In fact, it might work better, as our presence at The Flappy Duck adds only confusion to the scene, as we keep waiting for a payoff that never comes.

Douglas does have one line — announcing the arrival of their invisible desserts — that makes a token stab at tying the action into the set they’re sitting on and probably wondering why anyone bothered to build, but true to the slapdash feel of the script nobody comments on this, and it lies there like a non-sequitur. It’s a singular attempt, at last, to find some comedy in The Flappy Duck, and nobody cares enough to see it through.

It’s not that the Flappy Duck sequence(s) couldn’t be funny, it’s that the writing isn’t working to make it funny. The attempted punchline here is that Douglas introduces the head chef to his wife while she jacks him off under the table with her foot. It’s a chance for Matt Berry to make yet another funny face but it would unquestionably be more interesting to watch if they gave that face something funny to say. Which leads us to the biggest issue…

The Writing

The distance between these two examples in terms of writing quality is staggering. Despite both episodes being penned by Linehan, “Fifty-Fifty” seems to have an innate understanding of why its ideas are funny, and it exploits that knowledge to mine the comedy more deeply, efficiently, and effectively. “Reynholm vs Reynholm” doesn’t seem to know why it’s supposed to be funny, and it relies on the actors to sell an idea that feels like it was never fully conceived before the episode was shot.

At Messy Joe’s, the jokes don’t stop after the initial reveal. Rather we move logically along the comedy scale, compounding the situation until it hits its breaking point. From the initial reveal to Jen sitting apologetically across from her date to a mariachi band attempting to serenade them to a clown pointing and laughing at the loser who blew his shot on Millionaire, every moment feels like a step forward for the plot, for the characters, and for the comedy.

“Reynholm vs Reynholm” spins its wheels without any clear destination in mind. Its singular plot is about the reappearance of Douglas’ ex-wife, whom he remarries and then wishes again to divorce. For no reason whatsoever, they discuss this at The Flappy Duck. For even less of a reason, Jen also meets Victoria there to deliver the news that Douglas wants a divorce. And then for no reason whatsoever, the four main characters gather at the end of the show to drink milky wine and celebrate the fact that they limped to the end of the episode and never have to film scenes for it again.

“Reynholm vs Reynholm” flails wildly for something to cling to, with references to past episodes being tossed out in the hopes that they’ll get a chuckle out of recognition and the long-overdue return of Richmond, but these last-ditch acrobatics are unsuccessful in distracting us from the fact that this is an episode about a character we’ve never met, which doesn’t seem to have any real stakes for the show nor any basis in reality, and which is resolved in a deliberately unsatisfying manner.

Far be it from me to suggest that we have to care about the characters in order for the jokes to land, but I do think that the show has to at least pretend that it thinks we care, and by this point Linehan no longer feels interested in that.

Nobody at home will ever be moved to tears by the plight of Moss and Roy — let alone Douglas — but the show needs to at least keep up the illusion that somebody might. That’s the only way it can successfully generate comedy from the awkward situations in which these characters find themselves. Admit that we shouldn’t care and disbelief is shattered: we suddenly don’t care about them, and we’re going to wonder why we’re watching.

“Fifty-Fifty” works because it maintains the illusion that these events mean something. When Roy is frustrated by women and attempts to demonstrate how shallow they are with his experiment, it means something. When he becomes sucked into that experiment himself and tries to date the woman who fell for him, that means something too. When Jen lies about having a knowledge of classical music because she wants to impress a handsome stranger, that means something. When she disappoints him and reveals the truth, that also means something.

It all builds toward a climactic clown beating that sees Roy’s date falling for Jen’s date, demonstrating that — in this case at least — Roy’s hypothesis was correct, and Jen’s paid the price for her falsehood.

This isn’t destiny that brought these plot strands together. This isn’t fate, isn’t luck, isn’t karma. It’s writing. And it’s the work of a writer in command of his craft.

By “Reynholm vs Reynholm,” that sort of command is no longer felt. Episodes feel like strings of set-pieces and unrelated moments. Some of them get laughs, some of them do not. That much is common in sitcoms. But that’s exactly why we need a thread to cling to…something to follow along. Some gesture on behalf of the show that says, “If you’d like to care about this, or even pretend to, for just half an hour, we’ll make it worth your time.”

When “Reynholm vs Reynholm” dumps us time and again into the humorless Flappy Duck, it’s an act of narrative desperation. There’s nothing Linehan can think to do with the main cast or setting, so we’re transported to this new location with a new character in the vague hope that, somehow, it will pay off.

But it never does. And when Victoria eats a knife even though they aren’t edible, it’s as though Linehan forgot that he already made that joke earlier with Douglas and the menu. It’s not a callback, it’s not a fulfillment of foreshadowing, it’s not thematic resonance. It’s desperation…or at least that’s what it feels like.

There’s something to be said for going out on top. With The IT Crowd, Linehan didn’t do that. But by choosing to end it before he dug too deeply into mediocrity, he did the next best thing.

It would have been nice to have a fourth (and fifth, and sixth) great series, but that wasn’t in the cards.

Oh well. We’ll always have Mesijos.

When I was a little boy, I loved Jim Henson.

I didn’t just like him. I didn’t just enjoy his work. I loved the man.

He was probably the first person I knew as an artist behind the material he produced. Certainly I enjoyed other TV shows, and songs and films, but I always saw them in isolation. As products distinct from whatever anonymous forces breathed life into them.

Not so with Henson’s work. I don’t know why that is, but I knew his name. I knew what he looked like. I know not only that there was a human being out there bringing all of this wonderful stuff to life, but I knew who it was. He was the first artist I knew as an artist, and that’s either a cause or symptom of how important his work was to me.

He was also a less exciting first for me: his was the first death that hit me personally…and it hit me hard.

I guess I was fortunate that, by nine years old, I hadn’t had a family member die. Or a close friend. Or a beloved pet. But when Jim Henson died, it felt like I was losing all of those things at once.

I was devastated. If I choose to look back to that news, I find I’m still devastated.

Losing a friend is tragic because that friend isn’t there anymore. There is now a hole in your life where somebody you cared about used to be. It’s not easy, and shouldn’t be easy, to move forward from there. The world has changed, and one special person is no longer there.

When Henson died, though, the world didn’t just lose one special person; it lost an entire, powerful, selfless, incomparable creative force. A man who conjured up so much magic and wonder from nothing. A man who could make you laugh or cry with a piece of felt, and — what’s more — make you fall to your knees in sorrow when he’s no longer around to carry that felt.

Partway through The Crying of Lot 49, the protagonist takes out a notebook and writes to herself, “Shall I project a world?”

That’s a line I keep returning to in regards to Henson. From his lone, singular, gifted vantage point, he projected a world. In fact, he projected three worlds. Sesame Street. Fraggle Rock. The Muppet Theater. He seemed bottomless in his capacity for invention. He willed entire universes full of unique, rich and complex individuals to life. He treated them with love and respect by handing them off to great writers and even better performers. Henson’s vision was a serious one, even when it was silly. It was a life-affirming one, even when it was breaking your heart.

To this day I think it was Henson that inspired me to create. After all, what Henson did with cloth and plastic is what any artist should be doing all the time. Whether it’s words, or sounds, or colors, or anything else that brings you joy, an artist takes these small, insignificant things and assembles them into something life-changing. Henson and his team may have been constructing their characters from common materials, but when you look at Kermit the Frog you don’t see green felt and ping-pong ball eyes. You see Kermit the Frog. That’s because Henson was a success as an artist. He used small, insignificant things to build characters we not only believed in, but with whom we wanted to share our lives.

When I write, I try to do the same thing with words. If could ever be fortunate enough to create anything as rich or important as Kermit the Frog, I’d probably die of shock. Henson created characters that rich and important routinely. It really was some kind of magic, and it’s a magic that died with him, that the world lost, and that I lost at the age of nine.

By that point I was probably a bit too old for Sesame Street, and so I could have moved my affection over to reruns of The Muppet Show, or Fraggle Rock. But I found that I preferred Sesame Street in some way that I couldn’t understand then, even though I understand now: it was longer. Each episode was an hour compared to the half-hours of its sister programs. And that’s why I preferred it: it wasn’t that I wanted to watch these characters; I wanted to spend time with them.

I wanted to be part of that world of Henson’s. Be privy to that vision. Be able to touch, and feel, and interact.

I wanted the promise of his work to come true. I wanted to live in a world in which I could sit on a bench in the park and look over to see that I was sitting next to Kermit. A world in which I could look up into the sky and see Gonzo floating away with his balloons. A world in which I could see Fozzie’s act go poorly on stage, but then find him later and make his day by telling him I enjoyed it.

I don’t know. Maybe my particular childhood cried out for escapism more than others. Whatever it was, the Muppets helped me through some really difficult times, be sheer virtue of their existence. They taught me that magic was real, only it was called creativity. And with it, you really could change the world.

Jerry Nelson’s death isn’t like Jim Henson’s or Richard Hunt’s, because Jerry Nelson lived a long and full life. He was faced with an impossible legacy to carry on…and yet he carried it on anyway. (That’s another kind of magic.) I’m not sad because an old man has laid down to rest, but simply that one of the last threads connecting me to my childhood, to my early sense of wonder, to three distinct and safe places I was always allowed to visit when I needed an escape, has disappeared.

Up to the very end Jerry was an enormously talented man. He may not have had a Kermit or a Fozzie or a Gonzo or a Scooter…but he had a Gobo. And a Robin. And a Count von Count. And a blue businessman destined always to be disappointed by Grover. He had characters that could fill out these worlds, and make them more real. Everybody who worked on those shows did me — and countless other children, and adults — a service for which they can sincerely never be repaid.

The fact that my sadness at the passing of Jerry Nelson leads me to think about the larger universes Henson created isn’t meant to be a slight at Jerry…but rather a loving acknowledgement of what larger, unforgettable, culture-defining things he helped bring to life.

There’s no shame in being remembered as part of a team. And there’s probably no team more impressive to have been a part of.

Thank you Jerry. Sincerely, thank you.

So Breaking Bad starts up again tonight. Don’t worry; I have something else planned tomorrow by way of celebration. But for now, with the inescapable commercials, and online advertisements, and interviews and so on, it’s got me thinking about spoilers.

My girlfriend and I are at the end of season two. Tonight, season five begins. We’ve got a lot of catching up to do, and we’re getting there…but we’re enjoying the ride and don’t feel too much of a need to rush. Yet whenever we see some kind of promotional material for the show, we want to look away, stop listening, change the channel…all for fear of spoilers.

And I’m not really sure why. I’ve always maintained — and still maintain — that spoilers shouldn’t matter. If the quality of the piece of art in question is high enough (and for Breaking Bad I’d absolutely say it is) then it shouldn’t matter if you know what’s coming. The pleasure shouldn’t be found in an endless succession of surprises. The pleasure should come from the journey. From the many components that come together to create an engrossing experience.

Anyone can shock us. Anyone can jump up and yell boo. That can be a type of pleasure, but it’s not the only type of pleasure. Perhaps if we’re speaking about a summer blockbuster that has no ambition beyond thrilling us with pyrotechnics, spoilers could pull the rug out from under that film’s only trick. But if the acting is good, if the writing is solid, and if the directing is pulling everything together in the right way, then why shouldn’t that be enough?

Recently I was on a forum, and somebody made a comment about something and said, “It’s like the end of Psycho,” by way of humorous comparison. (It wasn’t actually very humorous, but there you go.) A second poster replied, “I haven’t seen Psycho, what happens?” And then the first told him to sign off immediately and go watch it.

Nothing wrong with that, but he justified this by saying something to the effect of, “Go watch it before you get spoiled. You’re very lucky if you don’t know the ending, so go watch it so you can experience it the right way.”

That’s troublesome to me on several levels. First, and less importantly, the ending was already spoiled in the thread by making that comparison in the first place. Shouting out “Go watch it now before you have the twist spoiled for you!” will keep him on guard for that twist, and that’s just as bad as — if not worse than — knowing what’s coming.

But secondly, it suggests that Psycho isn’t worth watching — or isn’t as worth watching — if you know what’s coming.

And, I’m sorry, but that’s bunk.

I knew the ending of Psycho well before I ever saw it. It may have even been the first thing I knew about it. Yet when I finally sat down to watch the film, I was absolutely ensnared by Hitchcock’s chilling masterpiece. It had nothing to do with not knowing what was coming next…it had to do with the film being a genuine masterwork by a man who knew what he was doing.

By now, most people know the dark secret of Norman Bates. I truly doubt, however, that it interferes with their ability to enjoy that film. If it does, then I can only concede that they must be watching films the wrong way. There’s really no other way to argue it.

When Kate and I were standing in line to see Moonrise Kingdom recently, a man walked by and shouted to everybody, “At the end of the new Wes Anderson movie, they all die.” That didn’t turn out to be true (Oops! Was that a spoiler too?), but if it had been true, so what? Does that make the journey Anderson has planned for us less magical? We may know where we end up. Does that matter? Should that matter? The film isn’t about its own final scene or scenes. If it were, it’d be around three minutes long. No, instead Anderson had more to say. We weren’t there to be shocked by an ending…we were there to be led by the wrist by a man we wished to spend time with. Is that an experience that can even be spoiled by advance knowledge?

What’s more, I knew that Rosebud was a sled. I knew that everybody rallied around George Bailey. And I know that Darth Vader is Luke Skywalker’s father. So do a lot of people. And yet I doubt that it’s interfering with their enjoyment of those films.

And why should it? Certainly the revelation of Vader’s paternity earned a few gasps in theaters, but was it what resonated most with the people in the audience? Probably not…or, at least, the shock was not what resonated most. If it had been, there wouldn’t be much of a reason to rewatch it now that that coin has been spent. And yet — and please correct me if I’m wrong — I’m under the impression that people do still rewatch the Star Wars films.

So there must be something else. People know there must be something else. After all, how many people can say that their favorite book, film, song, or anything else is something that they’ve only experienced once? No, more likely it’s something they’ve returned to — and continue to return to — many times over, despite the fact that they “know what happens.” They’re already self-spoiled. And it doesn’t detract from their enjoyment. If anything it may enhance it, as knowing what’s to come can give them a stronger appreciation for the steps the artist must take in order to arrive there.

That’s fair. That’s good. I agree with me.

And yet…I still don’t want to know what happens on Breaking Bad.

I know spoilers are a ghost we shouldn’t be afraid of…but when I see it coming, I run in the other direction.

Even though I know better.

Why? What’s so scary about knowing what’s to come? Isn’t it one of mankind’s most clearly recurring wishes to know, in some way, what the future brings? We can prepare ourselves for it. We can steel ourselves against it. We can look forward to it.

So why, given the opportunity to know the future in micro, are we so compelled to shut it out?

I don’t have an answer. I don’t know why. You can rationalize it all you like, but, in the end, we don’t want to know what comes next. At least, not until we get there.

That’s fascinating to me. Because I really, genuinely, honestly, don’t know why.

NOTE: This is a story that I wrote last year for Machine of Death. Don’t bother looking for it; they rejected it. Regardless, I thought it made for a pretty worthwhile writing exercise, and since it’s going nowhere else it might as well go here. There were certain guidelines, such as: the story must include a machine of death, the title of that story must be the prediction that your protagonist receives from that machine, and the prediction must come true. Enjoy. Or don’t. It’s up to you.

Cold and Despondent in an Empty Room
–Philip J Reed

The man didn’t know what he expected, really, when he showed up to have the exact circumstances of his death predicted, printed, stamped and certified. But one thing he never, in a thousand years, would have expected was that it would turn out to be a very good career move.

Of course he knew he was going to die. Everybody was going to die. That was the point of being alive…at least as far as he could tell. But knowing it so conclusively, so specifically…it was different. It made everything feel different.

“Snoopy or Cookie Monster?” the technician asked him blandly, digging through a crate at his feet.

“Snoopy,” answered the man, rubbing his arm where the needle had been. The technician handed him the bandage, and he applied it himself. The bandage seemed like a formality. Given the circumstances, it only could be.

* * *

His wife climbed into bed beside him. She had come home early. It wasn’t even dark yet. He pulled the shades and got into bed.

“Well?” she asked him softly, nuzzling his shoulder.

He pretended to be asleep.

* * *

The slip of paper read COLD AND DESPONDENT IN AN EMPTY ROOM. He didn’t ask for clarification, but the technician must have been asked for clarification a lot because he immediately offered, helpfully, “Suicide.”

“Suicide?” the man asked.

“It doesn’t say suicide,” the technician said. “But I think it’s pretty clear.”

“You think?”

The technician shrugged. “There’s counseling in the next room,” he said. “You get fifteen minutes, and then I think they charge for any more. But get there now because there’s always a line.”

“I’m not suicidal,” the man said. “It doesn’t even say suicide.”

The technician was preparing the machine for the next client. It was a fairly involved process that involved not only the replacement of syringes (for superfluous hygiene reasons) but also a complete systems check and a full baseline recalibration with a wide range of standards (from “LONG AND FRUITFUL LIFE WITH ULTIMATE TERMINATION IN THE SOFT ARMS OF WINTER” all the way down to “DOG ATTACK IN PARKING LOT”), and then a confirmation of the accuracy of that recalibration by a second, higher-ranking technician.

This higher-ranking technician was already approaching. The man still clutched the short piece of paper that he still needed to have certified by the clerk in the lobby as though he had pulled it from the world’s cruelest fortune cookie.

“Larry,” the first technician said without looking up. “Suicide?”

The higher-ranking technician pulled the paper from the man’s hand, glanced over it briefly, and handed it back. “Who knows.”

“Probably suicide though?”

“Does it matter?” the higher ranking technician asked. “Let’s go with this; we’ve got a tight schedule.”

The man was guided by a woman in white into the lobby, where the clerk recorded and made official the known circumstances of his eventual death.

* * *

These death tests were mandatory, but, for now, they were confined to a relatively small test group. It wasn’t that the machine’s reliability was in question; that had already been established beyond the shadow of any doubt when the inventor of the machine tested it on himself, learned he would die in under an hour’s time in a collapsing laboratory, and relocated in a panic to a much sturdier lab than his own which was then demolished by a wrecking crew who showed up to the wrong address.

The man had been chosen randomly, the letter said.

Very few people were chosen, the letter said.

Very few people were chosen, the letter said, not because the machine was being tested, but because civilization’s ability to cope with the foreknowledge of its own demise was being tested.

The man was a test subject. He was neither willing nor unwilling to be a test subject. He was going to die, he knew, whether he was a test subject or not.

The only question was how.

And it was a question the higher-ranking technician answered without even realizing it.

“Does it matter?”

The man thought about that. Instead of sleeping, he thought about that.

* * *

The man left the next morning before his wife woke up, and took the bus to work. The digital readout on the machine told him he had 59 days left to live, and while he knew that going to work should have felt to him like a poor use of what little time remained, there wasn’t really anything that felt to him like a much better use.

Did it matter? A few days ago, maybe. But not now. Of course it didn’t matter. It didn’t matter if he skipped breakfast. It didn’t matter if he never listened to another record in his life. It didn’t matter because in 59 days, it couldn’t matter.

He was a telemarketer. He was paid a salary too small to support even himself and his wife, let alone the family they had occasionally wanted, to call strangers on the telephone and try to make them buy insurance that he wasn’t even sure existed. He never met any of his customers and his phone did not accept incoming calls. He spoke to everybody once, and then never again. He either made the sale, or he didn’t.

You had one shot at things, and then you crossed the name off your list — whatever the answer — and moved on to the next. One of his coworkers, who was also named Larry, referred to this technique as “slash and burn.”

Larry was not there when the man arrived to work. Nobody was there, except for the cleaning woman, who shuffled from cubicle to cubicle looking for something to clean, hoping both that she’d find something, and that she wouldn’t. She did not try to make eye contact with the man, which he appreciated.

He sat down at his desk, put on his headset, buried his face in his hands, and spoke, one by one, to the strangers his computers called for him.

His coworkers showed up two hours later, and he did not lift his head.

* * *

“Hey,” his wife said.

“I’m too tired,” the man told her.

“Can we talk for a little bit before bed?”

“I’m too tired to talk.”

“Can you just tell me what the machine said?”

“I’m too tired to talk about what the machine said.”

Besides, the man knew, it didn’t matter what the machine said.

It didn’t matter what the machine didn’t say either.

It didn’t matter.

* * *

In the morning he showed up to the office even earlier. It allowed him to make another 20 phone calls than he had the day before. He was supposed to read to his customers from a script, but he started deviating from the text without realizing it.

His mind was nowhere. There was nothing he could think about. He couldn’t think about providing for his wife, because now he never could. He had taken this low-paying job because it was offered to him, and he assumed he would eventually move up. Now that could not happen.

He thought he would make friends who had connections somewhere. Now that could not happen.

He thought he would impress somebody eventually, and that sometime, somewhere, a door would swing open, and he could walk through it and find for himself and for his wife and for the family they now could never have a richer and brighter and better future in which he was — if not somebody — at least not nobody.

He thought he might find something. He thought there might be something to find. He thought that maybe, if he tried, if he lived his life and loved his wife and cared and worked and saved, that he might actually accomplish something.

Now that could not happen. And what was worse, it didn’t matter how he lived. It was too late. He might as well have been a criminal. The machine did not only confirm that his life would be short; it confirmed that whatever time he spent alive had to be meaningless.

He deviated from the script without realizing it. His eyes still glossed over the laminated page before him, but he was saying something different than he had said to customers before. He was saying things that they were listening to.

They were agreeing to sales. When they agreed to sales, the computer transferred them to somebody who would take down their billing information, and then they were gone.

Or, to them, he was gone.

* * *

By the end of the week, his wife resorted to physically cornering him. “You have to deal with this,” she told him.

“It doesn’t matter,” he said.

“Tell me what it said.”

“I’m too tired to talk.”

“Have you been eating?” she asked him. “You haven’t been eating.”

“No,” the man said. “I haven’t been eating.”

At least, he did not think he’d been eating. Why would he have been eating? What difference would that have made?

“You’re not going through this alone,” she said to him.

He held his eyes closed. He left when she was asleep.

* * *

“I’m not suicidal,” the man said. “It doesn’t even say suicide.”

“It gets flowery sometimes,” the technician told him, readying the machine for its next victim. “Me and my brother were in the second batch, last year. It came right out and told me I’ve got nothing to worry about until my trip to Greece, which, the way they pay me, isn’t going to happen for a hell of a long time. But it told my brother that ‘the sullen clap of Heaven’s malaise would steal his hair and life.’ Two weeks later, bam, lightning strike.”

The man stood silent. Whatever the answer was, he knew already that it was irrelevant. The machine either meant that he would commit suicide, or it didn’t. Either way, it didn’t matter.

“I don’t know,” the technician continued, at least partially to himself. “Some of them, it’s just, okay, here’s how. And other’s it’s like it’s channeling Shakespeare or some shit.”

It was either channeling Shakespeare, or some shit.

Either way, it didn’t matter.

* * *

Larry, the man’s coworker, stood beside him while he was on the phone. When the call was finished, Larry pulled the headset off the man and said, “Are you coming out tonight?”

“No,” the man said. And then, “I need to make another phone call.”

Larry said, “Don’t you ever go home?”

“Yes,” the man said sadly, realizing at once that, maybe, he didn’t actually have to.

“What happened?” Larry asked him. “You don’t come out anymore. It’s just a quick drink. You can’t turn into a hermit.”

The man was spared from having to account for his demeanor, however, by his boss, who also appeared in his cubicle and said that he wanted to speak with him for a moment. Larry, whose idea of job security was to evade the manager as often as possible, disappeared for the night.

His boss wanted to speak to him because the man’s sales numbers were extraordinarily high that week.

He said things like, “I don’t know what you’re doing, but keep doing it,” and “What we really need is a whole lot more men like you.”

The man wasn’t sure exactly what he said, because he wasn’t exactly listening. The man stopped exactly listening when he realized that it could no longer have possibly mattered if he listened at all.

* * *

When his wife left him he watched her go, but he felt very little. He didn’t regret her leaving, because he couldn’t blame her for leaving. He didn’t regret consulting the machine, because it hadn’t been his decision to regret, and also because it wasn’t the machine’s fault that nothing he said or did could possibly matter.

He knew that he could keep her — for about a month and a half anyway — if he could only tell her what the machine had said. He knew that she would help him try to make sense of it. He knew that she would stay with him, and comfort him, and help him come to terms with what he knew he could never come to terms with alone. He knew that he could spend every one of his remaining nights in bed with her, feeling her close to him, holding her, being loved by her, and needing her, if only he would speak up and tell her what it was that was pulling the man away from himself.

But he also knew that none of that mattered.

And so she left, and he watched her go, and at some point he either fell asleep or passed out, and before the night was even half over he returned to work, plugged in his headset, and let the computer find another sleepless soul, somewhere, alone and cold in their own empty rooms, the ghosts of optimisms past lining their walls or garage floors, in homes with sputtering heaters and understocked cupboards, their pets blind with cataracts and bathroom sinks adorned with hairbrushes they couldn’t bring themselves to throw away, with yellowed newspapers from better days and a drawer full of loose photographs, a hole in the wall that would never be repaired or a broken window half-heartedly concealed with wet cardboard, a painting never hung or a Christmas gift never delivered, and an overnight bag, empty, still with its original price tag, and dull knives and a broken stove, carpeting leading upstairs to a series of rooms gone unused for years, a Ping-Pong table in the back yard sagging from the rain, the musky smell of thick dust and expired store-bought tomato sauce, and unheard echoes of years-old conversation between people who would not — could not — exist anymore, the imagined phantoms of haunting that would never come, yes, just another of these many sleepless souls who just needed to hear from somebody so young, and already worse off than they could ever be.

* * *

By the end of the month, the man’s sales figures caught the attention of the regional office, and then the national headquarters. Not only had the man outperformed himself; he had outperformed any of the other sales people in any of the offices scattered across the country, tucked, as they were, into strip malls or conference rooms in larger business complexes.

Larry stopped trying to get his attention, and so did the rest of the man’s friends. He stopped calling them, and they disappeared. His wife was the only other one who knew about his appointment with the machine, and she was content to leave messages that were never returned.

It didn’t matter, the man thought to himself, whether or not he returned them. In another month it would matter even less.

“I know you’re putting in more hours now,” his boss told him, “but it’s more than that. Are you using the script?”

The man didn’t answer.

“Of course you’re not. The script is shit. What are you using?”

“I don’t know,” the man said.

His boss waited for something more.

“I just talk,” the man said eventually.

“Whatever you’re saying, it’s working. Your sales pitch. Whatever it is, and I don’t even care what it is, it’s brilliant. In some businesses you can let the product sell itself. We don’t sell anything here. We sell a waste of somebody’s time and money, and you’re selling it like it’s piping hot porno.”

His boss sat on his desk for a moment, thinking.

“Next Thursday,” his boss said finally, “I’m going to the emergency conference in Phoenix. You probably heard about all the lawsuits. Anyway, they wanted me to give a talk and I was going to bullshit my way through 45 minutes of variations on ‘we’re in the people business’ for the fourth year running. But I want you to come.”

For the first time that the man could remember, his boss said his name.

“I want you to come, and just kind of pep people up. Give them a good talk. Tell them how to sell this shit because I am telling you that you’re the only one who’s actually selling any of it.”

The man shrugged, which was as good as any other answer he could have given.

His boss asked him if he had to check with his wife first.

The man shook his head and said that she was dead for all he knew, which he knew was true, even though she had left him seven messages that day, the most recent of which was only an hour ago. The following Wednesday they flew out to Phoenix, and the man pretended to sleep for the entire flight.

* * *

His instincts were slow to change, and when the man checked into his room at the Sharpe Tower Hotel he wondered, as he couldn’t help but wonder, if this room qualified as empty enough to be the room. But then he realized, before the thought was even complete, that it didn’t, wouldn’t, and couldn’t matter. Even if he didn’t know that he still had two weeks remaining, it couldn’t have mattered.

Suicide, homicide, death…three sides of the same coin. It happened, and it comforted no-one to know that it was — or would be — one and not either of the others. The end result was the same. He sat quietly in the armchair and stared vaguely at a blank television screen. It wasn’t to be this room, but it didn’t matter if it was. He blinked enough times that the sun came up, and he shuffled into the conference room on the fourth floor to deliver his speech.

* * *

The man had no notes and hadn’t discussed with anybody beforehand what he was going to say, so there is no way to confirm that what follows is at all accurate. Unfortunately, this record, incomplete or erroneous as it might theoretically be proven to be by an outsider who cannot exist, is all that we have. It is scrawled in only periodic legibility in the margins of a room service menu that one of the conference attendees, a Martin Klein of the Owlstack, PA office, happened to have in his pocket, and it is reproduced here, in its arguable entirety, for the betterment and edification of generations to come:

There is no meaning and we all share an inevitable worthlessness. Nobody will be saved. It is over before it begins. I think I am supposed to make you feel excited about selling insurance. And I think you might as well be as excited about selling insurance as you would be about starting a family, or finding a dead child on your doorstep. It is all equally meaningless and you cannot keep whatever small amount of happiness you may manage to find in a world that does not care that you were ever born. You may disagree, but you’ll never prove me wrong.

You cannot be excited. You cannot be happy. You cannot even be remotely satisfied with anything you’ve ever done or had done to you. Because all of that gives you hope, and what we sell can only really make sense to the hopeless.

When you speak to your customers, remember that you are going to die, and remember only that you are going to die. Wherever it happens, whenever it happens, you will have nothing to show for it, and nobody will miss you. You are not even a human being. You are a voice on the telephone. You could be hit by a bus a few minutes after you leave work and nobody you talked to that day would even know or care.

That is my message to you. We are already dead, even when we aren’t. We stand here or sit here or lie here in our own graves, and nothing will change for anybody else when go quiet for the last time. I have been asked by the hotel to remind you that the breakfast buffet continues until eleven o’clock, and that today’s signature dish is Belgian waffles.

Related Posts Plugin for WordPress, Blogger...