Should a wonderful private moment be public?

Via Andrew Sullivan, I watched this moving video... No one can watch it without tears, I think. I certainly didn’t.

I was deeply moved. And then I thought. Not about pro- or anti-intervention positions, or the consequences and costs of sending troops abroad for extended missions. But about privacy.

I was moved by a private and personal moment. And I was moved, perhaps more than by great art.  Any artist who could stimulate emotion like this would be regarded as a genius.

This is probably one of the most significant events this girl has ever experienced. What right do I have to participate in it?

I think this girl had a right to feel this emotion completely and utterly in private. I don’t know what to do about the fact that she couldn’t, that she was compelled against her will to share it with millions of strangers, and that I participated in that violation, but I’m trying to figure it out. I think we all need to figure it out.

And I linked to it. And I encouraged you to watch it. I have participated fully in violating her privacy. Maybe she doesn't mind.  Maybe she's even proud, or will be someday. But that is all beyond the realm of her own choice.

We’ve been spared all sorts of ethical decisions simply because it was previously technically impossible to do any number of things, from examining fetuses at early stages to uploading videos of private moments. We didn’t have to take a position on texting while driving in the past, because there was no way to do it. There was no way to quickly copy and distribute music, or text, or images.  Now there is.

If the meek inherit the earth, it’s because they lack the power to do evil, not because they have decided not to do evil. Virtue implies the ability to do otherwise.  With power comes responsibility. We can’t duck the technology, and we can’t duck the need to decide what to do about its consequences. The answer may be “nothing other than moderate regulation, with an occasional hysterical overreaction to some egregious edge condition”. That is likely, in fact, to be the only possible answer.

But we have to make the choice consciously, with full knowledge of what it entails. We cannot evade it.
This particular little snippet is a useful place to start thinking. It is entirely positive. No one involved has anything to be embarrassed or ashamed about. It is really quite wonderful.  I think everyone should see it.

Should it be private? Or do we have a right to share?  Who decides, and how?  The fact that the questions are hard to answer does not mean they shouldn't be asked.

 

Always have something going for you

One secret to happiness in a writing career is anticipation.  When you get behind (and I spend most of my time behind), all you have to look forward to is a slog and a potential sale.  When you get a bit ahead, you have something coming out, you have something submitted, and your working on something else.

More productive writers have that feeling a lot of the time, but I do rarely.  Aside from the book, I have a story coming out in Asimov's, and two more out looking for a place.  Now, to really be ahead, I should have a story written for an upcoming workshop session.

We'll see.

But it's worth quite a bit of effort to get to this point, because it takes less mental energy to stay in it than it is to get to it.  The writing brain is a delicate thing, and needs some care and feeding.

This is, I think, why some other people play the lottery.  They want to always have something going for them.  There's always a chance that the numbers will come out right, and something good might happen.  All of us should try to make sure we've always got something going for us.  We deserve it.

Genre reading: Lonesome Dove

Do writers of Westerns have the same discussions about mainstream acceptance that (some) science fiction writers do?  That is, if there are any of them left--it's not exactly a jumping genre just now.

And I don't usually read it, though over the past couple of years I've learned to enjoy Western movies (with Rio Bravo a particular favorite).  But I'm reading Larry McMurtry's Lonesome Dove, and enjoying it a great deal.  Is it because it somehow transcends its genre?  I don't know enough to say.  But readers of a genre like its particular flavor, and will consume even inferior examples to get it, while non-genre readers wanting to try the flavor need a dish that includes ingredients they're more used to getting, in terms of plot, characterization, or presentation of information.  McMurtry lets us in gently.

And it's a long book, usually something that irritates me.  But it gives me stuff I like, like this bit.  Call, a sober former Texas Ranger who is recruiting young men for a big cattle drive, has lunch with a mother whose sons he wants to hire:

"This is my varmint stew, Captain," Maude said.

"Oh," he asked politely, "what kind of varmints?"

"Whatever the dogs catch," Maude said. "Or the dogs themselves, if they don't manage to catch nothing.  I won't support a lazy dog."

"She put a possum in," one of the little girls said.  She seemed as full of mischief as her fat mother, who, fat or not, had made plenty of mischief among the men of the area before she settled on Joe.

"Now, Maggie, don't be giving away my recipes," Maude said....

Humor, disappointment, suspense, and ambition, with a mix of characters and eccentrics.  Just like what I try to achieve in my own genre.

Military strategy for the unmilitary

Someday I'll write a big, fat fantasy novel.  I say this, even though I don't particularly like reading big, fat fantasy novels.  Writers like to say that they write books they'd like to read.  I'm sure I could write a BFFN that I'd like to read--the question (and one that's come up a bit too frequently) is whether anyone else will want to read it.

But one thing I do know--BFFNs must have a lot of military activity, and at least one giant battle.  And it stands to reason that those battles will need to reflect the limitations and affordances of historical military combat.  Here is where I hope my deep reading in history will stand me in good stead.  I hope.

I'm not militarily minded and don't gravitate to explicitly military fiction.  But I do like to know how things got done.  Most history writers are either too fanatically detailed or too cursory for me.  What am I looking for?

In The Fall of the Roman Empire, Peter Heather gives an account of military operations after large Gothic forces crossed the Danube and moved into.  He describes how the Rhodope Mountains

...are extremely difficult to cross from north-east to south-west...and movement north and south through the Haemus Mountains is channeled through just five major passes....

And bravo for Heather, there is a nice clear map without a lot of extraneous details, showing the geography and the routes of the armies between 377 and 382.

He goes on, about the Romans.

Heavily outnumbered as they were, the available forces had no prospect of defeating the Goths; so...they fortified the passes through the Haemus Mountains...Some of the passes...are quite broad, but they are all high.

Then he gives an account of how 4,400 Russians held one of these same passes, Shipka Pass, against 40,000 Turks during the Russo-Turkish War of 1877.  For two months, the Romans were similarly successful, but then a force of Alans and Huns joined the Goths.  If one pass was forced, the soldiers at the others would be cut off.

Once the Goths and their allies were south of the Haemus, they could rampage at will.  The only geographic barrier beyond was the Hellespont itself.  This situation led to Valens's defeat at Adrianople.

It's this type of description of terrain and strategy that makes me feel that I understand something.  Using history as a crib, I could write some convincing strategic maneuvering, using what I know of geology, geography, and climate.  And I could make sure it was something I enjoy reading.  What about the rest of you?

 

Your day job is a real job

The most important fact for any of us who think of ourselves as writers or artists to remember is that the job people actually pay you for is real.  Your employers don't care that you're writing a novel, or a song, or making a movie, or really entertaining your Twitter followers.  Or, rather, they care, but not in the positive "we have a real artist working for us!" way you might hope they would.

They care because they think you're goofing off.  "Not doing the job you're getting paid to do" is goofing off, even if you're creating great art while doing it.  And are you actually creating great art?  Be serious now.

Having a job isn't some unique torment you alone suffer.  Poke your head up out of your cube and take a look around.  See all those other people?  They have other things they like to do too.  Maybe they play basketball, or take care of an aging parent, or cook, or play in a band.  Maybe they don't do much of anything, but whatever it is, coming in to work certainly interferes with it.

But they're all here, and they're all working (probably).  So you should be too.  Accept that you're one of us, the workers of the world.  I can't pretend it isn't sometimes bitter and painful.  But it's bitter and painful in a perfectly normal, human way.  You'll find you can accept it, achieve some success in your day career (promotions and raises go some way to making acceptance easier), and still get your own work done.

How fragile is technological civilization? We'll probably get a chance to find out.

Over at FuturePundit, Randall Parker spent some time a couple of weeks ago to go over all the large-scale disasters that shook the 19th century (everything from gigantic volcanic eruptions to solar storms).  His question:  what happens when one of these hits our more complex and interconnected civilization?

In a different, but conceptually related analysis, Charles Stross  asks How Habitable is the Earth, and answers "only in extremely limited places and times":  humans evolved under an extremely specific set of circumstances--circumstances that could easily change. (Amusingly, Stross fools around and uses decerebrate meat puppets as his planetary explorers, and discovers that many of his blog readers take even his jokes with grim seriousness:  clearly a cult in the making, though Stross seems unwilling to lead it).

Years ago, in his novel A Gift From Earth, Larry Niven postulated a planetary probe poorly programmed to seek "habitable areas".  On Mt. Lookatthat, a plateau rises out of an otherwise Venus-like atmosphere, and so humans are sent to settle what is really an island.

The farmers and city dwellers of the dry Southwest take the maximum rainfall ever recorded as the standard, and base their plans on it, though "plans" is an exaggerated word for what they do.

There are always Black Swans, big out-of-norm events.  But there are, more importantly, a larger number of gray swans of various darkness, mostly uncorrelated with each other. Our technological civilization seems to have grown rapidly in a period unusually empty of such events, and treats this unusually wide zone of habitability as normal.  And, aside from a catastrophic black swan (e.g., a major asteroid strike), it can now probably deal with any such event.

But what happens when there are a few gray swans in close succession?  Regular readers know I've been reading about the fall of the Roman Empire (as in this discussion of Ward-Perkins, and this one on Heather).  It's hard to really get clear, because a large number of negative events (plague, tribal reorganization, internal political chaos) came together, not one gigantic one.

We could get a large volcanic eruption and a major solar storm that knocks out communication, during a time of political instability and financial disruption.  Our civilization is not a fragile flower, but it certainly has its breaking point.  With one big disaster you have something to fight and unite against (and write disaster novels about).  Is a group (flock?  herd? --swans don't seem to have been hunted enough for a nifty collective noun to be agreed to) of gray swans a conceptuallly different situation than a black swan?

If we stay in the game long enough, we'll have a chance to find out.

More Shorpy

Shorpy continues to be one of my favorite blogs--"the 100-year-old photo blog" as it bills itself.  Here, a few recent images that struck me.  Each is linked to the larger original on the Shorpy site--to get the full effect (particularly of Winter Crossing, the railcar ferry), you should click through (new window).

A little person wearing a Coolidge ribbon (identified by readers as soprano Hansi Herman, of Rose's Royal Midgets).  What part of cigarette-smoking, fur-wearing, Coolidge-supporting, performing German midget seems politically incorrect to you?

 

 

 

 

 

 

 

 

 

 

 

Detroit, winter 1900.  The heart of the civilization of the great industrial age.  Steampunk has become a weirdly dominant subgenre, and this image shows why, even though no one would actually want to be standing out their amid the jagged ice floes and cutting winter wind, and even though most steampunk tends to the Victorian rather than the American Renaissance--somewhere at the other end of this stands a Stanford White palazzo, and....

 

 

 

 

 

 

This isn't Evelyn Nesbitt, despite my mention of Stanford White.  The original Gibson Girl?  Someday you'll see my mystery novel that takes place in the world of White, Saint-Gaudens, and the invention of the Adirondack style.

Or maybe you won't.  But it's fun to think about.

 

 

 

 

 

 

And, just to show that everything isn't in glorious black and white, a 4x5 Kodachrome from 1942

Are technothrillers science fiction?

On his temporary tor.com blog, Edward M. Lerner (more typically at SF and Nonsense) asks a question:  how does a technothriller differ from near-future SF, if at all.  Somewhere back there, I think, is the income/status issue I've been seeing a resurgence of lately--"why do they have more mainstream acceptance and why do they make so much more money?"--though, to be fair, Lerner never heads in that direction.

Just remember that, with a writer, "and how does that get me a bigger advance?" is the unspoken addendum to any question, kind of like "between the sheets" for Chinese fortune cookies.

My answer:  SF is about the transformation of order, technothrillers are about the reestablishment of order.  In an SF novel, a change, particularly a technological change, moves out into society as a whole, and transforms it.  In a technothriller, changes, even dramatic ones, are confined to the immediate area of the characters and the plot.  In an SF novel, if dinosaurs are recreated, their recreation and the technology behind it gets used in war, in labor, in abstruse spiritual transformations.  In a technothriller (Crichton's Jurassic Park books), they stay on their island.

The containment has several related favorable features, as far as a mainstream reader is concerned.  Reactions, mores, and cultural features are recognizable.  And, as a result, the writer isn't tempted to spend time and energy making up stuff (changing the way people pump gas, or giving them weird new bedroom furniture) just to show that we're in The Future.  And the writer can't hide behind the chrome, and has to focus on the engine--the plot.

Regaining a literary reputation is not for sissies

It would be easier not to lose it in the first place, of course.  To get a reputation back, you have to do everything.

But you have a full time job and other responsibilities.  You don’t have time to do everything.

So you pick a handful of high-priority projects and try to get them done.

The problem with working multiple projects is that you can always find something more interesting to do than the project you're currently working on.  That last 10 - 20 percent is tedious and unrewarding, and there is always some fresh young project sashaying by that just seems much more attractive.  This is as true at work (“another round of corporate approvals?”) as in your writing (“I can’t believe I need to edit that again”).

Within my hour a day, there is only time to focus on one thing.  So, which is it?  Revise that story?  Write a new story in time for the next workshop session?  Tackle the revision on that giant novel manuscript?  Or sit around and think up some great new concept that someday I might work on?

At some point, each of those needs to get done:  an SF writing career really does benefit from a mix of novels and short fiction.  You don’t want huge time gaps between published works, and keeping both pipelines filled is enormously difficult.

The real trick is to actually be working on something every day.  Dithering, fiddling, agonizing, and woolgathering are all time-consuming activities.  They can easily take up that hour a day.  They will, unless sternly fought back.

Despite my best efforts, they sometimes do.

Am I getting it done?  Not perfectly, but better than I used to.  I’ve dug through a stack of old and new written stories and revised several (discovering, to my dismay, that several of them had waited quite a while).  I’ve written several new stories (which, curses, must now be revised, and so have just migrated from one stack to another rather than leaving my office).  And I have a large draft of my next book, After the Victory, and an outline for revision.  I’ve put together a proposal for it, but haven’t quite dared start the major revision—this is a single-minded effort of quite a few months, and I wanted to get my story pipeline filled.

So, we'll see.  There are no large secrets, only many small ones, and maybe I've learned a few.

L. Sprague de Camp and the uses of history

Recently I was listening to Garrett Fagan's lectures on Great Battles of the Ancient World (a Teaching Company class--I recommend them highly for light education while sweating), when I learned that Assyrian methods of siege warfare entered the Greek world through encounters with Carthage, during the wars over Sicily.  A fun topic for a historical novel, I thought.

Then I did a little research and realized I had been beaten to the punch, by L. Sprague de Camp, a youthful favorite I had not thought of recently.  In his novel The Arrows of Hercules, he deals with exactly those events, through the person of an engineer in the employ of Dionysios I of Syracuse.

De Camp wrote science fiction, fantasy, historical fiction, and historical nonfiction.  He was one of those debonair globe-trotting polymaths that sometimes find a congenial home in genre fiction.  His historical novels are the complete opposite of bodice rippers--they are more about bodice inventors ("hey, do you think we could take that baleen stuff and use it to....?")  Like most of his books, TAH is episodic and doesn't have a strong plotline.  Like real history, this happens, and then that happens.  Sometimes there's a connection, and sometimes there isn't.

Even the characters described as passionate and impulsive are quite measured in their emotional reaction.  And de Camp's attitude is that engineers are pretty much engineers, now matter what era they turn up in.

So don't look here for a Stephen Pressfield-style description of maggoty corpses.  There is some brutal violence, but it is over quickly.  I'm not sure there's a spot in the market for de Camp's  charming, informative witnessing to interesting events, but something like it should still do.

Most historical novels where someone experiences great events or a specific culture are told from the point of view of a time traveler, even if he is not literally that.  Blackthorne in Clavell's Shogun comes easily to mind--he's described as a seventeenth century Englishman, but he's clearly from the twentieth century.  Similary TAH's Zopyrus.  In Lest Darkness Fall, one of de Camp's best books, it is explicitly a time traveler who pops into the Rome of Late Antiquity--the period I've recently been reading a lot about.  My interest in it might actually stem from that book, which made a big impression on me in my youth.

I've never written a historical novel, but I think this era, between the great era of Sparta and Athens and the advent of Alexander the Great, has some promise as a setting.

Knowing history: the late Roman Empire

History informs much of my work, and makes up a lot of my free reading.

But it's easy to think that the past is a story that's been told to us, whereas it really is just a few syllables here and there, vaguely heard through a gale.  As part of my reading on the fall of the Roman Empire (not great scheme behind it--it's just that a lot of good books have recently come out on the subject), I recently finished Peter Heather's The Fall of the Roman Empire, which, really, is a detailed history of the period 376-476 with a few halfhearted attempts to show how the whole melancholy thing could have come out differently.  I don't think Heather ever convinces himself.

But he's extremely clear on what we know, and what we just guess.  The sources are, as always, fragmentary and partisan.  He  has his opinions on who is trustworthy, and whose testimony should be regarded with suspicion.  It's a nice glimpse at the history workshop, where those nice seamless narratives are put together.  And Heather's characterization of what was really a grim bureaucratic tyranny, which he compares to Soviet party congresses, is enlightening.

Attila, of course, plays a prominent role.  But the commander who really caught my attention was the Vandal leader, Geiseric, conqueror of North Africa, previously unknown to me.  Escaping a difficult situation in Spain, he shuttled his followers across the Straits of Gibraltar into the remote province of Mauretania Tingitana in 429.  He then moved east (St. Augustine died in the besieged city of Hippo Regius), and conquered what was the richest province in the Empire.  This conquest was a major nail in the Empire's coffin:  the revenues from this province helped pay for the army.

In 455 Geiseric launched a naval expedition which sacked Rome, much more violently and destructively than the relatively benign looting of Alaric back in 410.

In 468, an huge fleet sailed from Constantinople to reconquer North Africa, but was destroyed by fireships, much like the Spanish fleet of 1588.  Heather indulges in one of his wishful counterfactuals here, considering what the fleet could have accomplished if the wind had been blowing in the other direction.  Maybe.  Geiseric was clearly a formidable opponent, and his descendants ruled his kindgom through peaceful succession until Justinian's conquest in the next century.

If Geiseric were on the "right" side, he'd be someone we knew about.  His political and military talents were incredible.  He not only conquered and destroyed, but built a functioning and stable kingdom.  If Justinian hadn't come along, what would have become of a wealthy Arian Vandal kingdom in North Africa?  Probably conquered by the Arabs as they swept on their conquests, like everywhere else.  But maybe not....  There's a counterfactual for you.

Choosing a day job

Don't quit your day job.  It's the oldest piece of advice in the writer's life plan.

And, for most of us, it's a good one.  Some writers are incredibly productive, flexible, and tolerant of pain, and can make a living from their writing alone--the best way to figure out if you can handle it is to read Kristine Katherine Rusch's excellent Freelancer's Survival Guide.

Most of us can't.  I've talked to successful writers with decades-long careers who carried credit card debt and had no money in their retirement accounts.

What I thought when I heard that was:  "Why don't you just get a job?"  But I didn't say it, because I didn't want to sound like a parent, or a non-writing friend, or just a clueless buffoon in general.  That question has certainly been asked before.

But it's still a legitimate one--and one I actually now have standing to ask.

I write slowly, with undependable quality (I throw out much more than I finish), and then edit endlessly.  As a result, my end productivity is low, and the final product eccentric and hard to sell.  And, as I know from experience, more free time translates into only marginal increases in my productivity.

So I am systemically unable to earn a living from my writing.  It took me a while to face this.  After a lot of work, thought, and planning, I have found that a disciplined few hours during the week actually generates stories and novels.  Figuring this out took some time.

And during the day I manage marketing programs, write copy, think about customers, and learn more about whatever field I'm currently pushing--right now, sophisticated financial services to investors in multifamily housing.  I work with focused, intelligent people who are completely different than me.  It's challenging, and, a lot of the time, it's fun.  And I've gotten pretty good at it, which has its own satisfaction.  It also lets me understand how people do business, something completely alien to me before.

So, don't quit your day job.  But make sure your day job isn't a miserable soul-sucking torment.

And make sure it has a good health plan.

What question does my blog answer?

I got a tip from a blog I like to read:  Penelope Trunk's Brazen Careerist.  I'm out of the target demographic for her new social network startup (actually, I'm pretty much out of the target demographic for any networking model likely to be successful), but I love her career advice--and her rules for blogging.  One thing she said was:  a good blog should answer a question.

I like reading blogs, and I like writing my own.  But I like being read, too.  Just posting random bits of this or that just isn't getting to what I want to say, or what anyone wants to read.  This observation of Ms. Penelope's struck me particularly (thought she has a lot of other useful advice too).  What question is my blog answering?

I once had a decent career writing science fiction.  I was relatively successful, despite an absence of awards, and really liked it.  Circumstances kept me from moving that forward, and I've slipped back to obscurity.  Now I am restarting my career.  I'm middle-aged, have a family, and have a demanding day job that takes a lot of work and attention.  I also have a decent social life, like to garden, spend a lot of time in physical pursuits (it's a beautiful fall day today and once I post this I'm on my bike), spend time with my family, and love to read.  But I'm getting my writing done, have a book coming out, and am working on, and trying to sell, my next.

How am I going to do it, when I am not really all that energetic, that organized, or that smart?  That's the question I want to answer.  I may disappear again.  I may hold on by my fingernails.  Or I may actually have some success.  I'll let you know, right here.

 

When will we regain our lost WordPerfect technology?

Years ago I used a word processing program called WordPerfect.  I liked it, and only switched to Word when I had to.

I established a reading list in WordPerfect, and when I transferred it to Word I realized a problem:  Word has almost no sort capability.  Excel, also, has almost no sort capability.  WordPerfect could sort by word, field, line, paragraph, and it could sort from the last word, the next to last word...whatever you wanted.  A list of names could be sorted by last name, no matter if there were middle initials, multiple middle names, whatever.

That was twenty years ago.  Until recently I would port my Word document into WordPerfect, sort it, and bring it back.  But I switched computers and lost my WordPerfect (in DOS!)  I have the same problem at work whenever I have mailing lists with full names in one field.  It's a pain to get the last names sorted.  It would seem that someone would provide the capability (short of going into a database program).  Why is this?  Certainly I'm not the only person who has various sorting needs with various lists.

I'd buy a used or old WordPerfect package, but they turn out to be ridiculously expensive.

I have to say, I find this odd.  It's as if we once had nonstick cookware, but then the company that made them went out of business, and we had to go back to using a lot of oil.

Apples: the ease of misunderstanding the past

There is a farmer’s market near where I work.  I always go, and at this time of year, the stands carry a huge variety of apples.  Some are available most of the season, while some have a short harvest season.  Apples have been grown in New England for centuries, and apple cider used to be the prefered light alcoholic drink around here.

But when I look into the various apples I try, I find that most of them do not have a particularly long history.  A favorite, the Macoun, came about as a cross between two older apples, the Mcintosh and the Jersey Red, and was only named in 1923.  Even older varieties have been subtly bred to improve disease resistance, separation of the stem, disease resistance, simultaneous ripening, etc.

When we read a novel set in a previous era where people eat apples (and if it's set in New England they certainly will) our understanding of what they are eating and how they get them is incorrect.  The past is another orchard.  "Good keepers" were more important in an era without refrigeration and nitrogen-filled warehouses, even if they didn't taste particularly good.  And the trees they got the apples from weren't those comfortable dwarves you see it a pick-your-own orchard.  They were...well, they were trees.  You could fall out of them and kill yourself.

It's easy to forget how much work had to be done to get us from then to now.  Generation after generation, busy agronomists and farmers have competed to create apples that will appeal to apple eaters, and be cheap and efficient for apple growers to produce.  So raise a Macoun, or a Spencer, or a Northern Spy and, before you take a bite, and give thanks for their labors.

The Savannah Disputation

The other night I went with my playgoing friends to see The Savannah Disputation, by Evan Smith.  As I mentioned a few months ago, we have been regular attendants at one of our two large local theaters, the Huntington Theater Company, and have been dismayed by the hash of expensively produced mediocre-to-bad new plays, and respectful treatments of classics that we have been served.

So far, going to the SpeakEasy Stage Company has been a great decision:  this play was crisply written, funny , and even profound.  Which is to say, it was not an embarrassment.  Going to the Huntington Theater was often just plain embarrassing.

The setup of The Savannah Disputation sounds kid of sitcommy, perhaps unavoidable in a world where TV has sucked up all the best talent, and has the resources to relentlessly explore every even vaguely realistic narrative form: two older Catholic sisters, one grumpy, one sweet, are visited by a perky Evangelical missionary, find themselves unable to justify their faith against her relentless talking points, and so drop a priest friend into a theological cage match without warning him.

This isn’t one of those “stories about nuns” Catholic plays (quite popular in Catholic Boston).  This is a genuinely funny examination of what we base our faith on, and how we all use facts to bolster what we already believe.  There is real loneliness, real desire for connection, and real fear of death under the humor.

I don’t know who Evan Smith is, and there is little about him online.  He doesn’t even have a Wikipedia entry.  No web site.

Evan Smith is a throwback, in other words: a literate younger person (I think he’s in his 30s) who actually enjoys writing plays and, what’s more, is good at it, quite unlike the majority of new playwrights produced by the Huntington Theater Company. 

Through October 17 here in Boston, but it seems to fairly popular in various places:  a one-set four hander with two good roles for older women, one for an older man, and one for a younger woman, and so easy to put on.

Biking with lunatics in Sao Paolo

Treehugger has an interesting piece on speeds of various means of transportation in Sao Paolo (via The Infrastructurist).  It had the merit of testing various types of bicyclist (including an untrained cyclist who stayed on side streets) against buses, cars, helicopters, etc.  Most contests stack the deck by not including regular folks on regular bikes (a fast cyclist did in 26 minutes what a regular guy did in 66 minutes, so you can see what effect that has).  A delivery trained cyclist and a trained cyclist on a fixed-gear bike beat even the helicopter six plus miles across town.  Pretty much everyone with control over their speed beat the car (82 minutes).  Even a bus beat the car, so Sao Paolo must be both a commuting nightmare, and have some separated bus lanes.

I ride a fixie about six miles to work every day, so I appreciate that.  But bicyclists are annoying and smug, and everyone hates them, and I understand that.  I bike every day, all year, in Boston weather and traffic, and find it normal, and don't get why other people would like sitting in cars, but I know I am in a minority.

But even I found the bicyclist in the video scary.  He's riding through tunnels, on busy highways, at night, with no taillight or reflective gear.  Sao Paolo looks like a great place to get killed.  It's new.  Boston is old, so the deranged street patterns actually make bicycling easier.  Cars are clearly the intruders here.  But only a madman would put his butt out on a bike in Sao Paolo.  My personal opinion, anyway.

Plus, the guy in the helicopter wasn't really trying.

Learning the ropes of book marketing

Last week I took a course at Grub Street, a kind of writer’s club in downtown Boston, on how to promote your book.  There was an enthusiastic group of about 20 students, most of whom had a book of one sort or another coming out in the next year.  Given what I see as the demographics of literary production in general, it didn’t surprise me that only four of the students were men.  The book subjects, fiction and non-fiction, ranged all over, but certainly with a plurality about family relations.  One of other men had a superhero-related book, and there was me, with my AI-hunting suspense novel.  But no one made fun of us.  At least not while we were there.

The class was taught by the enthusiastic Jenna Blum, and I hope I learned something from her.  Through relentless hustling, she turned a poorly-selling hardcover into a best-selling paperback, though just listening to her activities was exhausting.  Relentless self-promotion is, above all, relentless.

For me, I have to balance not only the fact that I have a full-time job, but also the need to write the next book, and short fiction as well.  Several of the participants said they would devote most of their time to promoting their books.  Jenna is taking the next year to promote her second novel, traveling around the country, chasing storms (the book's subject), and managing a bewildering variety of tie-in activities.  That was all more inspiring than useful to me:  there is no way I could manage anything like that.  And if she finds this while Googling herself:  thanks, Jenna Blum!

My goal:  make sure that anyone who could reasonably be expected to enjoy a snarky AI-hunting novel with a lot of suspense knows about Brain Thief and gets a chance to give it a try, particularly those who would not usually try science fiction.  Of all my books, it’s probably the most accessible for those from outside the field.

 

Hub on Wheels

This morning I got up before six AM and headed down to Government Center, in downtown Boston, to participate in Hub on Wheels, a ride all the way through the city, on closed-off roads.  It was drizzly, and the forecast was for heavier rain, but we were lucky, and the rain stopped partway through.  Storrow Drive (along the Charles River) was closed off in both directions, and formed the 10-mile route.

It's been a while since I did it.  It was fun and relaxed, and went through the Arboretum and Forest Hills Cemetery, as well as on a variety of bike paths I'd never been on.  Down in Mattapan the route went on a bike path paralleling the stretch of the Red Line that still runs old PCC cars (over 60 years old by this point), and one went by going in the other direction.  Also in Mattapan, a couple was having a screaming fight in the street, ignoring the steady stream of bicyclists going by.

A nice 50 miles.  If you're in Boston next year, I recommend you give it a try.