You Help Nobody When You Surrender Right of Way

Man DrivingHere’s a public service announcement: stop waving people on, asshole.

I know, you don’t think you’re being an asshole. You think you’re helping. I understand where you’re coming from. But it’s really important that somebody tell you you’re being an asshole. So, asshole: you’re being an asshole.

Right of way exists for a reason. Do you want to know the reason? It’s so you can keep driving your car without killing or being killed. Pretty obviously a good thing for all involved. So why do you think it’s polite to surrender that right of way? It’s literally the only thing between you and a car accident.

It’s nice to think that coming to a complete stop in the middle of the road and waving someone past is somehow a nice thing to do. But it’s not. Because you haven’t just surrendered right of way…you’ve surrendered the silent agreement between another person and the traffic around them. You’ve put them in danger. I know you didn’t mean to do this, but you did. And that makes you an asshole.

Don’t surrender right of way. You will kill somebody. If recent history is any example, it’ll probably be me. So fucking stop.

Some reasons not to surrender right of way:

1) Nobody behind you knows what the fuck you’re doing when you suddenly stop your vehicle and sit there waiting. Nobody else can see what’s going on. They are likely to try to get around you, and then the person you were waving on gets hit.

2) The person that you’re waving on doesn’t know what the fuck you’re doing either. In the time it takes you to silently negotiate this temporary alteration to traffic patterns with somebody else via vague hand signal, you could have just driven past and the person waiting would already be on his way.

3) Pedestrians also don’t know what the fuck you’re doing, so they’re not going to know who’s turning where, or when, or at what point it’s going to be safe for them to cross with their groceries, their dog, or their child.

4) The other lane or lanes of traffic can also be added to the long list of people who don’t know what the fuck you’re doing. You may come to a dead stop and wave somebody on, and that’s so very nice of you, but traffic moving in the other direction isn’t privy to your grand gesture and they’re going to keep coming, and they’re going to hit the person you’ve just waved into their path.

5) You don’t know what the fuck you’re doing either. If you did, you’d know that you stop at a stoplight or a stop sign, and that’s it. The roads are designed and traffic patterns are determined on the assumption that vehicles move. The moment you betray that assumption, you’ve cast everything else into doubt as well, and motorists will take steps to keep moving forward themselves. At best, you waste somebody’s time. At worst, you kill somebody or start a pileup.

You’re not doing anybody a favor. When I’m waiting to cross the street, I’m waiting for a reason: I’m supposed to wait. I’m not waiting for some gallant hero to stop his car…I’m waiting for that fucking car to get out of the way so that I can cross.

Why? Because I don’t know…what…the fuck…you’re doing. And once I figure it out, and I try to cross, the guy behind you almost hits me because he had no idea what was going on. Because your dumb ass is in the way, and not going anywhere, and he has somewhere to be.

So don’t wave me on. And definitely don’t get huffy when I wave you right back on in return. Especially since you’d already be long gone and I’d be well on my way if you didn’t put me, yourself, and everyone else on the road in that particular moment in immediate danger.

When you drive, I know what you’re doing.

When you drive, everyone knows what you’re doing. Why? Because the roads have been laid out in such a way that it becomes easy to anticipate what you’re doing, as long as you follow the rules.

When you surrender right of way, nobody knows what your intentions are, why you’re doing it, or what they’re supposed to be doing in return. And you look like an asshole.

Which is fine. Because you’re an asshole.

This has been a public service announcement. Asshole.

Why “Metroidvania” Is Not a Thing

Metroidvania is not a thing.

It isn’t. Or, at least, it’s not a thing that should have that particular term appended to it.

“Metroidvania” is a classifying term gamers use to refer to video games, usually 2D, that restrict or grant progress based on the items you have. It typically takes place in a large world comprised of smaller sections. As you find items and upgrades for your character, you can explore more and more of that large world, and usually even find additional treasure and passages hidden in previous areas.

If it sounds like I’m describing Metroid here, that’s because I am. And if it doesn’t sound like I’m describing Castlevania here, that’s because I’m not.

The term “Metroidvania” is an obvious portmanteau of those two series. But there’s a problem, because Castlevania has fuckall to do with the formula.

See, when Metroid was released, this sort of gradual progression in all directions was a relatively new navigational approach for video games. Whenever a game was released afterward that followed a similar mechanic, it was usually classified as Metroid-like. Just as games that offered a stage select were often compared to Mega Man, and games that featured you jumping on enemies to kill them were compared to Super Mario Bros.

Castlevania began life as a simple — though very good — side scroller with a Hollywood-Gothic horror theme. The antagonist was typically Dracula, and the protagonist was a vampire hunter (typically of the Belmont lineage) who set out to destroy him. You fought with a whip or similar weapon through linear stages. Sub-weapons were temporary, there was no backtracking, little in the way of alternate paths, and no permanent upgrades of any kind.

In other words, it was nothing at all like Metroid.

Eventually however Konami struck rightful gold with Symphony of the Night, which was a lot like Metroid. The entire game takes place in Dracula’s castle, and you progress by collecting upgrades in the forms of items and abilities. It was, and is, a great game. And thus, “Metroidvania” was born.

Symphony of the Night — along with its similarly-themed quasi-sequels — is about the only time the term “Metroidvania” makes any sense to use. After all, it combined elements of Metroid and Castlevania.

Since then, however, the term has been thrown around to encompass anything even remotely Metroid-like, whether or not it incorporates any elements of Castlevania whatsoever. Somehow these two games — despite one being a series-wide approach and the other being a series exception — got hybridized in the cultural consciousness and had a genre of their own named after them.

But that doesn’t work. Or shouldn’t work. “Metroidvania” only makes sense if the game being described contains elements similar to each of those series, and, really, nearly always, that’s not the case. A game in which you explore a funhouse or something, throwing pies at clowns and gradually opening passages can be like Metroid. It doesn’t sound to me, though, like it could possibly be anything like Castlevania. So why would we call it a “Metroidvania?”

I find it interesting that one singular game could be looked at as Metroid‘s equivalent in defining the genre…and I also find it inaccurate. Symphony of the Night borrowed Metroid‘s approach. It added its own elements, yes, but those are not the elements that define most other games that have since fallen under the classification.

The fact that the term “Metroidvania” exists speaks volumes about how immediately important Symphony of the Night was to gaming. But nearly always, “Metroidvania” is a misnomer.

That game you’re playing where you’re seeking jump upgrades and better bombs to blast open new doors? It’s a lot like Metroid. It’s nothing like Castlevania. It is, I’ll grant you, a lot like Symphony of the Night. But Symphony of the Night was a lot like Metroid, so let’s not complicate things.

It’s Metroid-like. Unless it isn’t.

And it usually, unquestionably, is.

Stewie Griffin and the Problem of Cynicism

Family Guy, 12 and a Half Angry MenI don’t like Family Guy. You know that already. But it does, at times, manage to make me laugh. Other times it manages to insult me as a writer. With the episode “12 and a Half Angry Men,” it managed to upset me as a human being.

Now this isn’t a matter of taking offense at an off-color joke. That happens too (seriously, Family Guy, I know you find sexual assault and domestic violence to be inherently hilarious, but is it too much for you to at least try to make a joke about these things instead of just putting them on display and assuming I find them inherently hilarious too?) but in this case it was more an example of problematic cynicism, and one that’s potentially damaging to our cultural mindset.

The episode is about Mayor West being on trial for murder. The jurors all see it as an open and shut case, apart from Brian who holds out for a not guilty verdict. As might be expected he gradually sways the other jurors to his viewpoint and Mayor West goes free. Family Guy certainly wouldn’t be above suggesting that Mayor West actually did commit the crime, but I think it’s safe to say that, within the reality of the episode, he didn’t, and Brian and the others rendered a fair verdict.

However at the end of the episode, the following exchange occurs:

BRIAN: It was a pretty intense experience, but the important thing is that, in the end, justice was served.
STEWIE: All you did was let a guy go. There’s still a murderer out there.
BRIAN: Yeah but we saved an innocent man today. That’s something to feel good about.
STEWIE: Feel good about? They found eight more bodies last night. One of them was on this block. There’s a maniac out there. He’s cutting people’s power off, breaking into their homes, and slitting their throats.

Stewie continues his rant, and the episode illustrates, ultimately, that Stewie is correct. There is a murderer on the loose, and Brian shouldn’t be proud of what he accomplished. And here’s the thing: that mindset of Stewie’s, which is clearly endorsed by the episode, is a vastly destructive one.

It’s important to note the context of this exchange, which is just the latest in a long line of “let us spell out a ridiculous thing about that genre convention…” gags. Family Guy likes to poke fun at form…playing it straight (relatively) for a time, before stepping back and saying, “But wait a minute…why did that happen?”

In this case, “Why did that happen?” refers to the deliberations being seen as a success, when, ultimately, the crime remained unsolved. See what’s wrong with that? Just typing it out gives it away: those are two different things. Related, sure, but separate. The deliberations are not the criminal investigation. The jurors do not and cannot catch the bad guy. That’s not their job. That’s not what they should be doing.

Okay, fine. A mindless gag at the end of the episode that thinks it’s being clever but is actually just irrelevant. Except that I then began to see reviewers being convinced of Stewie’s viewpoint, such as in this example from The A.V. Club:

“And Stewie points out what never seems to get highlighted in all these stories: if Adam West didn’t do it, there’s a murderer still on the loose. There are more bodies. And taking too much pride in swinging a jury takes a lot of credit for what amounts to simply letting a guy go.”

No. No.

Ten trillion times…no.

It’s not “simply letting a guy go.” Conflating the role of a jury with the responsibility of cleaning up the streets is a bad thing. It’s not a clever insight, and it’s not a problem that someone takes pride in preventing an innocent man from going to jail.

In cases like this — both real and fictional — there are two things at play. (I’m assuming here that a crime was actually committed, which isn’t always the case and can therefore complicate things even futher.) One: Someone committed a crime. Two: Someone is on trial for committing that crime.

Those two things cannot be seen as the same thing. If you don’t understand the separation there, then you’re playing the wrong game. And that’s a problem.

The jurors are responsible for item two…and not at all for item one. They don’t go searching for the criminal…they assess the testimony of the defendant. That’s all they do.

Granted, I have some personal feelings on this subject. And maybe that’s why this felt so bothersome to me. But pull those out and you’re still left with a pretty clear logical conclusion: each group of people involved in this case has a job to do, and it’s the jury’s job to do theirs, only theirs, and to do it the right way.

There should be a sense of pride associated with finding someone not guilty when there is not sufficient evidence of their guilt. Because that’s doing the right thing. That’s being human. That’s taking another man’s fate into your hands, and being responsible with it.

Yes, if you find the man not guilty then that means there is still a criminal out there. But that’s not the issue the jury was assembled to address. We have a police force for that. The fact that you found a man not guilty does not mean you’ve let the world down and failed to do something constructive. You’ve prevented a potentially innocent man’s life from being ruined, or ended. Isn’t that about as constructive as one can get?

Take Stewie’s concern to its (tellingly) unspoken conclusion. He harps on Brian because Brian did nothing but “let a guy go.” So it would have been better for Brian to not let him go?

What then? Mayor West still didn’t commit the crime, which means the criminal would still be out there, racking up bodies. But it would somehow be seen as more constructive for a man to be imprisoned than not? Just so we’d have something to show for it?

Stewie often serves as a voice-box for the writing staff. Part of his role as a character now is to point out these logical inconsistencies. But that’s a role that’s far too prone to cynicism, and it’s important to not let that drift too far along, lest you lose your humanity along the way.

This isn’t an “inconsistency.” Brian didn’t “just let a guy go.” And nobody should feel unproductive for doing the right thing…even if that one right thing leaves another wrong thing unaddressed.

I guess it’s easy to play with fate as long as it’s somebody else’s. But something tells me if a member of the show’s writing staff were on trial for a crime he didn’t commit, and he was found not guilty, he wouldn’t see that as a problematic inconsistency. More likely he’d be grateful that somebody did see to it that justice was served, and I truly doubt he’d be saying with his own voice what he already said here with Stewie’s.

Because he’s one man, and the criminal is another. Their fates are not, and should never be, tethered together. If your cynicism is causing you to bind them up…then I think you’re long overdue for some serious soul searching. That’s not the world you live in. And you should be very happy about that.

Why I, Partridge is Mandatory Reading for Anyone Who Thinks They’re a Writer

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.