Posted on Leave a comment

A Time for Merry Persiflage

Tonight Mark and I and his parents went to the Gilbert and Sullivan Very Light Opera Company’s free outdoor summer performance of “The Mikado.” They’re doing it again at the Lake Harriet Bandshell (where we saw it) tomorrow night at 5:30. I recommend it to Twin Cities residents if you can make it–there aren’t many mosquitoes down by Lake Harriet yet this year, and it’s free, and you will have before you such joys as Christopher Michela playing the Mikado.

(As far as I am concerned, he can reprise that role yearly. They can put the Mikado in “Yeomen of the Guard” and have Christopher Michela play him. They can put him in “Othello” for all I care and suddenly I am trying not to let my brain work at that for fear of what would come out.)

Among the joys of this production is that the entirety of “I’ve Got a Little List” is modern reference, which is entirely appropriate for Gilbert and Sullivan. Better still, they specifically called out the Orchestra Board as people who renovate the hall and then lock out the musicians. They got cheers for that line, more prolonged than for anything else in the song. And yes, I did clap and hoot. Loudly. It was not even a slightly mixed reaction from that crowd.

This week the Orchestra management canceled the Summerfest concerts to the surprise of precisely zero people. They offered, when they were canceling the last of the season, that we could have Summerfest tickets, and we said o ho ho it is to larf. But we weren’t actually laughing then, and we’re not laughing now. Mark is reading a book about music theory–I’ll get to it when he’s done–and one of the things it talks about is how venues shape types of music. Orchestra Hall without an orchestra is frankly a pretty dumb concert venue. You can put a folk concert in there, or a jazz combo, or a rock band, and we’ve been to all of the above. But it is for orchestras. It’s for our orchestra.

At least it’s for what’s left of it.

We’re trying to figure out what to do about the SPCO season, because it’s a very different kind of orchestra than the larger, fuller Minnesota Orchestra, and frankly we like the MN Orchestra style better mostly, and also (again speaking quite candidly) the MN Orchestra at its best is a better orchestra. I don’t mean anything against SPCO–it’s amazing that we can have two professional-quality orchestras at all, if in fact we can. But SPCO is not generally asked to play Carnegie Hall. And the SPCO musicians…were not, shall we say, treated ideally in their settlement.

So what do we do? Do we act like the SPCO season is our main chance at orchestral music for the year and plan accordingly? Do we get tickets for one or two shows that are the really exciting ones and hope for a MN Orchestra settlement? The paper ran an article about how this time around the management did not get nasty and personal with the propaganda around the cancellations, and I stared at the page, thinking, “Really? That’s what we cling to as a sign of progress? That they rested on their ad hominem attack laurels rather than reiterating them?”

That’s so depressing that I’m going to go think about attack laurels instead.

Posted on Leave a comment

Needlework

Oh, people. People, people, people, I am so tired of dislike of needlework being used as a stand-in for making a young female character actually interesting. I see this mostly in middle-grade fantasies, mostly. Not so much in YA, although I don’t know if that’s because I’m not seeing as much secondary world YA as I’d like. It sometimes goes with not being boyyyyyy crazy. Because girls who are interested in boys are stupid and hate everything that is fun and good and probably will grow boobs early and never ever ever have adventures. (Also girls who are interested in girls are invisible and don’t exist. So basically if you have proto-romantic feelings before age 18 or preferably 21, you stink. Thanks, MG tropes!)

Several things about the needlework thing annoy me, though. One of them is that it’s the cheap shot among “women’s work” stuff. It’s the one that middle-grade readers of the present are by and large not being asked to do, or at least not insistently/universally. Some girls are crafters as a hobby, but very few of them would self-define as doing “needlework.” So it’s a lot safer for an author aiming at a tomboy everygirl, because, hello, third wave! Tomboy everygirls can love making cookies or soup or whatever. And nobody* really says, “I adore cleaning. I live for cleaning. Cleaning is so awesome.” You can have your character announce that she hates scrubbing the floor, but nobody thinks that makes her amazing, they just think it makes her normal.

The other thing that ties in with this is: needlework used to be a lot like cleaning, in that it used to be necessary for continued health. Sure, you can choose whether you want your home spotless or a little messy, but you do in fact need to wash your dishes, one way or the other. That’s a health issue. And before industrial textiles, you had to do a million textile-related chores in order to keep your family healthily clothed. Mending. Taking things in and letting them out and altering them for younger/smaller family members. Even tapestry, while it is an art form and was used for self-expression, was also used to keep the walls of those stone castles and houses from turning the wenches into wenchcicles. Even in post-industrial textile societies, you will see a very realistic concern for what torn clothing and clever needlework can mean if you read the books of Noel Streatfeild, where the cost of a dress to put a family member in a good position to gain economic advantage is really non-trivial. I would love to see a parent or sibling in a fantasy novel react to a character’s stated hatred of needlework in one of these contexts–basically someone treating it as the protag saying, “I want you to buy me a better cell phone and data plan and all the other bells and whistles I want,” or else, “I hate cleaning the toilet,” rather than, “I am so interesting and independent!” I don’t expect that soon, though. It’s pretty embedded.

So where does all this come from? Two places: resentment of early twentieth century middle-class Anglo/American enforced femininity, and the Victorians. A lot, a lot of the women who pioneered the fantasy genres–especially children’s fantasy–chafed at the roles they were slotted into in the rest of their lives. And the “needlework as a useless pastime for enforcing female idleness” is straight out of Victorian life, where manufacturing endless unwanted decorations for the parlor and the jumble sale was, in fact, some women’s lot. But the Victorians were substantially along the line of progress of industrial textiles; a vicar’s daughter who spun flax would be distinctly odd, because that sort of thing was done in factories by then. Taking those frustrations and plunking them down wholesale in medieval-inspired cultures is understandable for those who lived them and witnessed them firsthand–Edith Nesbit, if ever you do that, I forgive you. (But notice that Nesbit has an unusual regard for the consequences of the children’s rash behavior on servants and the family budget. This was not much replicated by her imitators.) For those of us for whom they are historical study, it’s just plain laziness.

More than that, it’s attempting to make traits and interests exclusive that frankly aren’t. My friend V., for example, crocheted me a hyperbolic plane. She is interested in fiber arts and in math. She didn’t have to choose Boy Stuff or Girl Stuff–she can like some gendered activities and a great many activities like fiber arts and math that are not essentially gendered. And we lose a great deal when we accept shorthands for characterization too easily, too readily. “She’s a tomboy, not a girly girl.” “He’s a brain, not a jock.” We make our own cultural pitfalls in creating supposed opposites that aren’t really opposed more universal than we mean to when we import them whole cloth into secondary worlds.

Honestly, though, it’s just boring. It’s a trigger for me to say, “Another one of those, author getting lazy,” and put the book down. Find something else to express your character’s adventurous soul. Or don’t make them have a standard-issue Adventurous Soul TM in the first place. Whichever.

*Almost certainly somebody says this, because, well, people. They vary. And almost certainly there are loads of women who hate “needlework.” I am not a seamstress or a crafter myself. My complaint here is not that girls who fit these traits are unrealistic or do not exist, it’s that the traits are being overused and used cheaply.

Posted on Leave a comment

Personal rehabilitation and the community

So yesterday the Wild upset me and Tim by getting rid of Setoguchi and using the money to get Matt Cooke. I know this means nothing to you, so let me give you some background: Matt Cooke is a goon. This is the nicest language I can use, because I don’t want to distract anybody with exactly how angry I am: it is an objective fact that he is a goon, that his hits are dirty and his play unacceptable.

And my team is keeping him around. Is paying him a non-trivial amount to do so. Is associating him with people who are interested in professional hockey in general, and with the Minnesota Wild in specific.

This is, to say the least, pretty upsetting.

See, hockey is a rough game. Anybody who talked about the unique physicality of a hockey game would be right; professional hockey is really pretty unique that way because it consists of very large men on an enclosed slippery surface. And because people have not chosen to take steps to make it not that way, which they could do. But there are hits and then there are dirty hits. Hits to the head. Slashes to tendons. Things that fans of a player might want to look at and say, “That was an accident,” but they just can’t. Because it wasn’t any accident. Because when you are a hockey player, it is your job to have enough control over yourself and your play not to have that kind of accident.

Matt Cooke has seriously injured several other players with head shots. The management of the Wild knows it. And they have chosen to employ him anyway. I love my team. They entertain me. They do really fun things, and I love, love having them in town. There’s no one else in the game quite like them, for me. And they have chosen to employ Matt Cooke.

So…Matt Cooke has assured the world that he’s rehabilitating himself. That he is turning over a new leaf and becoming a new kind of player. Tom–I’m sorry, why was I thinking Tom? Chuck Fletcher has assured us all in the Strib today that he believes Cooke is going to be a fine contributor to the team and not cause the kind of problems he’s caused before.

And me, I believe in rehabilitation. I do. I believe that people are allowed to become better people. I believe in helping people learn from their mistakes.

But there’s got to be a line drawn, and my question is where is that line drawn? Where do somebody’s repeated mistakes make you think, “Okay, buddy, why don’t you become a better person tending bar at Applebee’s somewhere, or selling Kenmores at Sears? Why don’t you become a better person in a field that is not quite so fraught with baggage as this one? Run a soup kitchen. All the best to you. Get out of my field.”

I think Matt Cooke is past that line for me. Because not only is this a person who has had egregious dirty hits. He’s had them after he said he was going to change his game. After his behavior was specifically pointed out as unacceptable; after his own coaches and teammates said that it was the kind of stuff the game did not need. After. This is not an inexperienced kid who has never played the game before. This is not a clumsy guy who just picked up hockey later in life. He had his chance to learn appropriate behavior in his field as a young person, and then he had another chance when people noticed that he hadn’t learned it.

And as long as a major company in his profession continues to employ Matt Cooke, even if they say he’s turned over a new leaf, I just don’t believe that he will. I believe that they’re enabling him, and they’re using one of my favorite teams in my favorite sport to do that. And that upsets me. It makes me angry. The guys on the other teams should not have serious reason to fear when one of our players is on the ice. Fear that they’ll get checked into the boards, sure, that’s hockey as it is played. But fear that they will be deliberately concussed or crippled, given injuries that will drive them out of working in their field of choice, not accidentally but deliberately? No. That’s not okay. And when it’s my team, in some sense they’re doing it in my name.

I want somebody to grab the guys in juniors and in the minors who are watching Matt Cooke and say, “Look, this is not a way to be. This is not a way to get a career. This is not our game.” I want somebody in the community to intervene–and to intervene believably–to show younger men that Cooke is not their role model and that this behavior will not be accepted. I want to catch them before they become this guy. Cooke’s not the first. I wanted it with Todd Bertuzzi, whose name in this house is That Little Bastard Bertuzzi. I’ve wanted it with half a dozen other players at least. Because this kind of bad behavior can taint an entire field. Can hurt people and ruin lives. And if you pay the guy, you’re supporting it.

You know what I mean?

Posted on 1 Comment

Subtitles: a request

One of the great things about Netflix, I have discovered in the few months we’ve had it, is that I can watch a variety of foreign films and TV without having to pay through the nose for it. Hurrah, Netflix! Yesterday I watched a Chinese movie with my workout, and today a Danish cop show, The Eagle. Both were fun, and I am definitely continuing with the Danish cop show. I especially like to language-geek about translation choices: I only know about ten words of Chinese, but one of them is “kill,” so I can tell when the crowd is chanting that rather than the “Fight!” the subtitler has chosen to put at the bottom of the screen. And I love thinking about choices like that and when it’s a matter of bad translation, when it’s a matter of cultural difference being recognized, when it’s a matter of subtle shades of meaning.

But the last few days have given me a new plea for subtitlers.

Subtitlers: please, please, please indicate change of language in the conversations you’re subtitling. I can hear the difference between Danish and Icelandic*, but I’m not sure that should be your default assumption when you’re subtitling in English–especially when there’s characterization stuff about who reacts in which ways to the Icelandic. And once you get into Middle Eastern languages, I can tell you that the characters have stopped speaking Danish, but I cannot tell by ear what language they are speaking, except I can tell Indo-European from non-Indo-European given enough time and sample sentences, mostly, sort of. And therefore rule out Pashtun, Persian, etc. if I’m lucky. In the case of this show, I assume that the characters who were not speaking Danish, Icelandic, or Arabic (which was clearly labeled in the dialogue that the character would speak it and why, so good there) were speaking some dialect of Turkish, because culturally that is who is likely to not get labeled in Denmark as unusual or in some way interesting. But it still would have been nice to not be just completely guessing.

It is pure blind luck that I know enough Japanese language structure to be able to say, “Wait, that was Japanese, not Chinese,” and again: only if I am really paying attention to the dialog as it is spoken by the actors and not just as its meaning is conveyed by the subtitles. That is a level of attention I don’t always have available to use, and I can easily imagine situations in which I could not perform the analysis required to get there. And while it can be a fun intellectual exercise, it’s generally not supposed to be the point of the viewing experience for most viewers, I wouldn’t think. It makes the focus on the meta-story instead of the story.

So please. Use different colors of subtitling, or put the language marker in brackets at the beginning when they change, or something. Dumping it all into English–or whatever else you’re subtitling it in–is not enough. I get why, for example, in many Asian languages the translator will choose to use some form of the character’s name when that’s clearly not what the actor is saying: because many of the social-honorific forms don’t really translate to English without needless exoticizing. I just don’t think that switching languages within a subtitled work falls into that sort of subtle judgment category.

So what are your favorite subtitling problems, bloopers, or beautiful incongruities?

*Here is your quick and dirty, entirely parochial, guide to distinguishing the Scandinavian languages by ear: Danish is the one that sounds funny. Icelandic is the one that sounds fancy. Swedish and Norwegian both sound normal, but Swedish sounds the pointy end of normal and Norwegian sounds the squishy end of normal.** And Faroese sounds like you’re trying to talk with a sheep on your head. You’re welcome; don’t say I never gave you anything.

I have no idea whether this is useful to anyone but me, actually, but that’s how I do it.

**Once you’re distinguishing between Nynorsk and BokmÃ¥l, you’re a) very inside baseball, and b) really talking about dialect rather than language inasmuch as the two categories are distinguishable at all. So just give yourself a gold star at that point and move on, unless you actually, you know, speak Norwegian.

Posted on Leave a comment

Copperhead, by Tina Connolly

Review copy provided by Tor.

The first book in this series, Ironskin, was a fairly close Jane Eyre recasting. If Copperhead is an equally close retelling of anything, I’ve missed it. It’s temporally a fairly close sequel but in structural terms not at all close–the main character changes from Jane to her younger sister Helen, and I think it could be read on its own fairly easily.

The main problem I had with Copperhead is that it’s in a clearly alternate universe, but I wasn’t clear how alternate–so how much it was supposed to refer to the Civil War Copperheads was not clear to me for most of the beginning of the book. And frankly they strike me as a pretty important historical element, so the fact that ultimately they don’t have much in common with the Copperhead movement in this book was not in general a plus.

However, I really liked the shift to seeing from Helen’s point of view–rather similar to the most recent Mary Robinette Kowal book, Without a Summer, which, while it did not shift viewpoint character, did give a far more nuanced and interesting picture of the beautiful and flighty younger sister character. Helen found ways to make a difference–even in the resolution of the book–that were true to her personality and skill set, rather than having to become a more standard-issue fantasy heroine in order to make her mark. The fact that she, for example, paid closer attention to the lives of the servants than many heroines seemed of a piece with both her past and her personality. And the gigantic funnely fey-related machine…was both fascinating in its inception and in its climax. And that’s all I can really say there without spoilers. But the endings all did feel earned, I can say that much, whether they fit the standard mold or less so.

Posted on 1 Comment

Books read, late June

Leigh Bardugo, Siege and Storm. Too much boyfriend, not enough sea serpent. (Seriously not enough sea serpent. Even if you have more patience for teenage relationship dynamics than I do. Sea serpents! They’re awesome! Not to be squandered!) I will still go on and read the sequel, but the balance of elements is not really what I would prefer.

Alfred Duclos DeCelles, The ‘Patriotes’ of ’37. Kindle. Random Canadian history, filling in the gaps. Various placenames in Montreal now have additional reference points for me.

R. Austin Freeman, The Case of the White Footprints. Kindle. Old mystery. I did not see some elements of this coming because, “Hey, I bet this will have random racial implications!” was just not something I thought of. It was not quite as jarring as running into Josephine Tey using ethnic language, but it was pretty jarring. However, it seemed more like an artifact of his time than the constant essential fact of Freeman, so I will probably try some other stuff when I’m in the mood for old mysteries and free is the right price.

Edward P. Kohn, Hot Time in the Old Town: The Great Heat Wave of 1896 and the Making of Theodore Roosevelt. This book badly needed a copy-editor, or possibly the author needed to have his stet stamp taken away. Not sure which. It was kind of a hot mess (yes, you saw what I did there), and it would more reasonably have been described as the Fall of William Jennings Bryan than the Making of Roosevelt. The heat wave information was interesting, a good counterpoint to more dramatic historical narratives and to people who act like everything in the days before a particular modern convenience (in this case AC) was Just Fine Dammit, rather than resulting in 40-100 dead babies in one city per day. But the text was marred by such howlers as misplacing the Mississippi River by several hundred miles (hint: it is nowhere the boundary between Iowa and Nebraska, folks) and spelling the same person’s name multiple ways in one paragraph. Probably not recommended unless you’re really interested in WJB, New York history, or non-standard natural disasters.

C.M. Kornbluth, The Adventurer. Kindle. Random Golden Age short on my Kindle, not very memorable.

James Michener, Space. Grandpa’s. This is one of the worst books I’ve read in a long time in terms of bigotry, and it was in some ways made even worse by the fact that you could watch him trying. And still failing so very badly. But when you write a slam on Jerrie Cobb and her cohort gratuitously into your book when you could have ignored them (or, y’know, treated them reasonably, but let’s not get crazy here), the fact that you have a “lady lawyer” is not going to appease me. And the stuff around non-white people in the space program…just stop, Michener. Just stop, and go write about moon rocks. You do fine with rocks. Tell us more about the rocks. HONESTLY.

Robert Sheckley, Bad Medicine. Kindle. This is one of the “classic” SF stories that has created its own cliches, but at the time I don’t think it was.

Walter S. Tevis, The Big Bounce. Kindle. The original flubber story. Too serious to call it flubber or involve basketball.

Abigail A. Van Slyck, The Lady and the Library Loafer: Gender and Public Space in Victorian America. Kindle. Reading rooms! All sorts of things about reading rooms. Short and interesting.

Helene Wecker, The Golem and the Jinni. This was the big win of the fortnight, highly recommended. It’s a turn of the (19th/20th) century New York setting, with a golem who works in a bakery and a tinsmith jinni. Beautifully written, great characters and setting. Hurrah for this book.

S.M. Wheeler, Sea Change. Discussed elsewhere.

P.G. Wodehouse, A Man of Means. Kindle. Wodehouse of a fairly standard type.

Jane Yolen and Adam Stemple, B.U.G. (Big Ugly Guy). It was apparently golem time in Mrissaland this fortnight, but this had a completely different tone than the Wecker. It’s a middle-grade or YA (not sure where it’s being shelved, actually) book that has a klezmer-jazz-pop-rock fusion band at its heart, a group of misfit kids who come together against bullies and their own worse impulses. There are important things about adolescence and power between the lines of this book, and sometimes in the lines themselves. I really liked this.

Posted on Leave a comment

Biographical hazards and characterization ramble

Last night as I was casting aside a library book with great prejudice (people: if anyone tells you that Thor was the king of the Norse gods–as a casual aside in a work of purported nonfiction, no less!–regard whatever else they say as suspect, because they do not know what they do not know), Mark suggested that this was the wrong approach because if I don’t finish books, I don’t blog about them to warn people. And it’s true, this is the tradeoff I make for not wanting to be unfair about books I don’t finish: I don’t warn you in advance that they are unfinishable. I’ve seen a couple of low-rated books on my mother-in-law’s Good Reads because of this and felt mildly guilty. It still feels like the right balance, but occasionally I make the “why I quit reading your book” posts to talk about general issues.

This one is with biographies. In order to write a biography of any length, it’s easiest to find the subject interesting, or you will be screamingly bored with your book. A good biographer understands the difference between “interesting,” “likeable,” and “sympathetic.” You’ll see the difference between interesting and likeable extremely clearly if you read corrective biographies, which are easiest to find about recent politicians: some historian or political scientist will get fed up with their sense that everything about Politician X is better referred to as St. X, and will write up a biography that corrects that view. Mostly these people have to be interested in X, or at least in X’s effects on the world, in order to do it at all–but sympathy and liking are definitely not required. (Good examples of this include Ronald Reagan and John F. Kennedy.) But outside politics, corrective bios are rarer, and the real pitfall is for the biographer to buy into their subject’s shtick. If your subject says, “I am the greatest musician of my generation!”, that’s an interesting window on your subject’s views, or at least on how your subject has tried to present them to the world. But for you to decide that this means your subject is the greatest musician of a generation–or more–is short-sighted and silly. And you should at least have some notion of who you are implicitly downgrading and why if you choose to accept the greatest musician notion.

The interesting/likeable/sympathetic split seems to come up with fictional characters, because a great many readers use the phrase, “I didn’t like any of the characters,” or, “I didn’t like this character,” pretty much interchangeably among these options. And I think the only one that’s really necessary for all readers is interesting. Some people really do want to read only about characters they’d be willing to have dinner with; some people really do want to read only about characters whose aims are compatible with their own. But some people don’t, in both of those cases, whereas nobody says, “This person is so boring to me, give me another hundred thousand words about them!”

One of the places this can go badly awry is if you need to kill off a major character. This can shift the balance of interesting/likeable/sympathetic in disastrous ways, because there will almost always be readers for whom Dead Guy A was the only one who fit the bill–they were reading for A. This is not a reason not to kill characters, but it’s certainly a reason to pay attention to what things people might like in your writing and why.

Last weekend a bunch of us were talking about bands that had broken up or carried on under the same name but without the exact group of people as before, and it looked to me like one of the most successful modes of carrying on is to not just replace the person who has left, but to add multiple people with slightly different (often overlapping) skills. Two of the places this has worked well for me are in the TV shows House and early seasons of MI5 (Spooks in the UK). One of the places it has not worked well despite my liking the show quite a bit is Criminal Minds. CM has a habit of replacing people demographically: Young Brunette Woman, Middle-Aged Dark-Haired Man, even a run at a substitution in the category of Young Blonde Woman. This encouraged me to compare directly or to scornfully refer to the replacement early on as The Fake [Character Name], whereas having a less direct substitution just shifts the dynamic overall.

Late seasons of MI5 have not succeeded nearly so well with this, I should say. The show is a bit infamous for being willing to kill or otherwise get rid of characters who would be pivotal in other shows–you really cannot count on any one character being around for the next episode. Early on, they were very good at fast characterization, giving me a quick hook to hang my caring on. Like many readers/viewers, I wanted to keep caring about a show I liked, so hey, look, it’s an older lady coming back to spy some more, and look at her doing the following things, hurrah! Ditto for various other characters. But by the time it got around to Tariq, it became clear that I wanted to like the character (young Near Eastern-British hacker nerd spy!) more than I was actually being given very much of the character to like. He was filling a role, and the other new S9/S10 spies even more so. I have three episodes left, and it’s begun to look a lot more like, “We need somebody to do such-and-such! You’re a warm body, and such-and-such is exciting! Go do such-and-such!” So if you’re going to substitute in a new bass player and keyboardist for your old bass player, you need to write pretty cool solos for bass and keys. Or at least let them improvise.

Biography does not have this benefit. Sometimes the person you find interesting is surrounded by interesting people up to a point, and then you run into the Great War or the Black Death or whatever, and suddenly everyone interesting has died and there’s nothing you can do about it. This is why I would not be a real historian if you paid me. All sorts of things happen that you cannot fix. Even Hilary Mantel can decide that somebody needs to have better lines than history might give them, but when you’re a real historian, you’re stuck.

Posted on 1 Comment

The Long Conversation: a 4th St. con report

One of the metaphors that comes up a lot at 4th St.–that certainly came up at 4th St. a lot this year–is genre as conversation, literature in general as conversation. And we kept emphasizing how far back this stuff goes, how people have been turning over ideas about the stories they tell and how they relate to the lives they lead for Quite Some Time Now Really.

It was a 4th St. It was so good. Oh wait: I already said it was a 4th St.

Con reports are hard, as better people than I have said before, because there is so much of the conversation about the con, and conversations are about flow, they’re about relationship, and so even when you remember great lines like Bear’s, “These Dead Marshes aren’t going to cross themselves!”, they don’t fit, they don’t give the full flavor, so you end up waving your hands incoherently.

I think starting with “Idiom, Character, and World Building” was a particularly good notion, because it felt like a lot of stuff in the rest of the con built on that. As usual I know that the panelists had cool stuff they didn’t get a chance to talk to, but that’s a sign that things are going well, not poorly. My own panels–Short Fiction, Tell Don’t Show, and That’s Another Panel (this year’s theme: Swearing)–felt to me like they went really well, and again, I was always left with more stuff I could say, and felt like the other panelists and audience were too. I did not, for example, have to resort to talking about James Michener on TDS, which would have gone better before I read Space this month. I think “fantasy of discovery” is a very useful framing of the lower-violence/variant-conflict fantasy, because it does an end run around the idea that if people aren’t fighting each other, nothing happens. I think Beth’s idea that deliberately broken structure can enhance reader attention will be very useful indeed. I think–a lot of things, honestly, but I’m full of tired, so getting them to come out coherently instead of just blurting, “I FIXED MY BOOK! Well, conceptually. The actual work of fixing my book is still to come,” is hard right now.

What you’ve probably already heard before: it was a 4th St. with nearly 24 hours without power. But that was okay, for most values of okay, for most of us. There were some really charming aspects: conversing by emergency light, or in the pitch dark. Doing music in the dark. Someone in the letters to the editor was predictably grumping about how we are not Resilient And Independent Like Our Forefathers Of Yore, and honestly: this is nonsense. Even people who had not packed for a power outage and didn’t have the candles and flashlights they would have at home managed to have a perfectly lovely evening using their cell phones for flashlights and their friends’ voices for beacons. It was fine. Modern humanity is fine. (Also, honestly, I had to wonder whether the power outage served as a convenient lightning rod, so to speak, for any crankiness anyone might have brought in. Possibly there was nitpicking elsewhere, but I didn’t hear any of it, and there’s always somebody who comes in grumpy and looks for something to blame. So hey, convenient, something to blame! Or else this was just an unusually good year. But past Fourth Streets have been awesome too, so I think probably something was a factor, and this seems logical to me.)

I don’t think we could replicate the experience by just turning off the lights in the con suite, and frankly that sounds pretty creepy to me. But having it occur naturally–I forget who was referring to it as camp–I think maybe Suzanne?–but at any rate we got some of the better parts of camp as well as some of the worse. (Hot water: do want.) And it was Fourth Street, so–yeah. I got to see some of my favorite people in the world, and they got me thinking about all sorts of useful stuff that will percolate out into the rest of my year. I love this con.

(PS Tim also has a con report. I think he captured much of the flavor of things.)