Good news; we heard from our contractor today, and the structural engineer has gotten far enough that they can start work again on Monday. Perfect timing, as I’m expecting to be well enough to go to work on Monday and won’t have to listen.
Author Archives: wjduquette
Hypertext Literature is Dead
Gosh, I’m writing a lot this morning. I think I’m just tired of sitting around.
Anyway, a guy over at Slashdot asks the question, “Is hypertext literature dead?“. I glanced at the comments, many of whom predictably said, “Dude! Wikipedia!” These people missed the point completely. Hypertext is alive and well, certainly; it’s how the Web works. And interactive fiction is alive and well. Not only is there a small but lively culture devoted to what we used to call “text adventures,” every computer game with a significant story-telling aspect to it is a kind of interactive fiction.
But hypertext literature, however, is dead…and good riddance to it, say I.
Back around the time the World Wide Web was becoming popular (and when was the last time you heard anyone say, “World Wide Web”?), it was common to hear people say that hypertext was the future of fiction. Authors would take advantage of hypertext to write books consisting of short, linked pages that could be read in any order, or that had multiple endings. You could choose to follow one character all the way through, and then follow another character, or read it back to front—assuming that there even was a front or back. It was to be a process of exploration, where the reader participated in the creation of the text they actually read. It was a Brave New World.
You might be thinking of the “Choose Your Own Adventure” books as a kind of hypertext literature, and they were, I suppose; but most of what I saw had something different in mind. It wasn’t meant to be a game; it was meant to be serious literature, serious exploration of characters. You were meant to read the whole thing, in time, but in your own order. I remember looking at a few experiments along these lines, back in the day. They were somewhat interesting. But, you know, they used to say that atonality was the future of serious music. The results were somewhat interesting, and yet melody and traditional harmony are still with us.
Just off of the top of my head, I can think of three reasons why hypertext fiction simply hasn’t caught on. The first is simply pragmatic: you get lost. As a reader, you want to read the whole story…but if you’re linking from page to page through a vast network of pages, it’s hard to have any idea how much you’ve read and how much is left. And since you didn’t usually have links to every page from every page, it’s hard to know how to find the pages you’ve not read. Ultimately, you end up with a linear list of pages somewhere in the work, and you keep having to go back to it to find starting points you’ve not yet read. It’s a lot of work.
The second is artistic, and has to do with the nature of story. A story, like a piece of music, is essentially linear. It has a structure: earlier parts lay the groundwork for the later parts, and the later parts build on the earlier parts. Imagine breaking a symphony up into ten second segments, and mixing them randomly: no doubt someone has written a symphony like that, but I doubt very many people have enjoyed it; and it wouldn’t work with, say, Beethoven’s 9th. A story has a logical order to it that builds to a climax. That order may not be purely chronological; we’ve all read books in which the chronological events are told out of sequence, and to good dramatic effect. They are told out of sequence because that’s how they best build to a climax.
This is true even in computer games like the various Legend of Zelda games: the player is free to wander about the world and solve problems in the order they choose…but only up to a point. The overall flow of the game is, in fact, tightly controlled so as to build up to the climax.
Hypertext literature rejected this notion in principle. The reader was to determine the order, not the writer. As a result, any order was as valid as any other. I suppose there might be stories that can be adequately told in this way; but in general, this notion runs contrary to the very nature of story.
The third is also artistic, and has to do with the skill of the author. Writing a work that can be effectively read in any order is hard. As an analogy, compare Pablo Picasso with Jackson Pollack. Picasso went through a period they call “high analytic cubism” where he painted “portraits” of people that looked like nothing so much as a flock of hundreds of little squares, hanging in space, all at slightly different angles. The notion, as I understand it, was that each square represented a point on the person’s face: the face was analyzed into hundreds of tangent planes, and each plane was exploded out in the form of a little square. If this is what Picasso really did, if it isn’t just hooey, then the resulting painting really is in some sense a portrait of the subject, even though it looks like nothing much, and involved quite a lot of real work. I couldn’t do it.
Jackson Pollack, on the other hand, laid canvases on the floor and dripped paint on them. Anybody can do that.
And that’s the problem. To do hypertext fiction really well wouldn’t involve a rejection of classic story structure. Instead, you’d need to have a deep, deep understanding of how stories work and of your story in particular, and your story would have to lend itself to being told in any order. You need the right author, and the right subject, and that’s a very small set. I’m not saying that it can’t be done…but the idea that it will ever be mainstream is, and always was, simply nuts.
You’re the Doctor
In my previous post I noted that you can only write like yourself (Read that one before this one). You have to follow your own muse, not anybody else’s. Ultimately, no one else’s opinion matters.
And yet, it does. Criticism from knowledgeable, trusted people is essential to growth in any craft. The trick is knowing what to do about it. And the trick is this: your critic is the Patient. You’re the Doctor. Your critic says, “Doctor, it hurts right here.” Or, “Doctor, your treatment is working mostly, but the side effects are awful. I keep falling asleep.”
In short, if a trusted critic tells you that you have a problem, you have a problem. Constant Readers can tell when something isn’t working, and you should listen to them. But you’re the Doctor. You know the story you’re trying to tell, and you need to figure out for yourself what the right fix is. This is harder than it looks, because your critics will usually express their criticism as a suggested fix without actually pinpointing the real issue. In effect, they are saying “Doc, it hurts when I do this.” It’s up to you to diagnose the underlying problem, and to determine the appropriate prescription. And in the end, this will usually be something other than what the patient suggested.
I’m not advising that you ignore the suggestions you receive. Sometimes they will be spot on—and if you find a critic who can reliably tell you what’s wrong and how to fix it, glom onto them with both hands and a rope.
“So where did you learn all this,” I hear you asking. “You’re not a published author…how much experience with this can you possibly have?” That’s all true. But on the other hand, I’m a software engineer, a mathematical modeler, and a skilled technical writer with twenty-five years of experience. I’m not sure I’ve put Malcolm Gladwell’s “10,000 hours” into technical writing…but I’m not sure I haven’t. And all that time, I’ve relied on getting the best criticism that I can get. Fiction writing isn’t the same craft…but it’s a craft, just the same.
You Can Only Write Like Yourself
I’ve written a couple of novels, and I’m in the middle of revising a third (the first is on-line here, if anyone is interested). And every so often I’ll be reading a book, and be struck by the quality of the writing, and I’ll say, “Oh, I simply can’t write like this! I wish I could write like this!” I’ll sometimes have the same experience while reading blogs. I’ll read a book review by Julie or by Lars and think, “Gosh, they do this well. Why should I bother?”*
But here’s the thing, and it’s the most important thing I’ve learned in fifteen years of on-line activity: you can only write like yourself. I can’t write like Steven Brust or Terry Pratchett or Lois McMaster Bujold or Roger Zelazny…but then, they don’t write like each other, either, and I wouldn’t want them to.
But I can write like me. I can write so that my prose pleases me, so that it when I read it aloud it flows smooth as molasses. I can write it so that it makes Jane laugh, and makes me smile when I come back to it.
In the end, I have to trust to my judgement, to my sense of what works. I have to write for me. And if other folks like what I write (and they do seem to), that’s gravy. Tasty gravy, and I like it a lot…but the meat and potatoes are in the writing.
* I’m not fishing for compliments, here, nor is this evidence of some kind of crisis of confidence. I’m just reflecting.
White Cat
White Cat is the first book in a new series by urban fantasist Holly Black. It concerns a young fellow named Cassell Sharpe who is Not At All Nice, though he would like to be. His world is almost identical to our own, except that a small fraction of the population are “curse workers”—by touching another person with their bare hands, they can give them luck, change their memories, or even kill them. Each curse worker has a single ability…at least, so far as we know so far. (I suspect some inflation might occur in the long run.) As a result, everyone wears gloves pretty much all the time; not wearing gloves is considered improper or even dirty.
Curse working was prohibited in the United States in 1929, and so naturally become the province of organized crime. There are a number of major crime families, and Cassell’s own family is associated with one of the more powerful, the Zakharovs.
These things happen in the best of families, so they say, but the Sharpe’s aren’t one of the best families. Cassell’s mom is a con artist who can make people love her with a touch (and is in prison as a result); one older brother is the lieutenant of the heir-apparent of the Zakharovs; another is in law school. All three are curse workers; Cassell is not. But he’s been well-trained in the con, and he’s the resident bookie at his expensive boarding school.
So Cassell is making his way, pretending to be normal…and then he starts dreaming of a white cat, and sleep-walking. Someone is making him do it…but who?
Julie reviewed this book some while back. I’m kind of hot and cold with Julie’s recommendations; some of the books she likes simply don’t do anything for me. Being home sick, though, I was looking for books to read, and I thought I’d give this one a try. Gladly, this is one of the ones I like. I’m not inclined to gush about it, but it was a good, solid read, and I expect I’ll read the sequel one of these days.
Stop the HHS Mandate!
Image
Bullet for a Star
A couple of days ago, Lars Walker reviewed Bullet for a Start, a light hard-boiled detective novel (if that makes sense) by Stuart M. Kaminsky. I was looking for books to read yesterday, and it sounded light and entertaining, and for the most part it was.
The book is set in the 1940’s; the protagonist is one Toby Peters, a small-time PI who used to be a security guard at the Warner Brothers studio. He’s called in to investigate a blackmail attempt against Error Flynn, and along the way runs into Peter Lorre, Humphrey Bogart, Edward G. Robinson, and others. Oh, and he gets beat up repeatedly.
This is the first in a series of novels first published in the 1970’s, and in the usual way of things (according to Lars) Toby isn’t quite himself yet.
If this sounds at all interesting, you should go take a look at Lars’ post; I don’t see any point in repeating his perfectly accurate review.
The Spy Who Came In From The Cold
Being stuck at home with a cold yesterday, I went looking for Kindle books to read; and since I’d read and enjoyed John le Carre’s Tinker, Tailor, Soldier, Spy and its immediate sequels a few months ago, Amazon suggested I try The Spy Who Came in from the Cold.
I started it with some trepidation; Tinker and its successors are not easy books, requiring patience and much reading between the lines. I knew Spy was worth the effort, but I wasn’t sure whether I was up to making it. As it happens, I needn’t have worried. I don’t know whether Spy is really easier to follow, or whether I’ve simply acquired a sense of how le Carre works, but I enjoyed it thoroughly.
It’s the story of Alec Leamus, the head of station in Berlin prior to the erection of the Berlin Wall. As the wall goes up he sees all of his agents being killed one by one; as the book begins the last one is shot dead just a few yards shy of Checkpoint Charlie. Alec is old, and tired, and there is no longer much of a station to be head of, and he returns to London in disgrace.
It seems that his networks were rolled up by the exertions of a German named Mundt, the head of the East German counter-espionage office. Leamus has come to hate Mundt, and when Control offers him the chance to bring about Mundt’s downfall he jumps at it. The remainder of the book details the operation.
The Kindle edition I read includes a forward by le Carre, in which he explains that he wrote Spy in just six weeks while employed at the British Embassy in Bonn. It was inspired by the rise of the Wall, and by le Carre’s own bitterness and loneliness, and so it is a bleak novel of betrayal and pain…but also deeply fascinating.
If you’ve not read le Carre, and are at all interested in espionage and spy fiction, this strikes me as an excellent book to begin with.
It’s Quiet. Too Quiet.
I’m at home sick with a cold, and, shockingly, it’s quiet around here. The contractors finished up the bulk of the jackhammering yesterday, and now with the extraneous walls removed and the foundations and plumbing all exposed, we can see what needs to be done structurally. We had the architect and a structural engineer come through yesterday afternoon, and now we’re just waiting to see what they tell us. In the meantime, it’s quiet. No hammering, no saws, no voices.
I’m sorry that the work isn’t going forward today (though not as sorry as our contractor is), but on the other hand, it’s nice that things are restful.
Up Jim River
Up Jim River is the sequel to Michael Flynn’s The January Dancer, which I reviewed a few days ago.
It has a somewhat different feel to it than its predecessor. The January Dancer is told primarily in retrospect: a bard finds a scarred old man in the Bar on Jehovah, and wangles a story out of him about the Twisting Stone. The tale alternates between the bard and the old man and the main matter of the story; and the main matter of the story covers a lot of ground. One of the neat things about the book is the structure: the old man insists on telling the story in his own way, and that way isn’t entirely linear.
Up Jim River picks up where The January Dancer leaves off. One of the principles of the earlier tale, a Hound of the Ardry named Bridget ban, has disappeared, and the bard dragoons the old man to help her go searching. Indeed, the bard is Bridget ban’s daughter, and entire “modern” part of the previous book was simply part of the bard’s search. As a result, Up Jim River is much more linear than its predecessor, and seems to move at a more deliberate pace.
Nevertheless, I enjoyed it thoroughly. As I said in my earlier review, the Spiral Arm of Flynn’s imagining is an interesting place, and we get to see much more of it. Some of the old characters return, and it’s interesting to see them “for real” rather than through the old man’s eyes; and there are a number of intriguing new characters as well. And though this is the second book in a longer work, it isn’t simply advancing the global story arc; it has a definite beginning and end of its own.
The third volume in the series is called In the Lion’s Mouth, which has just recently been released; I intend to read it as soon as the e-book price has come down some.
