Unsolved Mysteries: The Frank Rivers Saga

Unsolved mysteries bug the living crap out of me.  I can't help it.  The human race has put a man on the moon, built skyscrapers, cloned animals, and done all sorts of stuff that seems scientifically impossible...until someone does it.  (Internet, anyone?)  So why is it so hard to figure out what happened to some people?  How can simple things like bones and flesh and minerals just disappear, or become seemingly impossible to find?

Before they found the skeletons of the Romanovs, I lost some serious sleep wondering where on earth they were.  I still occasionally lose sleep over the Amelia Earhart thing.  I've spent serious time pondering where the Ark of the Covenant could be.  These are all solvable problems...or they should be, in my mind.

But in the past year, I've lost the most sleep over one of my own relatives:  my elusive great-great-grandfather.  I've become addicted to genealogy research.  It's my crack.  The computer has to be pried out of my sleepy fingers before I'll shut it off and let go of the elusive loose end that is Frank Rivers.  He's the guy on the left in this photo, with his hand on the dog.  The man you can barely see.  The man I can't find.

Frank Rivers.  Don't suppose any of you know who this guy is?  I sure don't.

According to family information I was given, he lived in Smith's Valley, Nevada in the late 1800s.  This picture was taken there in about 1902.  Based on federal census information, I think he showed up in Cache Creek by 1870.  He sold the Nevada farm and moved south, but I'm not sure exactly when--he died in Los Angeles in 1912.  I don't know how or when he headed west, but he wasn't born here.

He filled out his census information with several different birth dates ranging from 1841 to 1845.  Most of his census answers indicate that he was born in New York about 1844.  One says "L.I.," which I take to mean Long Island.  However, Frank's daughter Hazel (my great-grandmother, the little girl sitting on the porch in the photo) answered her 1930 census with a strange response for "Father's Birthplace:"  Michigan.


Michigan?  WTF?  Why the heck would she say Michigan when in 1900, 1910, and 1920, she said Frank was born in New York?  What did she know that I don't?

Another family member, a second cousin who'd begun a family tree in the 1970s, also lists Frank's birthplace as Holland, Michigan in July of 1842.  That's not New York and it's not 1844.  Why do my second cousin and great-grandmother think Frank was born in Michigan, when he himself told every census taker who asked him he'd been born in New York?  Was he lying?  Did he have something to hide?  Or, if he was telling the truth, why would my great-grandmother have lied?  Or did Frank lie to his kids, but tell the truth to the census taker?  What's the point of that?

It makes my head hurt.

I have spent HOURS on Ancestry.com and FamilySearch.org looking for leads.  This has gone on for over a year now.  For the past two nights, I've been up past midnight tracking down everyone by the name of Francis or Frank Rivers who lived in New York or Michigan in the 1840s.

So far, I've got two "Francis Rivard"s in Michigan, one born in 1843 and one born in 1835.

I've got two "Francis Rivers"s in New York.  One, born in 1844, was in the poorhouse by 1854 and indentured to a guy named William Buchan in Hopewell.  He shows up on the census in 1855 and 1860, but he's vanished in 1865.  Is this my Frank?  Did he head west when he grew up?

The second New York candidate was born in 1844 and lived in St. Lawrence, NY.  I need to go back and see where he falls off the map....if he falls off the map.  Maybe one of these guys is my ancestor.  Maybe none of them are.  It kills me to know that I may never know who Frank Rivers was.

It doesn't seem right that I can't find out who he was.  He was just a man.  An ordinary man.  No king, no oil baron, no one.  Still, he existed.  There are a few pictures of him and a record of a few land deeds and court cases in Nevada.  A man named Frank Rivers lived.  So why is it so hard to find out who he was and where he came from?

I'll probably never know the truth.  And I am having such a hard time with that.  Whoever he was, he's a part of me.  Did he murder someone and flee west, taking a new name?  Is he a humble farmer whose birth was just never documented?  How am I supposed to know where I came from when I can't figure out who this guy really is?

He's the major thorn in my genealogical side.  And it kills me that he's an unsolved mystery.  I feel like there's always going to be a part of me I don't know unless I solve this mystery.  It's silly, because I am who I am regardless of what Frank did.  But I began my genealogical quest in the hopes of finding answers as to why I'm so different from most of my family members.  When I spot others who are different, like Frank, it makes me think I might be like them.  But if Frank was a bad guy, what does being like him mean?  I want to know.  I need to know.  And I can't.  And it makes me want to tear my hair out.

Do you guys have any unsolved genealogical mysteries?  Which unsolved mysteries keep you up late at night?

Social Justice Stories: Good Idea? Bad Idea?

I don't like social justice stories.  You know the kind--stories that are all about publicizing an issue or gaining sympathy for a particular group, like single mothers or veterans or refugees from the Sudan.  I'm all for helping whoever needs it, but I just don't think short stories are the vehicle for helping with these kinds of issues.  I've always thought these kinds of stories come off as preachy and message-driven (as opposed to character- or even plot-driven).

In fact, I'm reading the 2009 Best American Short Stories compilation, and the social justice themes are starting to get a bit on my nerves.  I'm less than a quarter of the way through the book, and I've already encountered a wounded veteran trapped during Hurricane Katrina, a little boy who died of AIDS because of a botched transfusion, a Chinese man jailed because he followed his own career path, a Jewish widow who will do anything to see her husband's works edited and published. The first two stories in the collection were great--filled with normal, identifiable people making choices that define their lives.  And then wham, bam, nearly every story after these played the social justice card.  It makes me want to pull out my hair.  It's like the literary version of Oscar bait.  Want a crapload of Oscars?  Cast Daniel Day-Lewis as a paraplegic transvestite who was abused as a child.  Want to get published in a prestigious anthology?  Write a social justice story.    

So...given all this...why in the hell did I start writing a social justice story yesterday?

It started with Vanity Fair.  If you subscribe to the magazine, flip back to your August issue (the one with Emma Stone on the cover).  If you don't subscribe, just click here.  Alex Shoumatoff's "Agony and Ivory" is the easily the best piece of journalism I've ever read.  I've never been moved to tears by a magazine article before.

The article details the recent rise in African elephant poaching, fueled largely by a resurgent demand for ivory in Asia.  The ignorance and stupidity and greed on all sides breaks my heart.  Apparently, a large percentage of wealthy elderly Chinese believe an elephant's ivory tusks fall out, like baby teeth.  They don't know that the animals need to be killed to retrieve the ivory they pay thousands of dollars for.  The Muslim youth brigade Al-Shabbab (yeah, that's them on the news refusing to allow aid workers into Somalia to help with the famine) is also involved in the ivory trade.

The poachers are going after mating bulls and matriarchs--the exact elephants needed to keep herds alive and full of genetic diversity.  If the words "extinction vortex" mean anything to you, that's what's going to be happening pretty darn soon in terms of Africa's elephant population.  The article describes Kuku ranch group rangers finding a dead elephant.  Its face was hacked off to get at the ivory.  The body was still kneeling on the ground, decaying in an upright position, exactly where it had fallen.

Sometimes poachers shoot the elephants.  Sometimes they stab them dozens of times.  Sometimes they poison them.  Sometimes they do some or all of these things.  It is absolutely cruel the way these poachers go after these creatures.  Occasionally, the elephants don't die--they bleed and limp across borders or national park lines, searching for sanctuary.

The kicker is that I've been to one of the Kenyan parks mentioned in the article.  I spent one amazing weekend on safari at Intrepids Samburu (northern Kenya) in...good grief, could it be as long ago as 2003?  While I was there, I saw an elephant skull resting on the ground.  I took a picture of it because it was so creepy looking (at right). I have no way of knowing whether the elephant died a natural death--even though all I saw was the skull, it could easily have come apart from the rest of the skeleton.  Note, however, that there's absolutely no ivory present.

Anyway, in the VF article, Shoumatoff speaks with Iain Douglas-Hamilton, the founder and director of a Kenyan NGO, Save the Elephants.  STE monitors the elephant population in Samburu from their headquarters in Nairobi.  I sat next to Mrs. Douglas-Hamilton on the plane back to Nairobi from Samburu.  We talked the whole way about their foundation and what it does and the very small connection my employer at the time had to them.

For me, this made the article hit a little too close to home.  I might have seen some of the elephants they mentioned as being murdered recently.  I just can't imagine any ivory trinket being worth the life of one of these amazing creatures.  It boggles the mind, as they say.  Who would want this little guy to die?  (My boss snapped him in the Masai Mara.)

So, yesterday, I sat down to write and came up with an idea for a six- or seven-part story that gives the reader a glimpse into the entire disastrous cycle, from the buyers to the poachers.  I'm hoping I can avoid the trap that most social justice stories fall into--that they're boring and predictable.  I'm treating each small mini-chapter as a complete story in and of itself.  Hopefully, I can keep the characters and the conflicts interesting enough to hold a reader's interest.  I'm not planning on demonizing anyone, either.  Every story has two sides, and to keep the story interesting, it's my job to find out what those two sides are, even if I obviously don't agree with them.

I'll keep you all updated on how the story turns out.  In the meantime, if you read the article and happen to be moved, please consider donating anything you can spare to Save the Elephants here.    

Anatomy of a Fake-Cation

How many of you guys are headed out for a summer vacation?  How many of you guys can't afford it, but still need a little fresh air?  Allow me to introduce the concept of a "fake-cation."  If you're broke, like me, but still need to get out of your own space to keep your mind fresh for writing, like me, a fake-cation might be just the thing.

Here's how it works.  You go somewhere within driving distance, no more than two or three hours away, and stay one night.  It might be ten blocks from where you live.  It might be two hours from where you live.  But you treat it as if you were in Paris, staying at the Hotel George V.  The hubby and I have done this several times when we just couldn't afford a real vacation.  It works almost as well.

The first time we did this, in 2006, it was to use up a free hotels.com gift card I'd gotten through work.  We went to a cute lakeside hotel less than 30 miles away.  Still in our own backyard, essentially, but far enough removed from the slightly grimy area we lived in so that we got a mental break.  We went out to dinner and treated ourselves to an in-room movie (I never do this, so it felt like a real treat.  Plus, Miami Vice actually turned out to be a decent flick).  Overall, we came back rested and happy, and feeling like we did something indulgent.

We tried it again yesterday.  On the spur of the moment, we decided to get away to Reno.  Strange destination, I know, but due to a strange combination of factors, there were two errands we needed to run in the neighborhood anyway.  We drove up to Sparks, ran an errand, then dropped back down to Boomtown to blow out a game card in their kids' arcade area that still had about $7 on it.  We played air hockey, skee-ball, and random video games with Fast and Furious themes.

In all seriousness, never underestimate the good that can be done with $10 in a kids' arcade.  It can wake up any slumbering competitive skills, which is always a good thing for writing.  You know that get-up-at-4-am-to-train kind of drive that Olympic athletes have?  We writers need that same kind of commitment.  I know I don't always have it, least of all during lazy summer days.  If you're not a naturally competitive or aggressive person, it can be hard to rouse the slumbering beast.  Getting absolutely trounced in air hockey is a good way to get some of that determination back.  I lost at least three games and ended one in a tie.  Obviously, I suck at arcade games, but that's not the point.  I got a taste of what it feels like to look up at a scoreboard and be down 5 to 2.  Sometimes, we need to look at writing that way, too.  And we need to fight back.  Get that page count up.  Write even though you don't feel like it.  Finish that story even though you don't know where it's going or why it matters.  The only thing worse than giving up is never even playing the game.

Another nifty part of hanging out at Boomtown is the bar and its accompanying lounge acts.  For less than ten bucks, the hubby had a beer, I had a Jack and coke, and we listened to an R&B cover band do strange things like mash up Stevie Wonder with Color Me Badd ("I Wanna Sex You Up," if you were wondering).  Things that might seem cheesy in ordinary life are perfectly acceptable during fake-cation.

Unfortunately, Boomtown wanted $90 a night in order to stay.  Using the lobby's free WiFi, we checked out some other places and booked a room at Silver Legacy for less than half the price.  There's nothing like one of the gargantuan casinos to make you feel like Alice gone down the rabbit hole.  If it's a break from your physical and mental surroundings, I highly recommend some place like this.  There are a ton of people--great for people-watching and forming new plots and characters.  There are a ton of lights and sounds, which can sharpen your skills of observation.  (There's also a lot of cigarette smoke, which turned my eyes so red I looked like I was already drunk or high, but that's a small price to pay for feeling so far away.)

(Brief aside:  Silver Legacy, would it kill you to let people eat for less than $25 per person?  I am BROKE.  I LEFT your casino and went to eat at the Cal-Neva casino because, sensibly, they have a restaurant that offered me food for less than $10 a plate.  Harrah's, Circus Circus, and the Eldorado could not do this.  I have realized this is why you can afford to let me have a room for less than $50 a night--you assume I'm going to drop another $50 on dinner for two.  You assumed wrong.)

Anyway, on our way home this morning, we stopped in South Lake Tahoe and checked out some of the vintage cars at Hot August Nights.  I'm so not a car person, but even I can appreciate the awesomeness of these vehicles.  There was a Ford GT-40, which the hubby says costs at least as much as a McMansion (the photo is from 2008, but it's the same car).  Nice.  There was some purple car (yes, that's the actual make and model) with a mostly naked woman painted onto the front and back of it.  There were 1930s gangster cars with running boards, perfect for ye-olde-drive-by-shootings.   Plus, my personal favorite, a sparkly beige 1962 Chevy Corvette owned by a very lucky woman named Carol.  I also dug the thrashed matte black early 60s Austin-Healey with the skull shifter.  Rock on, dude, rock on.

I do have a point to all this rambling, besides trying to make my life look more interesting than it is.  The point is that as a writer, you have to get out of your own space to get new ideas.  You have to see things you don't see everyday to keep your ideas and descriptions fresh.  Smell things you don't ordinarily smell.  Watch people you've never seen before.  Just look at what America is up to--and then take the bits that interest you and turn them into a story.
 

Book Review: Rob Roy

So, lately, I've been feeling in need of a little swashbuckling to lift my spirits.  I've had this copy of Rob Roy for years now, but hadn't got around to reading it.  I figured a little Scottish warlord action would be just the thing to take my mind off money worries, rejection worries, am-I-really-cut-out-for-this worries.  After all, these guys had real problems to deal with.  You know, war, cattle thievery, duels, and whatnot.  I can honestly say that I've never had to deal with the prospect of having to pay protection money to a rogue Highlander to make sure my nice, fat herd of cattle stay put.

Warning to those who intend to read this book someday:  there will be spoilers ahead.  Proceed with caution.

Overall rating: 3.5 out of 5 stars
I was pleasantly surprised! The writing is fluid, events move quickly, and once the mysterious events are put in motion, I really did want to find out what the hell Rashleigh (the villain) has on Diana (the love interest).

The main character, Frank Osbaldistone, is the straight man here.  Don't look to him for wit or excitement.  He's there as a foil for all the super-interesting people around him. Basically, he decides he doesn't want to take over his father's massive accounting firm; oh no, this guy would rather write shitty poetry all day.  His father sends him to the family estate in the northern wilds of England.  There, he'll basically sit and rot among his lame-ass relatives until his father decides to call him back and give him another shot at the family business.

On the road to his family estate, he travels with another guy headed north named Morris.  Morris is a huge chickenshit who constantly fears being attacked by bandits.  Eventually, Morris and Frank separate and go their own ways.  (This is important later, because some crazy stuff happens to Morris after Frank leaves.)

When Frank gets to Osbaldistone Hall, he meets his lame-ass relatives who obey a simple mantra in life: eat, drink, hunt, repeat.  He also meets Diana Vernon, a cousin.  She's whip-smart, beautiful, and seems to do whatever the hell she wants around the place.  Frank soon notices, however, that there's something creepy and mysterious going on between Diana and one of his Osbaldistone cousins, Rashleigh.  Although Diana obviously has the hots for Frank (as he does for her), Rashleigh is always in the way--this guy pretends not to have a vested interest, but you just know he's working behind the scenes to eff up Frank's chances with Diana.  Not cool, dude.  Not cool at all.

One of the big surprises in the book, for me, is the fact that almost two hundred pages of it go by here at Osbaldistone Hall.  Not in Scotland.  Not a Roy Roy in sight.  (Okay, so technically, he did appear in disguise, but I'm not counting that and neither should you.)  I didn't have a problem with this because the goings-on at Osbaldistone Hall are interesting, and Diana Vernon is a freaking awesome character.  I got the sense that if she lived now, she'd be a Charlie's Angel or the woman Angelina Jolie's character only wishes she could be in The Tourist.

Anyway, after the 200-page mark, the real conflict begins to unfold.  Without delving too deeply into the plot, it goes a little something like this:  Frank-o flees to Scotland and participates in some intrigues relative to his father's business and a coming Jacobite uprising against the Hanoverian crown.  While in Scotland, you meet Rob Roy Campbell MacGregor and his wife Helen MacGregor.  Dude, Helen MacGregor is the reason they invented Valium.  This woman is seriously pissed off, like, all the time.  So pissed off, in fact, that she orders the murder of Morris.

The murder scene was riveting.  I wasn't sure Scott would pull the trigger on this one.  I kept thinking Morris would get out of it, but then the moment happened, and away he went.  I won't tell you how they got rid of him, but let's just say it's not the way you want to go.  Much like Vronsky's horse-racing scene in Anna Karenina, this is a scene that grabs your attention and refuses to let it go.  It doesn't matter when it was written or where or why--it's exciting, it's nerve-wracking, and you can't help but feel for these characters.

My reaction to Rob Roy was harder to define.  He is one of those characters that I didn't appreciate until he was off-stage.  While he was there, he was moderately interesting--balanced, fair, violent when he had to be, determined, and strangely honorable.  But you don't fully appreciate these qualities until you're stuck in a scene with Frank-o, Andrew Fairservice (annoying as hell!), and Nicol Jarvie (pleasant in a non-remarkable, only mildly annoying kind of way).  Then you realize what Rob Roy's character really brings to the table:  the experience and gravity of someone who has really lived.  He's killed, he's been imprisoned, he's escaped from prison, he's stolen some cattle, he's had his own cattle stolen.  Save Helen, none of these other characters can match the depth of Rob Roy's experience and it shows.

At the end of the book, Scott ties up all his loose ends.  You find out what was really going on between Rashleigh and Diana.  You find out what happens with the brewing Jacobite rebellion.  You find out how the major characters end their days.  Because the book was written in the 19th century, modern readers might get the sense that everything is tied up a little too neatly.  This was a convention of the time, though, so don't hold it against Scott.  It doesn't detract from the book's high points at all.

Overall, there are plenty of reasons to read this book:
*Diana Vernon
*Rob Roy
*Morris's murder scene
*Beautiful descriptions of Scottish clan life and Scottish landscape

There are also a few things you're going to have to take with a grain of salt:
*Freakin' long-ass passages in Scotch dialect.  If you're not into the whole "Scots wha hae" thing, you're in for some rough going once the characters make it to Scotland.
*Straight-man main character
*Andrew Fairservice

If you do read this one, I'd love to know what you think!

Some Good News...at Long Last

Finally, I have an uplifting piece of news to share with you all!

My short story, "Croatoa," was accepted into an anthology titled "A Rustle of Dark Leaves," to be published by Misanthrope Press.

I really crossed my fingers for this one!  I have a soft spot for this story. It's a dark, twisted, supernatural version of how the lost English colony of Roanoke might have been wiped out.  If you guys have never read about this colony, it's worth checking out.  Here's a National Geographic article that just might whet your appetite for the subject.

I'll keep everyone updated when I hear more about a publication date for this anthology. In the meantime, keep writing! You never know when good news is just around the corner.

That's What Friends Are For

This post is dedicated to one of my girlfriends--my best friend, actually.  We've both been having a rough time of it recently, with money and a bright outlook for the future often in short supply. But we're there to support each other as we chase our dreams and that's what matters.  I want her to know that no matter what happens with jobs and money, at least we'll always have each other.  

Here's the kind of friend Yan is:  she willingly agreed to be my date for my ten-year college reunion.  Who else but an amazing friend would subject herself to that kind of torture?

Yan, this one's for you.  

Long-lasting friendships are rare--for me, anyway.  It always seems that misunderstandings over boys, money, and lifestyles get in the way and eventually tear something down that once seemed invincible.  I had one particularly bad split with a former roommate who didn't approve of the guy I was dating (and married), or the fact that I ran off to Vegas to marry him without telling anyone.  While I can definitely understand that she was hurt when I didn't tell her about it, I can honestly say that I didn't even tell my own parents about it ahead of time.  I had to call them after getting back from Vegas and tell them I was *married.*  To a guy they'd met *once.*  In a close-knit family like mine, that call was torture.

I could have been ostracized or yelled at or disowned.  But was I?  No.  My family loves me, and they may not have understood why or how I did what I did, but they rolled with the punches and trusted my judgment. Every grandparent, aunt, uncle, and cousin has accepted Paul into the family with warmth and generosity.  And yet...one of my best friends couldn't do the same thing.  That still hurts, to this day.

I don't feel an obligation to live my life as an open book to everyone around me--we all have things we need to work out on the inside, on our own, before sharing them.  Honesty is a good thing and should be valued, but never at the expense of your sense of self.  When it came to marrying Paul, it was this strange but magical moment that just happened.  One moment, in all of life, where only two people exist.  And I took hold of that moment, seizing it for all it was worth.  When it was time to come down from that high, I looked around for a handhold and the people who I'd left behind.  Almost all of them welcomed me back.  Almost.

It takes a special kind of friend to roll with those punches and accept others for who they are--even when they do things you don't like or approve of.  Yan is one of those very special people.

We met when the University of California paired us as roommates.  At first, all we knew about each other was a name and an address.  As we wrote to each other and then finally met on the dorm's move-in day, it became clear to both of us that we were a lot alike.  Both vulnerable, deep thinkers, and self-confessed late bloomers, we went through so many growing pains together during those four years of college.  During and since college, we've had periods where we don't speak.  Sometimes those periods lasted for years.  Even when we weren't speaking, though, I always knew we'd reconnect.  I knew we'd never be out of each other's lives for good.  We were too alike and had been through too much together to throw in the towel.

Essentially, we had to go out and live our lives.  We had to make mistakes.  We had to have opportunities missed, relationships ruined, and tears cried to fully understand where the other was coming from.  But now that we've weathered those storms, I know our friendship is stronger than ever.

That's why I know that even if our dreams don't come true quite the way we want, we'll still be there to help each other through the fallout.  If I never become a published writer, it's okay.  I know she's still got my back.  As long as I want to strive for it, I know Yan is there to tell me she believes in me, 110 percent.  She's my biggest supporter, in fact!  And if her boutique doesn't take off the way she wants it to, it's okay because I've still got her back!  I'll be there to tell her she's still one of the bravest people I know for even trying it.

The great thing about Yan is her ability to grab the bull by the horns (or by the balls, if you've seen Never Been Kissed).  If she wants something, she'll fight for it.  And if it doesn't work out, she'll sit back and analyze the situation to figure out why.  She thinks about things--the causes of things.  She uses what she's learned, about people and situations.  She looks for the positive and the bright side, but she doesn't back down from the darker side of things, either.  She can see your side of the issue even if she doesn't agree with you, but she's not afraid to tell you you're wrong.  

I consider myself incredibly lucky to have Yan in my life.  She's funny, beautiful, smart, insightful, dedicated, and a constant inspiration. There is no one better to have in your corner.  Yan, I love you, girl.  I honestly don't know where I'd be without you.  I miss the days when we'd sit on your balcony in Marin, drinking wine or cocktails, and wondering where the hell our lives were going....after we came back from a shopping spree at Ross or Marshalls, of course.

There's a questionnaire on the last page of every issue of Vanity Fair, called the "Proust Questionnaire." One of the questions asks you when and where you were most happy.  I think those weekends in Marin with you would be my answer.  Shopping, eating, drinking cocktails, analyzing boyfriends and ex-boyfriends, watching Sex and the City...I don't think it could ever get better than that. You, my friend, are when and where I was most happy.

Now, if you've gotten all the way to the end of this post and live in the San Francisco Bay Area, please go say  hi to Yan at her boutique!  Tell her I sent you.

Yan's Fashion Sense at 1324 Noriega, between 20th & 21st Avenue
*on Yelp
*on Facebook

Sewing Project #1: Pajamas

I mentioned in the last post that I'd meant to show you guys some of the sewing projects I've been working on. I finally dragged out the camera yesterday, so here goes nothing.

Sewing Project #1: Pink Pajamas

Why on earth would anyone do this?
My Christmas present to myself was a brand-new sewing machine and the promise that I'd teach myself to sew. My mom sews. My sister sews. My grandma sews. It's just something the women in my family seem to do. For the longest time, I didn't see the attraction. I love to shop.  It's almost criminal how much I love to shop. But that's the funny thing about being broke--I'm no longer able to do what I love, at least not without racking up an unreasonable amount of credit card debt.

Plus, the older I get, the more I'm realizing that clothes really do need to fit well to be attractive. And I have a short torso, which makes all the clothes in my size hang wrong. I don't know if I've started shrinking already, or if I just never noticed this before, or if the clothing manufacturers are making things for longer-torsoed people these days. But it seems that everything I try on has straps that are too long, which cause a bad fit, a sloppy look, and way too much cleavage.  So, for the first time in my life, sewing seemed like an answer.  I can make my own clothes, ensure they fit, learn a valuable and vanishing skill, and still acquire new things for the closet.

So how did it go?
Um, yeah.  The first sewing project I tackled was a pair of pajamas.  Unbeknownst to me, this was probably a bad choice for the first project.  For those of you who also sew, I used McCall's M5992 pattern, shown below.

I made the pants first, figuring they'd be easier than the top.  I was only partially right.  My first mistake was sewing the crotch shut.  Paul still can't figure out how my mental faculties failed to alert me that this was a really bad idea and so not what the pattern was telling me to do.  But spatial imagery and I don't always get along.  In fact, we're barely on speaking terms.  Hence the sewn-shut crotch.  (This issue will rear its ugly head again in my next sewing post.)

Once I figured that out, I had to rip out all the seams and start over.  Then, once I got them together a second time, I realized I cut the wrong size.  I could barely get the friggin' things over my hips.  (Vanity, thy name is first-time sewer!)  Apparently, I am a size medium instead of size small.  So then I had to tear out all the seams again and re-do them with the most minimal seam allowance I could.  The third time was a charm, though, and the pants were now complete.

If you're a first-time sewer, like me, the only thing I can tell you about these pants is DO NOT, FOR THE LOVE OF GOD, MAKE THE STUPID DRAWSTRING THE WAY THEY TELL YOU TO. It is next to freaking impossible to make a spaghetti-sized tube of fabric and then turn it inside out without wasting hours of your life. It must have taken me three or four hours to do, and involved the following equipment: lacquered chopsticks, safety pins, straight pins, and at least four whiskey shots.  I kid you not.  Save yourself.  Abandon ship. Just use ribbon, like any sensible person would do.

So that was the end of the pants.  Next, I tackled the top.

The first parts of this were surprisingly easy. Pocket? No problem.  Sewing front of top to back of top? No problem.  The collar was where I ran into trouble.  I still have no idea how to put a collar on correctly.  I fudged and did it my own way, which is why I have a random rough edge where a clean seam should be.  I don't think you can see it in this photo, but if you look below the neck of the hanger, you might see what I'm talking about.  I'll get another shot at this one, because I bought flannel, too, for a second pair.

Anyway, the collar lays mostly flat, as you can see. There are a few rough spots, but overall, I was pretty impressed that I got the thing assembled and it looks like...well, a real collar.  I was also pretty impressed that the set-in sleeves worked well.  I only ended up with one pucker on one shoulder.  If I was a perfectionist, I would have torn out the seam and re-sewed it.  But at that point, I was just glad to still be alive.  I left that pucker there.

Next came the buttonholes.  I had been dreading these for quite some time.  (The whole process of making this pajama set happened over weeks, if not months.  It was spring semester, and I could hardly find a few spare hours to work on it what with class and homework and reading assignments and all.)  But when I sat down to do them, they were surprisingly easy.  The buttonhole function of my sewing machine worked quite well.  What took forever was ripping the actual buttonhole.  Before I did it, I had no idea that you created buttonholes by ripping the fabric.  That was kind of disturbing to find out.  There is no real clean or easy way of doing it, unless I'm missing something.  It was a backbreaking hour or two of squinting at the lines of thread and praying I wouldn't rip into them with my seam ripper. In the end, they worked--and even better, they lined up almost perfectly.  Phew!  That had been one of my biggest worries for the project.  What I effed up the buttonholes?  There's no recovering from that mistake.

So I came to the end of my first sewing project, alive and well and with a new pair of pink pajamas.  I'll tackle this pattern one more time.  I bought a turquoise flannel print for another pair that I'll do sometime this fall.  Hopefully this time, I won't sew the crotch shut!

Stay tuned for the next sewing project I'll talk about--flannel boxer shorts.  It doesn't sound super exciting, I know, but this time, the hubby gets in on the action and we both get mystified by the pattern instructions.  Good times!  

A Funny Thing Happened on the Way to Key West

I meant to post about something else entirely today (teaching myself to sew), but first I need to iron the things I've sewn so I can take non-shitty pictures of them, and ironing sucks, and it's hot outside, and no one wants to slave over a hot iron when it's hot outside, so I'll try to get it done later tonight, and oh, hell, I guess I can always tell a really embarrassing story instead of posting something useful or educational...

Here goes nothing.

Paul and I drove out the Keys a few years ago for summer vacation. We stayed in Marathon Key because it was cheaper than staying in Key West. We booked a beautiful little cottage-style room for two nights. Once we got there, one of the first things we noticed about Florida, and southern Florida in particular, is the fact that it has bugs. Bugs the size of small children.

I hate bugs the way Indiana Jones hates snakes.  I hate spiders most of all, but really, my hatred extends to any bugs that can crawl into places I might find them. One time, on choir tour senior year, a cricket flew out of my backpack in New Mexico and I almost fainted.  True story.

So. Marathon Key. We check into our room and prepare to relax. It's nighttime and we've already driven from Hollywood, and all we want is to chill out and get a good night's sleep. Paul goes to take a shower.  But first he has to kill the shower's other inhabitant, an enormous palmetto bug.  That sucker was as thick as a carrot and as long as my pinkie finger (I have really long fingers, people).  It hissed at us.  Paul smashed it with his shoe, but some of the guts stuck to the floor.  Really gross. I tried not to look at the wing remnants as I took my own shower.

Afterward, I put my pajamas and flip-flops on and padded over to the bed.  Suddenly, I heard another hissing noise--the exact same noise that freaking bug made before Paul slapped it upside the head with his Vans.  All I could think was that another bug was somewhere in the room, probably near the bed.

I jumped onto the bed and screeched, "There's another one!  I heard it!"  Panicked, I scanned the room for a crawling insect the size of a mini-golf scoring pencil.  I didn't see anything, but I knew what I'd heard.  Paul made a more thorough investigation.  He lifted up the tiny refrigerator, looked under the bed, and moved the nightstands.  He didn't find anything.

Still wary, I decided to put my feet on terra firma.  I put one foot down on the floor and instantly heard the hissing again.  I shrieked, swore, and jumped back up on the bed.  "You heard that, too, right?" I asked.  Oh, yes, Paul had heard it, too.

He redoubled his efforts and checked even more dark corners of the room.  I started freaking out.  How can I sleep in a room where there's a giant roach waiting to share the bed?  I told Paul what I was afraid of, and he said he'd check the bed sheets if I'd get off it.  That meant touching the floor, which I wasn't happy about at all.  Those fuckers moved fast, and if I felt those tiny bug feet crawling over mine, I knew I'd flip out.  For sanity's sake, it seemed safer for me to stay on the bed.

But my husband's sanity prevailed over mine and I got down off the bed.  Slowly, one foot at a time, I came back down to earth.  But as soon as I took one step away from the bed, I heard it.  That prehistoric shitbird was hissing at me again!  The gall!

I ran over to the single chair in the room and jumped up on it.  Then the bastard hissed again!  It would have been funny if I weren't sure it was looking for a way to tunnel into my suitcase for maximum heart-attack impact the next morning.  While I stood like a demented flamingo on a rickety metal chair, Paul duly took apart the bed, pushing the mattress off the box spring and de-sheeting it.  He looked everywhere.  He looked under the bed, again.  He checked inside our suitcases.  He checked the bathroom.  There was no bug to be found.

"But I can hear it!" I whined.  "It's here somewhere!  We have to find it."

But where else could we look?  Paul had already exhausted pretty much every hiding place the small room offered.  He fixed the bed and then sat down on it.  "Come on," he said.  "Let's just watch some TV and try to relax."

Now, relaxing when there's a Jurassic Park-sized bug on the loose is not in my DNA.  But I tried.  Because it was Paul's vacation and not just mine, I tried.  I got down off the chair...and damned if that bug didn't hiss at me again!  This was too much.  I had never been targeted so fiercely by a roach before.

That's what made me wonder.  How could the fucker know exactly where I was and what I was doing?  Was it Superbug?  Did it have eyes in the back of its head?  If it did, I had to catch it and sell it to scientists and retire to Key West permanently.

I took one step forward.  The bug hissed again.  Was I getting warmer?

I stepped again.  Another hiss.  What the hell was going on here?

Then I figured it out.  The bug only hissed when my feet touched the floor.  It only made noise when I stepped toward it.  One more test confirmed my theory:  I was, in fact, "wearing" the bug.

The hissing noise was apparently some defect in my Old Navy flip-flops.  Brand new and unworn until that day, they apparently made evil hissing bug noises when they were wet and then stepped on.

The moral of the story:
*Florida is full of bugs.
*Old Navy flip flops make evil hissing bug noises when they're wet.    
*It is absolutely essential to marry a man who understands your fear of bugs.

Books vs. Boyfriends: Finding the One

Have you guys ever had a revelation while working out? I had one today.  I went running by the lake, and about five miles in, I finally saw the connection between the books I've written and the boyfriends I've dated.

Here's the context: I've been ridiculously depressed because my thriller manuscript isn't getting any love. I put my heart into it and I love this book with an unhealthy passion. But it's just not working out in terms of getting an agent.  This is what's put me in such a terrible mood.  But today, I can finally see a bit of light.  Writing books and submitting them is no different than dating. Here's the proof:

THE FIRSTS
Boyfriend, A.: We had nothing in common other than being in the same college. He was on the rebound and I'd never dated anyone in my life.  I fell hard and ended up chasing after him for years, allowing myself to fall into an on-again, off-again pattern that was emotionally destructive and no good whatsoever for my self-esteem.

Book, vampire historical: Everyone else was writing about vampires, so why shouldn't I? I thought it would catapult me into some sort of Stephenie Meyer afterglow.  I wrote and rewrote and rewrote for years, in the same kind of on-again, off-again pattern that was so destructive with A. Instead of realizing I could (and should) move on, I stuck with what was familiar instead of branching out into something new.

THE SECONDS
Boyfriend, R.: A guy who was fun to be with, actually liked me, and had no problem expressing emotion. He was everything A. wasn't and provided the validation I never got in that first relationship.  Of course, this was a mistake, too. You can't date someone just because they're the opposite of someone who hurt you.

Book, lighthearted mystery:  After the historical vampire epic, I went for a lighthearted romp:  fast dialogue, lots of wisecracks, absolutely no historical research required. It was what I needed to convince myself I could write another book without sucking up years of my life.  This book was better than the first one because of what I'd learned writing the first. Still, it didn't quite fit my style--much like R.

THE THIRDS
Boyfriend, J.: Smart, funny, British, made a good living, had a cat, turned me on to Kate Bush...so many great things here.  I thought this man had everything and I fell hard, an elevator plunging from the the hundredth floor with no support cable.  We shopped together, we tried new restaurants, and had lovely times strolling through the Haight or the Mission. At one point, he mentioned getting some of his grandmother's jewelry out for me. True love, right? Wrong. He decided to try and go off his antidepressants on his own, bailed on meeting my parents, and decided he was not looking for commitment. He spent the next two years dating a number of girls, including me. I convinced myself that if I hung in there long enough, I'd be the winner. Not so.

Book, female-oriented thriller: This one is breaking my heart right now. Like J., it was supposed to be the one.  J. was supposed to give me a ring and this book was supposed to give me a contract.  I had such high hopes that agents and editors would love it as much as I do.  Everyone says you're supposed to write the book you want to read.  I did that, but it still didn't work.  Much like the British boyfriend, it can't be forced into generating that commitment. It seems unfair that no matter how much effort you put into a relationship or a book, you are unlikely to get the result you want.  But that's how fate works. You don't control it.  It controls you.  And sometimes you don't know realize any of this while you're living it. You have to get through it and get past it to see what was really happening.

THE FOURTHS
Boyfriend, J.: Another J!  This time, it was a short relationship with a co-worker, someone uncomplicated and fun. We bonded over video games, but had little in common.  Still, he seemed blissfully normal after the emotional nuclear aftermath of the previous J.

Book, category romance:  This one didn't last long, much like J.  I wrote it in two weeks and revised it in one.  It's not literary.  It's not going to set the world on fire.  But it was fun, fast, and easy.  I wrote it as I was querying for the thriller. Of course, I didn't know at the time the thriller wouldn't be accepted, but at the same time, after writing a complicated thriller with a mentally ill heroine, it was refreshing to write something fast, fun, and dirty.

THE FIFTHS
Boyfriend, N.: A college friend I reconnected with at a friend's party later in life. He was nice and very upstanding, the sort of person about whom you could say, "He makes me want to be a better person."  He liked some of the same books and some of the same music, but there wasn't enough of an overlap to sustain a real connection.  There was no spark, nothing deeper that would make me pine for him when he was away. The relationship lasted two years because it was comfortable.  But no one marries comfortable. He took a job across the country. I stayed in California and wondered why I'd let two years of my twenties slip away.

Book, literary mystery: I just started writing this one, actually. This is my first attempt at a literary novel. Now I'm wondering if it will end up like this boyfriend, serious and steady but boring...and also not the one.

THE SIXTHS
Boyfriend, P.: We celebrated our fifth wedding anniversary on July 1st. It wasn’t a given that this was it, believe me.  I broke up with him a few weeks into the relationship, and he broke up with me six months in.  That break-up was on a Sunday. Friday night, he came back to my apartment and asked me to marry him, to run away to Las Vegas for the weekend.  I packed the only white dress I had in my closet and we hopped in my Mazda for a drive into the desert that lasted a whole day.  We went to a pawn shop where I fell in love with the first ring I saw.  He bought it for me and we went to Chapel of the Bells. That Saturday night, we got married.

Book:  I don't even know what this one will be, since I'm still writing book #5.  Does this mean the universe might smile on me this time?  I guess I won't know until I get there....

Realizing all of this has made me more accepting of the thriller's failure. At the time, I felt so bitter and angry when J. and I didn't end up together. I couldn't understand it. It wasn't fair!  But fairness has nothing to do with it. It's about being ready for something, about finding just the right fit.  I guess this book isn't the right fit, even though I want it to be so badly it hurts.  I wouldn't have been happy married to J.  It had to be P. So I guess I'll have to be patient with the books I write, the same way I was for all the men I dated.  They can't all have stories that end like this:

The Cheese Stands Alone

Last week was a surprisingly rough one on the writing front. Combined with a perfect storm of rejections and Category 5 PMS, it landed me in the depths of despair. Everyone, it seemed, had something negative to say.  Even things that should have been positive had their negative sides revealed. Suffice to say, it felt like the universe was kicking me in the teeth.

Then, today, I remembered a line from a song I haven't heard since elementary school:  the cheese stands alone. That is going to be my writing mantra from here on out.

Writing is a solitary pursuit.  It is not meant to be done with others.  It is not meant to be done in anticipation of what others might think or say.  Somehow, I allowed myself to be so swayed by what other people were doing or saying that I lost my focus.  I stopped having fun and enjoying the ride.

The problem, I think, has two causes:

(1) I want to be a published writer so badly it feels like it will literally kill me if it doesn't happen.  Every rejection feels like a nail through the heart...or the head.  I know these thing shouldn't be taken personally, but this is my dream.  This is my everything.  There is no way it won't hurt.  I can't just walk away from this.  I have to keep trying.  In essence, it's a torture that may not end.  Ever.  But, much like the Thorn Birds, still I do it.

(2) I spend a fair amount of time each day reading writer blogs, agent blogs, editor blogs, and reader blogs.  This is not good.  Maybe other people can handle all those voices in their heads, all those agent posts wondering why the perfect query hasn't dropped in their lap yet, but I can't.  In my mind, I've sent them the perfect query and been told no.  I've submitted a book into which I put everything I have to give.  If you read lots of agent posts, they repeatedly tell writers this is all they need to do.  It is not.  What they don't tell you is that certain genres are off-limits unless you're a mega-seller.  But then their blog posts repeatedly claim that if you write what you love and write it with heart and skill, your book will find a home.  I'm still searching, so I have to take this with a grain of salt.  It's part of the game, I know, but I can't then sit back and read posts lecturing writers on no-nos that I haven't committed without some degree of bitterness.  Lots of degrees of bitterness, actually.  This is probably natural for lots of writers, and many of you probably deal with it better than I do.  But because I want this so badly, my blood burns for it.  It makes me crazy to read too much about the industry or other people's successes or failures.  It makes me think about having what they have or wanting what they want instead of shutting the hell up and writing.  I start wondering what each successful person did that I'm not doing.  I go mad with jealousy.  It keeps me from being a happy person.  This makes my husband very angry, and I already burden him with a hefty number of personal oddities.

The cheese must stand alone.

I'm going to try limiting my blog reading to one day a week, where I madly skim what's been going on, either preceded or followed by a shot of whiskey.  Being somewhat bitter about the publishing industry and the difficulty in getting an agent is a huge drawback when all I want is to be accepted by both.  The only thing I can do to help myself, in this case, is focus on my writing instead of knowing everything that's going on in the industry.  And if I write what I love and I do it to the best of my ability and it still doesn't happen for me, well, I'll cross that bridge when I come to it.