Once upon a time, I spent many long years on a now-abandoned multigenerational family novel with storylines set in three time periods. I knew the date of every scene, and those dates were all locked together by the timeline of both the fictional family and real world events. One setting was pure history as far as I was concerned, one was a recent past that I'd lived through, and one was the near future. When I wrote the first draft in 2007, the familiar past era was closer than the imagined future. As I embarked on repeated revisions, on and off for more than a decade, the near future setting grew nearer and nearer. The year it took place (you can guess where this is going) was 2026.
It's a little strange to be in 2026 for real now, after spending so much time in my fictional version. (Of course, existing in 2026 is strange enough on its own.) But the strangeness is mainly numerical, and not from writing any vividly bold predictions about what life might be like now. In early drafts, most of my worldbuilding extrapolated from technologies I thought were cutting-edge. That tended to mean I accurately predicted how those technologies would be used about 18 months out, often before I finished a given draft. As my actual timeline barreled toward my near future, I gave up on any science fictional inclinations.
The major worldbuilding in my 2026 storyline was about a significant earthquake striking the Bay Area, something I never wanted to be predictive about. (But to make sure I'm not psychic, for the record: November 4, 7.5 on the Hayward Fault.) I also wrote the almost-throwaway but important-to-me line "The president was on her way to Oakland" way back before there was any particular woman (from Oakland, no less) who I hoped would be in the White House now. Sorry this game isn't more fun!
Anyway, that novel hasn't been in play for a long while, for many reasons, and that is even less likely to change in a future that's become its past. I only bring it up again to commemorate the weird space 2026 occupies in my writerly mind. And as a cautionary tale for other slow writers planning stories set at a particular point in the near future.
At present, I'm applying my slow writing to a different project. It's the novel my recent blog posts refer to, for some value of "recent" and "refer". I know I haven't said anything about it for months, and I've never shared many details. (Another thing that's strange is having a decade of blog posts about a novel that never went anywhere.) But I've been working steadily away, writing sentences and scenes that may eventually cohere into a finished novel.
This one is set entirely in the future. I've repeated the possible mistake of specifying a year, but I think I'm safe for not catching up this time, since the year is 2132. Spending imaginary time in that farther-out future is fun, and challenging, and definitely requires more meticulous extrapolations than I've ever made before. Not that I'm honestly trying to predict what I think the world of 2132 will be like. As Ursula K. Le Guin wrote in an often-echoed sentiment, "Science fiction is not predictive; it is descriptive." She wrote more about the idea than just the pithy sentiment, and I recommend the rest of her 1976 Author's Note to THE LEFT HAND OF DARKNESS.
I reread Le Guin's classic novel this month, and my book club had a wonderful conversation about it. Also in April, I turned 51 and had some delicious birthday celebrations, including a cake that I enjoyed baking. I got to show the world the sweater I've been knitting since last summer. And early in the month, early in the morning, I was woken up by a nearby earthquake that didn't result in anything besides the rude awakening. That can be my quake for 2026, thanks.
Good Stuff Out There:
→ At Literary Hub, Miranda Shulman describes What Knitting Has Taught Me About Writing: "When I say that every stitch, every word, is progress, I mean that every stitch, every word, is a valuable learning experience, not that they are permanent. When I'm knitting, I'm often following a complicated pattern translated from Dutch to English. It usually takes a few tries to understand what's being asked of me, and if I'm knitting in a dark room (like a movie theater or a dimly lit restaurant) I'll probably make a mistake. Then again, when I'm knitting on my couch at home, I'll also probably make a mistake. There's no way to knit a sweater faster than the time it takes to create the right stitches and understand the pattern. You have to make all the mistakes and be okay with re-doing it until it’s right. That's the process of making. That's dedication to craft. That's discovery."
No comments:
Post a Comment