There's a post title for Google to have fun with.
In any event, I planned to blog this morning, but I didn't really have a topic in mind. Usually, I sit down with a fair idea of what I'm going to write about, but not this morning.
I sat here sipping my coffee, willing the old neurons to start firing, but feeling that I just really didn't have anything to say. Just then, a wisp of a memory from childhood came floating to the surface. Something about not having anything to say. And then it hit me:
Supercalifragilisticexpialidocious
[Truth in advertising: I did not spell that on my own. Copy / Paste to the rescue.]
This is the word made famous by Mary Poppins, of course. To my deep shame, I have never read the novels, and so I must defer to the marvelous 1964 film as my sole source of canonical Poppins. In the film, young Jane Banks, speaking to her father, defines supercalifragilisticexpialidocious thusly: "It's something to say when you don't know what to say."
Musical interlude!
As Mary and Bert explain to us in song, you don't always have to know exactly what to say. Simply breaking the ice is often enough to get the words flowing, and next thing you know, you find yourself complimented with Edwardian kudos like, "There goes a clever gent!"
Relating this to writing, getting started is often the hardest part for me. Not just the beginning of a novel, but every writing session, every single day. I sit to write and spend several minutes just staring at the screen, with all the words trapped behind a dam of uncertainty. The best remedy for this is just to write. Anything. Even if it has nothing to do with my story. If I get the words going, my brain tends to wake up and move in the direction I want.
I've found the concept of supercalifragilisticexpialidocious works in a variety of situations besides conversation and writing: cleaning the house, planning a trip, getting on track with diet and exercise... Often, a task we wish to undertake feels overwhelming. We can't see how we'll ever get over the hill to the desired result on the other side. Just starting--somehow, anyhow--is often enough to help us overcome our fears and achieve our goals.
Supercalifragilisticexpialidocious. Give it a try.
Monday, January 9, 2012
Tuesday, January 3, 2012
New Year, New Ramble
Happy New Year, y'all! (I'm Southern. Deal.) How were your holidays? Mine were super--thanks for asking!
Every year about this time, lots of people hit the ground running with their resolutions. I'm not much of a resolutionary, myself. Still, this time of year always brings to mind the one time I made a resolution and stuck with it. This is the story of how I became a novelist. Gather 'round the fire, children, and listen to my tale...
Books have amazed me from my earliest memories. They introduced me to fascinating people. Characters became my friends, or role models I looked up to, or villains I reviled. I went to new, marvelous places--Narnia, Middle Earth, Prince Edward Island, secret gardens, beyond the tollbooth, Wonderland. I traveled through time to see life as it was once lived, or how it may be lived someday. When I wasn't reading books, I played out their stories with my toys, or in my backyard with my sister and friends roped into carrying out my adaptations. Books captured me like nothing else.
And the people who wrote them? Wizards. Gods. Idols. Untouchables. To be able to do this thing that words on a page could do... it was wonderful and totally mystifying. I had no idea how a person went about creating a novel, how to become a name on the cover of a book. I longed to join my authorial heroes on the shelf, but it seemed so out of reach, something that happened to other people, important people--not little Elizabeth from a small Southern town.
Through the years, I wrote lots of short stories, poems, and narrative essays, but the novel eluded me. It was too big. Too hard. I didn't know how to approach it.
Finally, in 2004, I made a New Year's resolution: This would be the year in which I wrote a novel. I still didn't know how, but I was determined to figure it out. I went to the repository of all knowledge, Barnes and Noble, seeking enlightenment and came away with this book, which promised to teach me how to write AND sell my first novel. Perfect! I figured this writing career thing was pretty much in the bag, since I am great at following instructions.
I hatched a far too autobiographical idea and built my first novel outline, then plunged into my first first draft. I dutifully kept track of how many pages I wrote each day. Mr. Boyce was so supportive. He took our young boys out of the house to give me quiet time to write.
After not too many months (Four? Five? I can't quite recall now.), I had a completed manuscript in hand and was ready to move on to the selling portion of my guidebook's program. I drafted a query letter and proceeded to carpet bomb the New York literary world with it. When my first rejection letter came, I was ecstatic. I'd been blooded. I was legitimate. Each rejection just brought me one step closer to acceptance, I reminded myself.
Then another rejection letter came. And another. And another. And fifty more after that. As it happened, no one wanted a coming of age novel about a plucky young woman in a small Southern town--at least, not one riddled with a contrived plot and rookie writing errors. Every rejection I received was well deserved. My manuscript was nowhere near close to publication-worthy. I know that now. Looking back, I cringe at the thought of that thing ever seeing the light of day.
Still, I'd gotten a taste of the process. I'd finished a novel manuscript and gone through the motions of submitting. I had a better idea of what this whole novel thing was about, and I was hooked.
My first attempt wasn't published (Thank goodness!), but I wouldn't call it a failure, either. I learned so much from that first, terrible novel. It gave me the courage to explore and learn more about the craft of novel writing. It taught me to develop patience, to wait until my work is the very best it can be before submitting. I also learned to put a little distance between myself and my work. A rejection from an agent or editor isn't a judgment about me personally; it's a business decision.
I'm still plugging away, still taking baby steps toward finding a home for my novels. And I'll keep at it until I do find that home, and then I'll keep at it and build my career. There's nothing else I would rather do. In many ways, my resolution from 2004 holds strong, which is why I've stopped making new ones. It's the same resolution every year: This year, I will write and submit. That desire, that need, has never waned. It's the one resolution that stuck and changed my life.
How about you, readers? Tell me a story about how you became a whatever it is you became. Or tell me about your resolutions or why you never make them. It's a new year and it's cold outside. Sit by the fire and chat with us for a little while.
| If you listen well, I'll give you a butterscotch. A Werther's, if you're really good. |
Books have amazed me from my earliest memories. They introduced me to fascinating people. Characters became my friends, or role models I looked up to, or villains I reviled. I went to new, marvelous places--Narnia, Middle Earth, Prince Edward Island, secret gardens, beyond the tollbooth, Wonderland. I traveled through time to see life as it was once lived, or how it may be lived someday. When I wasn't reading books, I played out their stories with my toys, or in my backyard with my sister and friends roped into carrying out my adaptations. Books captured me like nothing else.
| l-r: Beverly Cleary, Louisa May Alcott, Roald Dahl |
Through the years, I wrote lots of short stories, poems, and narrative essays, but the novel eluded me. It was too big. Too hard. I didn't know how to approach it.
Finally, in 2004, I made a New Year's resolution: This would be the year in which I wrote a novel. I still didn't know how, but I was determined to figure it out. I went to the repository of all knowledge, Barnes and Noble, seeking enlightenment and came away with this book, which promised to teach me how to write AND sell my first novel. Perfect! I figured this writing career thing was pretty much in the bag, since I am great at following instructions.
I hatched a far too autobiographical idea and built my first novel outline, then plunged into my first first draft. I dutifully kept track of how many pages I wrote each day. Mr. Boyce was so supportive. He took our young boys out of the house to give me quiet time to write.
After not too many months (Four? Five? I can't quite recall now.), I had a completed manuscript in hand and was ready to move on to the selling portion of my guidebook's program. I drafted a query letter and proceeded to carpet bomb the New York literary world with it. When my first rejection letter came, I was ecstatic. I'd been blooded. I was legitimate. Each rejection just brought me one step closer to acceptance, I reminded myself.
Then another rejection letter came. And another. And another. And fifty more after that. As it happened, no one wanted a coming of age novel about a plucky young woman in a small Southern town--at least, not one riddled with a contrived plot and rookie writing errors. Every rejection I received was well deserved. My manuscript was nowhere near close to publication-worthy. I know that now. Looking back, I cringe at the thought of that thing ever seeing the light of day.
Still, I'd gotten a taste of the process. I'd finished a novel manuscript and gone through the motions of submitting. I had a better idea of what this whole novel thing was about, and I was hooked.
| I just have to keep spinning my... You know what? Never mind. That's painfully lame, even for me. |
I'm still plugging away, still taking baby steps toward finding a home for my novels. And I'll keep at it until I do find that home, and then I'll keep at it and build my career. There's nothing else I would rather do. In many ways, my resolution from 2004 holds strong, which is why I've stopped making new ones. It's the same resolution every year: This year, I will write and submit. That desire, that need, has never waned. It's the one resolution that stuck and changed my life.
How about you, readers? Tell me a story about how you became a whatever it is you became. Or tell me about your resolutions or why you never make them. It's a new year and it's cold outside. Sit by the fire and chat with us for a little while.
Thursday, December 15, 2011
Please Accept My Apology
On Monday morning, the eldest young Master Boyce woke up ill.
"I'm sorry you're not feeling well," I said as I tucked him back into bed.
Then the second one chimed in, his eyes gleaming with envy. "My stomach hurts, too!"
"I'm sorry to hear that," I murmured, shooing him along to breakfast.
He ate and got ready for school, all the while angling for a day off like his brother was getting. "I'm serious, my stomach hurts," he insisted. "I ate too much last night."
"I'm sorry," said I. "You'll feel better soon."
My son rounded on me. "Why do you keep saying that?" he snapped.
"What?"
"You keep saying you're sorry! Every time we're sick or we get hurt, you say you're sorry."
"Oh," I said, a little taken aback. "I'm... sorry."
He threw his hands up in frustration and stomped off to the bus, his annoyance at me driving away his phantom stomach ache.
I apologize a lot--or rather, I use the words of apology, when I don't really mean them, at all.
I'm sorry for your loss.
I'm sorry you're sick.
I'm sorry you fought with your husband.
I'm sorry things are hard for you right now.
I'm sorry the restaurant was terrible.
I'm sorry you had a bad day at work.
I'm sorry for saying I'm sorry so much.
I don't mean it. What I mean is, "I feel sorrow on your behalf." "I empathize." "My heart is heavy for you." "I wish you weren't sick." "I acknowledge the injustice of your situation." "This should not have happened to you."
Those are the kinds of things I mean, but I use "I'm sorry" as a lazy shorthand.
Some people are really bothered by this misuse of "I'm sorry," though not as much as the use of a word I won't mention. More than once the reply to my "I'm sorry," has been something along the lines of, "Why? You didn't do it."
I know I didn't do it. That's not what I mean. I think everyone knows that's not what we "I'm sorry"ers mean. We're honestly trying to express sympathy, but some people don't respond well to it when it comes wrapped up as an apology.
So, why don't I just say what I mean? It's a linguistic rut, a thoughtless habit. But I'm going to try to be more conscientious about the words I use next time I feel "I'm sorry" trying to fall off my tongue.
Do you say "I'm sorry" as an expression of sympathy / empathy? Do you find it problematic? Let's discuss it in the comments!
"I'm sorry you're not feeling well," I said as I tucked him back into bed.
Then the second one chimed in, his eyes gleaming with envy. "My stomach hurts, too!"
"I'm sorry to hear that," I murmured, shooing him along to breakfast.
He ate and got ready for school, all the while angling for a day off like his brother was getting. "I'm serious, my stomach hurts," he insisted. "I ate too much last night."
"I'm sorry," said I. "You'll feel better soon."
My son rounded on me. "Why do you keep saying that?" he snapped.
"What?"
"You keep saying you're sorry! Every time we're sick or we get hurt, you say you're sorry."
"Oh," I said, a little taken aback. "I'm... sorry."
He threw his hands up in frustration and stomped off to the bus, his annoyance at me driving away his phantom stomach ache.
* * *
I apologize a lot--or rather, I use the words of apology, when I don't really mean them, at all.
I'm sorry for your loss.
I'm sorry you're sick.
I'm sorry you fought with your husband.
I'm sorry things are hard for you right now.
I'm sorry the restaurant was terrible.
I'm sorry you had a bad day at work.
I'm sorry for saying I'm sorry so much.
I don't mean it. What I mean is, "I feel sorrow on your behalf." "I empathize." "My heart is heavy for you." "I wish you weren't sick." "I acknowledge the injustice of your situation." "This should not have happened to you."
Those are the kinds of things I mean, but I use "I'm sorry" as a lazy shorthand.
Some people are really bothered by this misuse of "I'm sorry," though not as much as the use of a word I won't mention. More than once the reply to my "I'm sorry," has been something along the lines of, "Why? You didn't do it."
I know I didn't do it. That's not what I mean. I think everyone knows that's not what we "I'm sorry"ers mean. We're honestly trying to express sympathy, but some people don't respond well to it when it comes wrapped up as an apology.
So, why don't I just say what I mean? It's a linguistic rut, a thoughtless habit. But I'm going to try to be more conscientious about the words I use next time I feel "I'm sorry" trying to fall off my tongue.
Do you say "I'm sorry" as an expression of sympathy / empathy? Do you find it problematic? Let's discuss it in the comments!
Monday, December 5, 2011
Baby Elephants
Fear not, dear readers. I have not, in fact, fallen into the abyss. I got caught up in November madness with kid sports and Thanksgiving (How was yours, by the way? Ours was great; thanks for asking!) and then Mr. Boyce and I high tailed it out of town for one of those decade anniversary trips... Phew! Anyway, I have Returned in Triumph--over what, I couldn't say, but here I am. Ta-daaaaaaaa!
So, while catching up on the mountain of laundry that vacations produce, I was thinking about this terrible cliché one hears authors spout about their book being their baby, or how writing a book is like having a baby, or some variation thereof.
I hate that.
It isn't true, and I'll tell you why.
Look, I've had a few babies in my time. Gestating a baby is rife with physical discomfort, but it's pretty low on the mental strain. Pregnancy is as much a biological process as growing fingernails, and you probably don't put much effort into making that happen, do you? Yes, parents-to-be absolutely worry and fret over their little ones, and there's a lot to do to prepare the nest for a baby's arrival. But, you don't have to think about actually making a baby. Gosh, can you imagine having to sit down and concentrate for hours at a time to form a baby's various internal structures and organs and choosing eye color and leg length and nose shape and... wow, I'm making myself tired just considering it. And the results wouldn't be pretty.
No, the baby will gestate just fine without any creative input from you, thankyouverymuch.
A novel, meanwhile, goes nowhere without the writer's full effort. Everything is created from scratch--the world, the characters, the plot. It's a heck of a lot of thinking work. And then there's the writing work. And the submitting work. And the marketing work. And the--hey, this is starting to sound more like a job than a baby.
Another point at which the book-as-a-baby analogy falls apart is the gestational period, ie, the time itself. That baby's only going to brew for so long. Thirty-eight to forty-two weeks in normal circumstances, and then, blammo! Evicted in a relatively brief rush of pain and effluvia. Hours (or days, for the unfortunate) later, and it's all over. Baby has arrived.
The time frame for writing a novel varies from author to author. Some can hammer out a first draft in a few months. Others might take a year or more. Editing tacks on more time, and manuscripts can languish in the submission process for years (Ask me how I know. Actually, don't. It's too depressing.). I've known an author who was picked up by the first agent she submitted to, and more authors who rack up dozens of rejections before finally finding someone to represent their work. Then comes submitting (yes, again) to publishers. Editing (yes, again) with the publishing house's editor. Then sitting in queue for publication, and then--THEN! Oh, glorious day, publication. The book is finished and released to the world. It's over. No going back, no changing, no growing.
That baby, meanwhile, which you gestated and birthed in less than a year is going to continue to develop and grow and change and require your support and help and love for the next infinity.
Likening a book to a baby is too emotional for my taste. It gives the novel an unreasonable sense of importance in the grand scheme of things. I have manuscripts and I have children. The two are not even closely related.
Of course, I put heart and effort and sweat and tears and even a little blood (paper cuts!) into my novels. Of course, I want to see them out in the world for readers to enjoy. But in the end, writing is a job. Novels are the products of authors' hard work, ones we want to sell. Submitting is the process of applying for a paying job as a novelist.
Maybe some authors really do have similar feelings about their novels and their children, but not me. I have to give myself some emotional distance from the businessy side of writing; otherwise, I'd go mad. Gestating an actual baby for nine months is hard enough. I couldn't deal with the uncertainty and stress of submitting if I thought of each manuscript as a baby. Besides, what kind of mother sells her children?
So, while catching up on the mountain of laundry that vacations produce, I was thinking about this terrible cliché one hears authors spout about their book being their baby, or how writing a book is like having a baby, or some variation thereof.
I hate that.
It isn't true, and I'll tell you why.
| No. |
No, the baby will gestate just fine without any creative input from you, thankyouverymuch.
A novel, meanwhile, goes nowhere without the writer's full effort. Everything is created from scratch--the world, the characters, the plot. It's a heck of a lot of thinking work. And then there's the writing work. And the submitting work. And the marketing work. And the--hey, this is starting to sound more like a job than a baby.
Another point at which the book-as-a-baby analogy falls apart is the gestational period, ie, the time itself. That baby's only going to brew for so long. Thirty-eight to forty-two weeks in normal circumstances, and then, blammo! Evicted in a relatively brief rush of pain and effluvia. Hours (or days, for the unfortunate) later, and it's all over. Baby has arrived.
| I put a lot of work into this one, but you can have it for a reasonable advance, plus royalties. |
That baby, meanwhile, which you gestated and birthed in less than a year is going to continue to develop and grow and change and require your support and help and love for the next infinity.
Likening a book to a baby is too emotional for my taste. It gives the novel an unreasonable sense of importance in the grand scheme of things. I have manuscripts and I have children. The two are not even closely related.
Of course, I put heart and effort and sweat and tears and even a little blood (paper cuts!) into my novels. Of course, I want to see them out in the world for readers to enjoy. But in the end, writing is a job. Novels are the products of authors' hard work, ones we want to sell. Submitting is the process of applying for a paying job as a novelist.
Maybe some authors really do have similar feelings about their novels and their children, but not me. I have to give myself some emotional distance from the businessy side of writing; otherwise, I'd go mad. Gestating an actual baby for nine months is hard enough. I couldn't deal with the uncertainty and stress of submitting if I thought of each manuscript as a baby. Besides, what kind of mother sells her children?
Tuesday, November 8, 2011
Pansy
I have a difficult time naming things. One of my children was named while we drove to the hospital, just a few hours before he was born. Another's first name was finally settled on a day or two before she arrived, but she had to live the better part of two days without a middle name.
Pets haven't been any easier. At an early age, I turned to literature for companion animal monikers. Thus the cat six-year-old me dubbed Romeo. Scout, Sadie, and Marlowe followed over the years. The time I stepped away from literary inspiration, I wound up with a goldfish named Hubert.
It's just so hard for me to name things. A name is a word (or a sparse few) that is forever associated with that person, pet, or character. It isn't arbitrary, it encapsulates the very idea of a person. Sometimes a name just doesn't mesh well with who a person is. Margaret Mitchell originally named her heroine Pansy O'Hara. Can you imagine? Thankfully, her publisher convinced her to change the name, and Scarlett has been an icon ever since--fiery, feisty, passionate, bold. Scarlett. That's a great name.
Naming my own heroines hasn't been my primary difficulty, but the menfolk give me fits. My current work in progress was held up at the beginning of chapter two for nearly a week while I anguished over the hero's name. A Romance hero's name should be strong, and give a hint as to what kind of person he is (the heroine's, too, but I have an easier time with female names). You can't just slap any old name onto a character and expect it to fly. That'll never work!
Sometimes, writers will tell you their characters speak to them. I've seen author / character interviews, and my author buddies have occasionally mentioned something jolly their current favorite character said in passing. Frankly, I just nodded and smiled when I heard of such things. None of my characters has ever spoken to me. That is, until the day I tried to force a name on a hero. This particular hero (A different one than the above mentioned chapter two holdout. These guys kill me.) had driven me batty in the development stage. I knew so much about him--how he looked, how he spoke, the clutter on the desk in his study--but I didn't know his name. Finally, I decided to smoke him out. This hero is a gambler. Temperamental. Proud. Intense. Just to be spiteful, I told him he would be a hobbyist carpenter and that I was going to call him Howard. Clear as day, I heard him. "My name is Ethan, and I sail." Well. Alrighty then.
I thanked him kindly for his time. We never spoke of the carpentry kerfuffle again.
| It seemed like a dignified choice at the time. |
It's just so hard for me to name things. A name is a word (or a sparse few) that is forever associated with that person, pet, or character. It isn't arbitrary, it encapsulates the very idea of a person. Sometimes a name just doesn't mesh well with who a person is. Margaret Mitchell originally named her heroine Pansy O'Hara. Can you imagine? Thankfully, her publisher convinced her to change the name, and Scarlett has been an icon ever since--fiery, feisty, passionate, bold. Scarlett. That's a great name.
Naming my own heroines hasn't been my primary difficulty, but the menfolk give me fits. My current work in progress was held up at the beginning of chapter two for nearly a week while I anguished over the hero's name. A Romance hero's name should be strong, and give a hint as to what kind of person he is (the heroine's, too, but I have an easier time with female names). You can't just slap any old name onto a character and expect it to fly. That'll never work!
Sometimes, writers will tell you their characters speak to them. I've seen author / character interviews, and my author buddies have occasionally mentioned something jolly their current favorite character said in passing. Frankly, I just nodded and smiled when I heard of such things. None of my characters has ever spoken to me. That is, until the day I tried to force a name on a hero. This particular hero (A different one than the above mentioned chapter two holdout. These guys kill me.) had driven me batty in the development stage. I knew so much about him--how he looked, how he spoke, the clutter on the desk in his study--but I didn't know his name. Finally, I decided to smoke him out. This hero is a gambler. Temperamental. Proud. Intense. Just to be spiteful, I told him he would be a hobbyist carpenter and that I was going to call him Howard. Clear as day, I heard him. "My name is Ethan, and I sail." Well. Alrighty then.
I thanked him kindly for his time. We never spoke of the carpentry kerfuffle again.
Friday, November 4, 2011
A Penny for the Old Guy
Remember, remember the fifth of November,
Gunpowder treason and plot.
I see no reason why gunpowder treason
Should ever be forgot.
-English folk verse
The Gunpowder Plot of 1605 is a fascinating incident in British history. You're probably familiar with the imagery of the Gunpowder Plot--the Guy Fawkes mask, bonfires, effigies, fireworks. In the United States (and perhaps elsewhere), the details of the plot itself are not as commonly known, so I thought I'd provide a brief and woefully inadequate overview of the Plot.
English Catholics had suffered intense legal and social persecution during the rein of Elizabeth I. When James I succeeded her in 1603, Catholics hoped the new monarch would undo these injustices. The son of the Catholic Mary, Queen of Scots, James did hold personal views much more tolerant than Elizabeth, but his administration brought about no official changes. Tired of waiting for a Protestant government to grant Catholics relief, Robert Catesby (who had previously taken part in the Essex Rebellion) devised a plan to topple the British establishment.
Catesby's goal was simple: Obliterate the Protestant English government and install a Catholic head of state. To achieve this goal, he and his co-conspirators planned to detonate a stockpile of gunpowder beneath the House of Lords during the State Opening of Parliament, November 5, 1605, when the king and the entire House of Lords would be assembled in one room. With the mass assassination accomplished, they planned to install James' daughter, nine-year-old Princess Elizabeth (Not to be confused with Elizabeth I, who was already deceased. Zombie monarchs rarely work out as well as you'd hope.) as a Catholic queen.
Throughout the spring and summer of 1605, the conspirators set the stage for their coup d'état. They leased an undercroft directly below the House of Lords and purchased the gunpowder required to demolish the building above. Catesby delegated responsibility for the explosives to a devout Catholic and military veteran, a gentleman by the name of Fawkes.
Guy Fawkes is the name most commonly associated with the Gunpowder Plot, because it was his arrest and subsequent torture and interrogation that led to the complete unraveling of the conspiracy. Things went bad when William, Baron Monteagle received an anonymous letter on October 26, 1605, warning him not to attend the State Opening of Parliament. An investigation commenced at once to discover the source of the threat. Just after midnight on November 5--only hours before the scheduled State Opening of Parliament--Guy Fawkes was discovered in the undercroft below the House of Lords, in the company of 36 barrels of gunpowder and a fuse.
In the days that followed, Fawkes and his co-conspirators were arrested, tried, and executed for treason. As I noted previously, Catholic emancipation did not take legal effect in England until 1829. Following the Plot, tighter laws were passed to curtail Catholic religious observance and legal rights. In January of 1606, Parliament passed the Observance of 5th November Act 1605. The Act declared November 5 an annual, public day of thanksgiving for the failure of the Gunpowder Plot. Initially observed with sermons and other boring services leading up to the iconic Bonfire Night festivities, it has since evolved into an excuse to set off fireworks, hang out around a big fire, and drink with friends.
I would be remiss if I did not point out that the Gunpowder Plot conspirators did not wish to create a religiously tolerant England. Rather, they hoped to revert England to a papist state--essentially turning the persecution tables on the Protestant population. Nevertheless, Bonfire Night was observed with decidedly anti-authoritarian tones in pre-Revolutionary Boston. The Guy Fawkes mask has been adopted as a symbol of anti-establishment sentiment thanks to the graphic novel V for Vendetta and its 2006 film adaptation. Most recently, both the hacking group Anonymous and Occupy protesters around the world have donned the mask as a sign of rebellion and group solidarity.
Like all political movements, the Gunpowder Plot of 1605 will continue to take on new meanings and interpretations as time passes. For some, the conspirators were regicidal traitors. For others, they were freedom fighters taking a stand against tyranny.
What would have happened if Guy Fawkes had not been arrested in the early morning hours of November fifth? Would the Plot have succeeded in killing James I and everyone inside the House of Lords? Oh, yes.
English Catholics had suffered intense legal and social persecution during the rein of Elizabeth I. When James I succeeded her in 1603, Catholics hoped the new monarch would undo these injustices. The son of the Catholic Mary, Queen of Scots, James did hold personal views much more tolerant than Elizabeth, but his administration brought about no official changes. Tired of waiting for a Protestant government to grant Catholics relief, Robert Catesby (who had previously taken part in the Essex Rebellion) devised a plan to topple the British establishment.
| Honestly, that mask could be the face of any one of these guys. Except for metro over there on the left. |
| Nine seemed much older back then. |
Throughout the spring and summer of 1605, the conspirators set the stage for their coup d'état. They leased an undercroft directly below the House of Lords and purchased the gunpowder required to demolish the building above. Catesby delegated responsibility for the explosives to a devout Catholic and military veteran, a gentleman by the name of Fawkes.
Guy Fawkes is the name most commonly associated with the Gunpowder Plot, because it was his arrest and subsequent torture and interrogation that led to the complete unraveling of the conspiracy. Things went bad when William, Baron Monteagle received an anonymous letter on October 26, 1605, warning him not to attend the State Opening of Parliament. An investigation commenced at once to discover the source of the threat. Just after midnight on November 5--only hours before the scheduled State Opening of Parliament--Guy Fawkes was discovered in the undercroft below the House of Lords, in the company of 36 barrels of gunpowder and a fuse.
In the days that followed, Fawkes and his co-conspirators were arrested, tried, and executed for treason. As I noted previously, Catholic emancipation did not take legal effect in England until 1829. Following the Plot, tighter laws were passed to curtail Catholic religious observance and legal rights. In January of 1606, Parliament passed the Observance of 5th November Act 1605. The Act declared November 5 an annual, public day of thanksgiving for the failure of the Gunpowder Plot. Initially observed with sermons and other boring services leading up to the iconic Bonfire Night festivities, it has since evolved into an excuse to set off fireworks, hang out around a big fire, and drink with friends.
| The sinister smile of freedom. |
Like all political movements, the Gunpowder Plot of 1605 will continue to take on new meanings and interpretations as time passes. For some, the conspirators were regicidal traitors. For others, they were freedom fighters taking a stand against tyranny.
What would have happened if Guy Fawkes had not been arrested in the early morning hours of November fifth? Would the Plot have succeeded in killing James I and everyone inside the House of Lords? Oh, yes.
Tuesday, November 1, 2011
Alone
Saturday morning, I woke up bright and early, pressed the coffee, and turned on the computer, as is my custom. My intention had been to cancel an unwise Amazon order I'd placed the previous evening in a fit of nostalgia and Ambien. When I opened the browser and fired up my email program, I noticed things were running sluggishly.
And by sluggishly, I mean not at all. Page Cannot Load. Server Not Found. Flagrant System Error. I turned to my husband still lying abed. "Hey, we don't have any internet," I informed him. He told me he'd go buy a carton of it later and rolled over.
A short time later, Mr. Boyce declared our household internet service dead in the water. This was bad news, as Chez Boyce is highly dependent on the internet. We use it for the computer, obviously, but also for our home phone and streaming entertainment to the television. Without the internet, we had been dropped into a virtual oubliette.
We had to wait until Monday for help, so we hunkered down for a weekend sans web. Saturday passed slowly. I kept thinking things like, Since I can't check Facebook, I'll just look up that recipe I've been meaning to try. Oh, wait. It's on the internet. Then I'd decide to call a friend, instead, but I couldn't do that, either, because we had no internet. I could still use my cell phone to text, thankfully, but bite-sized morsels of conversation aren't very satisfying.
Sunday wasn't any better. It's strange to realize how much you rely on something only when it's gone. I read and worked some puzzles and took a nap. Mr. Boyce kept wandering into the room where the modem lives to watch its lights flicker.
By Sunday night, despair had begun to sink in. We were alone. Stranded on a deserted island in the middle of suburbia. It felt as if we had always been isolated like this, and that we might never contact the outside world again.
On Monday, Mr. Boyce got word that help was on the way. Someone was coming in a life boat / cable company van. We arranged our afternoon to make sure one of us was here every moment to meet our rescuer.
The promised help never arrived.
Bitter and betrayed, we gathered the tatters of our dignity about ourselves. We didn't need the internet, anyway, I declared. We were fine without it. Just fine. I helped the Boycelings get ready for Trick-or-Treating. We had a fun evening walking the neighborhood, saying hello to neighbors, and congratulating children on clever costumes.
I realized we could still be connected without the internet--if on a much smaller scale. I arrived at a place of peace about our lack of internet. Of course, it was vexing to not be able to dial 911 in case of emergency, but we could always run to the neighbor's house if necessary. We have neighbors, a fact I sometimes forget as we isolate ourselves inside our house, connecting to everyone in the world except for the other humans in our physical proximity.
Today, obviously, the life boat arrived. I rolled out the red carpet as my hero replaced our terminally vegetative modem with a new, lively one. So here I am, reconnected. No longer alone. Alone as ever.
And by sluggishly, I mean not at all. Page Cannot Load. Server Not Found. Flagrant System Error. I turned to my husband still lying abed. "Hey, we don't have any internet," I informed him. He told me he'd go buy a carton of it later and rolled over.
A short time later, Mr. Boyce declared our household internet service dead in the water. This was bad news, as Chez Boyce is highly dependent on the internet. We use it for the computer, obviously, but also for our home phone and streaming entertainment to the television. Without the internet, we had been dropped into a virtual oubliette.
We had to wait until Monday for help, so we hunkered down for a weekend sans web. Saturday passed slowly. I kept thinking things like, Since I can't check Facebook, I'll just look up that recipe I've been meaning to try. Oh, wait. It's on the internet. Then I'd decide to call a friend, instead, but I couldn't do that, either, because we had no internet. I could still use my cell phone to text, thankfully, but bite-sized morsels of conversation aren't very satisfying.
Sunday wasn't any better. It's strange to realize how much you rely on something only when it's gone. I read and worked some puzzles and took a nap. Mr. Boyce kept wandering into the room where the modem lives to watch its lights flicker.
By Sunday night, despair had begun to sink in. We were alone. Stranded on a deserted island in the middle of suburbia. It felt as if we had always been isolated like this, and that we might never contact the outside world again.
| After some hours, my tears ran dry. |
On Monday, Mr. Boyce got word that help was on the way. Someone was coming in a life boat / cable company van. We arranged our afternoon to make sure one of us was here every moment to meet our rescuer.
The promised help never arrived.
Bitter and betrayed, we gathered the tatters of our dignity about ourselves. We didn't need the internet, anyway, I declared. We were fine without it. Just fine. I helped the Boycelings get ready for Trick-or-Treating. We had a fun evening walking the neighborhood, saying hello to neighbors, and congratulating children on clever costumes.
I realized we could still be connected without the internet--if on a much smaller scale. I arrived at a place of peace about our lack of internet. Of course, it was vexing to not be able to dial 911 in case of emergency, but we could always run to the neighbor's house if necessary. We have neighbors, a fact I sometimes forget as we isolate ourselves inside our house, connecting to everyone in the world except for the other humans in our physical proximity.
Today, obviously, the life boat arrived. I rolled out the red carpet as my hero replaced our terminally vegetative modem with a new, lively one. So here I am, reconnected. No longer alone. Alone as ever.
Subscribe to:
Posts (Atom)