the random ponderings of e. f. danehy

wherein erin discusses writing & young adult fantasy (using much parenthetical commentary & tangential ramblings).

Summer’s end and climbing

Tuesday August 31, 2010

It doesn’t seem like 31 August. Really. Okay, maybe it’s 95 degrees out there (and will stay 95 degrees for a number of days) but other than that it hardly seems like the summer — what I think of the summer, of July and August — is over.

We’ve been busy, on something of an internet and actual vacation these last few days (so I apologize for the silence here!), but I’m pretty sure we needed a break from the city. We took a trip down to Baltimore this past weekend and had a fantastic weekend with friends. There were adorable pugs, seafood, beer brewing (with much sighing from me), a stroll through the Inner Harbor, wedding talk galore, and — best of all — climbing. Indoor rock climbing. The husband and I had never been — well, he had done some as a kid, but I’d never been — and we came away genuinely surprised by how much we enjoyed it.

IMG_0829

IMG_0869
Our friends have been addicted for years and gave us a casual introduction this weekend. The moment it was over, the husband started looking into climbing gyms in New York City, so we could continue climbing when we returned home. He was so excited at the idea of getting out of the house while simultaneously spending time with me and working out that he insisted we buy gear under our friends’ guidance before we even left Baltimore.

Yesterday, two hours after our bus dropped us off in New York, we were at Brooklyn Boulders taking our first official belay lesson. After we were given the okay, we started climbing in Brooklyn. It was challenging, fun, and it’s something to do together that’s more engaging than going to the movies and cheaper per visit than going out to most restaurants. Before we were even done for the afternoon we agreed we had to return as soon as possible.

IMG_0913

So I think climbing is our new official hobby. While we can only ski a week or a weekend here or there in the winter (and we’ll always be doing that), we can climb year-round. Even though summer is over in some senses, the fun will most definitely continue.

Computer cursed.

Friday August 20, 2010

As far back as I can remember, I’ve known how to use a computer. As a small child, I could run a floppy diskette program through DOS as easily as I could crack open an Easy Reader. (Some of you will not remember floppy diskettes, or Oregon Trail and its brethren, and that’s okay.) I never remember being taught things, not specifically. When I had a question, I’d ask. Mostly I would troubleshoot. When I was little, we had almost as many computers as people in my family. I remember watching my father solder circuit boards and thinking how cool it was that my dad knew how to build a computer from scratch. By the time computer class in elementary school was mandatory, I knew what I was doing — better than a lot of the girls. I was the only kid in one of my early computer classes who knew what Control-Alt-Delete did, using it like some kind of magic combination to unlock a frozen computer. This was never strange to me.

My parents gifted me with my first desktop computer at age twelve. It was built from a combination of new components and older ones my father had lying around the house, and I adored it. When we first got dial-up internet, we couldn’t hook up my computer, because there was no phone jack wired in my bedroom, but I didn’t need this slow, laborious thing called the internet. I just needed a word processor and Microsoft Encarta, and I was off, writing my first attempts at novels. That computer, without a CD drive, with a 15″ CRT monitor that was as heavy as the tower, lasted me through middle school and high school, until it finally started gasping its last breaths when I was a senior in high school. I loved that computer.

After that, the computer disasters started.

For college, my parents bought me a Toshiba laptop. In October of Freshman year, it imploded. Blue Screen of Death. It was two months old. Because it was so shiny, the thought of backing up my data had never occurred to me, especially not by October. I lost all of my documents and files for the start of Freshman year. I ended up having to send in my Toshiba to be serviced (it was under a 1 year warranty) and they wiped my harddrive. “An unexpected malfunction. You couldn’t have anticipated it,” they said. Once it was back in my care, I treated it better than any possession I had ever owned, and learned all I could about these kinds of mishaps to prevent one from ever happening again. Because this was at Carnegie Mellon, I was also surrounded by a horde of talented techy folks (both employed by CMU in their computer help center and not) who were willing to take a look, offer me advice, teach me a trick or two. By Sophomore year, I had it figured out. Then, in October of Sophomore year, almost a year after the first problem, there was a second. This one was an implosion. Irreparable. The harddrive made a sound like a dying cat. It was out of warranty and there was no hope. They told me it would be almost as much to repair it as replace it. So I bought an entirely new laptop, an HP.

The HP and I had some good times. I treated it well, always on a flat, clean surface, never leaving it in standby; I kept it clean of viruses and spyware, all of that. I knew computers. I understood the principles. I was as well-versed in the basics of troubleshooting as any amateur could be. So when Blue Screen of Death reappeared Junior year, I was ready. I had weekly backups of my data, some stored on the internet, some in hard copy. I had the original boot CDs and I was able to wipe and reinstall Windows and solve the problem all by myself. I never figured out why the Blue Screen was out to get me, but it seemed to be hunting me down. This time, I was ready, and it was hardly an issue worth crying over. Boom, problem solved.

One day, nary a few weeks before the end of the (free! Included!) 1 year warranty on the HP, I couldn’t turn on the computer. I started panicking. I’d done everything right. I called HP, and they told me it was an issue covered by warranty. I sent in the laptop to them. They sent it back, fixed. Data — irrecoverable. But I’d backed up. It was okay. Not something I could fix, again a problem out of my control, but it was still okay. It was fixed.

(Are we keeping track of the disasters? That’s two Blue Screens of Death and two implosions, in two computers.)

When I graduated from college, my gift was a spiffy and souped-up HP desktop. Their customer service had been top notch, but the laptop was outdated. I needed a new machine. I started a new regimen of regular back-ups and good practices (consistent harddrive crud wipes, spyware/anti-virus cleaners, etc.) and… in the course of the first year of ownership, I had two Blue Screens of Death. Windows wouldn’t load. It wouldn’t recognize pieces of its hardware. I went to bed one night having just shut down the perfectly fine computer, then woke up the next morning to a Blue Screen of Death. Inexplicable. Random. It was out to get me.

Two. In a year. One resulted in a malfunction of a piece of hardware. Snap, no more DVR capability. Thank you, HP. The other was almost comical in how much of a non-event it was. Still forced me to wipe and re-install Windows and I lost all of my data, but I’d been backing up. It wasn’t a catastrophe. I solved it myself. That did not stop the husband (then fiancé) from looking at me askance and suggesting maybe I stay away from his computer. Or maybe let him have the new computer to play with, and I’d take his college laptop. Just in case. Because it was clear to both of us that my curse was not going away.

Flash forward to April 2009. As a wedding gift to me, the husband purchased me a Dell netbook. I hadn’t had a spiffy laptop since the HP started its downhill age decline, and I needed something to take to cafes to write on. “It comes with a year of warranty,” he said, debating whether or not we needed to invest in more. Compared to the cost of a netbook, buying the warranty was exorbitant. “Well,” the husband said, “If something implodes, it will happen in the first year.” Statistically, that has always been the case, I thought. Always. “Yep. One year is good,” I agreed. I’d dealt with having to send in both the Toshiba and the HP while they were under warranty in that first year of ownership. I had a track record. This was going to be fine.

In April 2010, two weeks after the warranty on the Dell expired, it decided it was going to make a MMRHHHHHMRHHHHHMRHHH sound one day instead of booting up. I called Dell. They told me my laptop was a goner, that if I was under warranty they might be able to do something, but it’s pretty much dead anyway. Sorry.

I turned to the husband, in tears. “I am cursed with computers. CURSED. I treat them well. I know what I am doing. I am techier than most English majors! What is wrong with me?!”

We discussed it and agreed, well, maybe it was finally the time to convert to a Mac.

I’d resisted because of the price tag but also because of my track record with computers. Something always happens. Always. But Macs have a track record, too. Their harddrives don’t implode randomly. There is no such thing as a Mac OS Blue Screen of Death. No such thing. This… overjoyed me. That, and I’d been obsessing over their product design for years, and every Mac owner I knew was immensely happy with their purchase.

We purchased the Mac in May 2010. During the checkout process, the husband says, “AppleCare protection plan. What do you think? None? One year? Three years?” I stared at him. “What do you think?” We bought a three-year plan.

Yesterday afternoon, at about 5:35pm, the six-month-old kitten was in a crazy mood, one in which she must pounce at all inanimate objects in the apartment as a point of asserting her dominance. I was in the kitchen, grabbing a drink, when I saw her pouncing on the bed. I also saw I had a flashing message on the laptop screen from the husband, at the desk just past the bed. I went over to the laptop, set my drink down, and answered the message. The kitten chose that moment to pounce, jumping across the desk — and knocking over my drink, spilling it across the MacBook Pro’s keyboard.

I stared in dumbfounded disbelief as the screen went dark and the liquid pooled on top of the keys. Then I leapt into action. I pulled the plugs, wrapped it in a hastily-grabbed towel, and submitted a request to Apple for service within three minutes. (The other desktop was on; shh, we’re techy people.) Apple called me immediately. “How are you doing today, Erin?” the service man asked cheerfully. “Five minutes ago, I was great,” I told him. “Then my cat spilled my drink across my keyboard. I’m not doing too well right now.”

He talked me through it, getting me to direct a fan at the keys, telling me not to panic, that even if the motherboard got fried, it’s totally fixable, and my harddrive is undoubtedly safe and secure. He made an appointment with a specialist at the Apple Store for this weekend, warning me to keep the fan on the keyboard for the next 24-48 hours. I giggled, with relief, and told him how happy I am that I invested in the AppleCare Protection Plan. “Oh, by the way, this isn’t covered under your AppleCare Protection Plan,” he said. “Spills, or drops, any sort of accident. We only cover hardware malfunctions.”

Blue Screen of Death, I think, where are you when I need you? Windows machines and my luck with your consistent harddrive failures, where are you?

In reality, I started crying. The Apple guy went a little quiet, talking about the weather, asking what it’s like in New York. “Warm,” I told him. “That’s nice,” he said. “So, what do you do for a living?”

“I’m a writer,” I said. There was silence on the line. I could almost feel the Apple guy connecting my profession with the gurgling MacBook Pro in the corner. He could probably hear my sniffling as I started mentally calculating the cost of fixing this, out of warranty, when all we bought the warranty for was to protect us against the unexpected — this, in a way. But we hadn’t thought we’d adopt a kitten when we bought the Mac, never dreamed we’d have an accident like this. Then the Apple guy said, “Well, um, your appointment is all set. Good luck.” We hung up.

When I stared at the laptop, filled with sticky beverage, tiny desk fan set on its frame whirring quietly, I started bawling. Crying as if I’d lost a family member. To my embarrassment, I’ve cried every time I’ve lost a computer. When the netbook died, it was like I’d lost a limb, an extension of my arm, like all of my writing went with it, despite its safety net. This time, though, was the first time with the kitten. The little, innocent perpetrator of the accident. I was bawling, standing in the kitchen, feeling completely helpless, and the kitten wandered up along the countertop and put her paws on my shoulder, sniffing at these things called tears. I realized I hadn’t yet cried in front of her. What reason would I have had? She started licking the tears off of my cheeks and it could have been scripted, it was so adorable. (Then, an hour later, she tracked poop from her litter box across the apartment floor… then across the cream-colored bed linens… necessitating a bath that neither of us wanted to endure. Yep, she’s a kitten, all right.)

I’m cursed when it comes to computers. Ever since that first laptop purchase, they’ve broken on me. In warranty, out of warranty, problem not covered under warranty. There’s no explanation to this string of bad computer luck. The husband, even techier than I am, is confounded. Our families shake their heads and remind us that so long as the data’s backed up, it’s only a tool, not the living entity I keep thinking my computers are. It’s funny. Some people are into cars, or into designer clothes, or into tasteful art — we’re into computers. And I have a black thumb when it comes to them. What luck.

I hope Apple can fix my computer this weekend. I’ll keep you updated.

On vacation at home.

Wednesday August 18, 2010

Writing Workshop Wednesday will be on vacation until September… like the rest of New York City. It shall make a triumphant return after Labor Day!

Unlike the rest of New York, however, my husband and I aren’t taking a chunk of time off this month to do anything interesting. We’ve taken one weekend trip already and we’re planning another, but since we’re skiiers, not beach folks, we tend to hang out around the house this time of year rather than go out of town. We also have the kitten who, being only six months old, requires more attention than an older cat. So like new, paranoid pet parents, we’re not taking any far-away trips any time soon.

But I have been going on “vacation” in a manner of speaking. I’ve been devouring books. The past three days have been occupied by The Hunger Games and Catching Fire by Suzanne Collins. Those are some serious thwwwp books! Mockingjay comes out next week and I am very, very excited. (I preordered it weeks ago. I’m hoping the delivery guy gets it here on the same day.) I’ll be twitching until then. *twitch*

My to-be-read list is long. While I am trying to prioritize books I haven’t read, I keep getting interrupted by the desire to re-read books — and then there are the two writing projects that keep calling to me. Very different in characters, setting, scope. I keep getting snippets of dialogue for them as I’m washing the dishes or in the middle of a scene while reading. Just — bam, insert my characters into my brain, insisting on a little bit of dialogue. Drives me crazy but at the same time, this is how it always happens. Until I get the whole thing out on paper (or, well, metaphorical paper on the computer screen) the characters will keep popping into my head and running through their lines over and over like actors in a play until I just write it simply to get it out of my head. Once it’s out of my head, there’s relief. For a little while.

*twitch* Is it Mockingjay release day yet? No? Sigh. *twitch*

So my vacation isn’t much from a physical leaving-the-house standpoint, but when I’m sucked into a good book I may as well be far, far away.

What about you? Are you reading and/or are you actually leaving town this summer?

Writing Workshop Wednesday: Poetry

Wednesday August 11, 2010

The Wednesday workshop wisdom continues! This week…

Poetry workshop take-aways // or, why this novelist kept taking so many darned poetry workshops.

I think in novels. As a kid, I thought, Oh, I think in stories. No. I learned later: I think in novels. In my first workshop at 15, I told my advisor that I couldn’t write a short story. Couldn’t. Couldn’t. “I write long things. Um. Novels. I think in novels. I can’t make it short. I can do chapters, if that’s okay.” That wasn’t okay. I was coaxed into writing stories that… read like chapters. My advisor finally coaxed me into making my final project a “novella.” But it still read like half a novel. By the time I got to college and realized that short fiction was the name of the workshopping game, I sighed and got to work learning what this short story thing was all about. In the meanwhile, I signed up for poetry classes. Poetry. Verse. Shakespeare. I knew what a sonnet was, thus, I could write poetry. WRONG. But those workshops taught me so much. This advice is hardly a substitute for what I learned, and may seem obvious, but it absolutely changed the way I thought about writing fiction — and about poetry. By learning to write it, I learned to read it, to appreciate a poem written well (like those of a former classmate, whose work I adore). Admittedly, the poetry I wrote for workshop reads like a novelist wrote it. (It’s also terrible.) Which is [yet another reason why] I write novels.

Besides the fact that poetry is (1) beautiful and (2) absolutely worth reading, you novel-reading people you! these were some of my biggest poetry workshop take-aways.

1. Words are beautiful.

So is the way a set of words can be strung together, the sounds they make when they smack and rub and brush against each other. Words are alive, alive on the page and in the mind of the reader. So many writers seem to use words as a means to an end. Yes — words are the vehicle by which you tell your story. But paying attention to diction, to image, to the particular words you use and how you string them together is an often overlooked part of novel writing. (And yes, paying attention to words is also a pursuit better left to revisions, not first drafts.) Most novelists are so focused on plot, on character, that they forget novels are built with words. We have more room to waste words than a poem in our 80,000 novel, technically speaking, but why should we waste a single word? Why? There’s no good reason. None. Words are beautiful and they deserve to be used well.

2. Image, image, image.

String together images as well as actions. Build images as well as dialogue. When we read we build an imaginary landscape in our minds, we populate it with the writer’s words and the images they draw with those words. Too much exposition and not enough grounded image loses my attention. Too much dialogue without rooting me firmly in the scene distracts me.

Showing versus telling, to me, is that difference between rooting me with image and giving me exposition. Telling me, “Anna’s father beat her when she was young” is very, very different from giving me the visceral recollection of a slap. But — images come with intensity, with meaning and depth. Images are immediate, are sensory, tangible things. Sometimes an image is too strong and exposition may be the better choice. But I hate to be told a crucial bit of information in a casual, throwaway bit of exposition when it can be relayed with an effective image or even a strong bit of dialogue (and “voice” is related to image, because I feel voice).

Images don’t need to be paragraphs and paragraphs and paragraphs of scene-setting detail. Too much image, too many adjectives and clunky nouns can overload an image. Too much image without enough meaning, depth underneath it. Images can be brief and still have strength. They can be slices of a life, picked out by a discerning eye, weighted with the promise of story.

Novels, as a medium, are not built around images as directly as a screenplay is built around image. Not even poetry needs image the way film needs it. But to ignore the effectiveness of well-placed images is to deflate the potential power in a scene.

3. Space is a tool.

Physical distance on the page can allow for emphasis. Where you choose to break sentences, add commas or semicolons or emdashes–these breaks influence the way your words are viewed, are digested by your reader. Judicious use of space is a subtle tool in any writer’s arsenal, regardless of how long their work. This goes for chapter breaks and section breaks as well. Those breaks can and should be regarded as tools, not just “breaks.” Space is a tool! Use it.

But don’t abuse that space.

With lots of dramatic paragraph breaks.

Because after a few instances, it looks silly and loses the emphasis you’re going for. Like the ellipsis, or the exclamation point, paragraph breaks for the sake of drama should be used sparingly, or at the very least, pay off for the reader.

4. Repetition. Repetition is a tool.

But it’s also one of the easiest tools to use too often, too much, becoming annoying rather than effective. There’s a difference between repetition and redundancy. You can use repetition to be effective. You can never use redundancy for anything.

How many times does your character’s name appear in a given passage? How frequently are the same words in close proximity? When you read aloud, do the same words pop up over and over? There are a plethora of action verbs and adjectives at your beck and call to describe similar actions and behaviors without being redundant. Decide which is effective repetition and which is redundant blah and eliminate.

5. Unnecessary words are clutter. Cut them out. Efficient images are effective images.

This is the simple reason why you see blogs and advice to writers repeating over and over to eliminate adverbs. The truth is this: adverbs are not inherently evil. But when you say she was grinning widely or shouting loudly — you are being redundant.

Redundancy, as we’ve agreed, is not effective writing. When the reader is pulled out of your image by its clunky phrasing, it is not an effective image. And we’re going for effective images, yes? And I know, as we agreed, words are beautiful things. But too many of them leads to clutter. Clean them up and really be honest when you’re doing it; this cleaning up may take multiple readers and a loving editor but you’ll have stronger prose.

6. One of the quickest ways to establish voice is careful diction.

Diction: the choice of words and the way in which they are used. Establishing voice is not simply a matter of throwing in key vernacular or vocabulary (like “y’all” or “dahling,” say). It’s not about short sentences. Or about long, flowing, elegant sentences replete with word upon word, flowery adjective piled upon adverbs of glorified density. No. Diction is all of that. Establishing a voice is about finding consistency, about finding a style and a flow that reads naturally. (I do enjoy well-used vernacular, but please: simply tagging sentences with vocabulary does not count as adding it naturally!)

Poems can establish voice effortlessly in single lines. Some of the shortest poetry can still feel as if it has a character behind it despite its few words. Getting into a character in a short poem was one of the hardest and most effective lessons for me in establishing voice, in getting into a character’s head and speaking their words. When I am having trouble finding a consistent voice, I fall back on my poetry workshop tricks. I look at my word choice, the consistency, the tone my words evoke. I ask for feedback. I read it aloud. It helps.

7. Your reader has five senses. Do you take advantage of them?

Not only within the imagery of the page, but with the very words on the page. When I say I love “evocative” writing, I mean to say I love writing that seems to lift from the page, that has undeniable depth. I measure that depth by the sensory experience I have when I read it. When someone needs to shake me out of a world — that’s a world written well. Every one of those worlds draws me in through smell, through sight and sound, through the occasional stirring of a memory through an image that brings my own sensory experiences to bear on my reading experience. The reason This Is Just To Say hits me so hard every time I read it is because I know what it feels like to bite into that cold, sweet plum, the juice dripping down my chin. I feel that. But some of my favorite books evoke that same visceral experience for an image or a scene I’ve never personally experienced because they use the same tricks of making reading a personal, sensory experience. I’ve never faced down a dragon. I’ve never been in a war, a battle. But the best scenes bring me there and keep me grounded through those little details, and through sense.

——–

Do you read or write poetry? (Or both?) Has any poem or verse influenced you or your writing (be it the “greats” of the past centuries or someone more modern)?

What tricks do you think writers of prose can learn from poetry?

  • a random quote

    Anger is the feeling that makes your mouth work faster than your mind. — Evan Esar

  • the latest updates

  • recent blog posts

  • a few random posts

  • blog post categories

  • blog post archives

  • the latest from some of the feeds I read