Good morning all, and welcome to Open Mic Saturday. This is the place
to share your news and perhaps do a little bragging. If you're writing a
novel: how much progress did you make this week? If you're writing
short stories: did you finish anything or submit anything this week? If
you've sold or published anything recently, when is it coming out and
where can we find it? In short, as a writer, what kind of progress did
you make this week?
Or what else is on your mind, that you feel like sharing with the group here?
Saturday, June 30, 2012
Thursday, June 28, 2012
Colorado Springs Shout-Out
To our friends in Colorado Springs: we've been watching development of the Waldo Canyon Fire with considerable concern.
If you'd just check-in and let us know how you're doing, we're greatly appreciate it.
Thanks,
~brb
If you'd just check-in and let us know how you're doing, we're greatly appreciate it.
Thanks,
~brb
Tuesday, June 26, 2012
World Enough, And Time
Don’t Tick Off the Tech Writer
LadyQuill has been quiet of late.
She was offered her last book contract (Google Secrets, available now at Amazon, grab it quick before they sell out!) three weeks before her birthday, so I bought her a new laptop as an early birthday present. Her old one had seen better days and just was not up for the rigors of an 800 page technical book.
I got her a good one, too. Dell. Full keyboard with keypad, nice wide screen, and she loved it. Cranked out that book and it worked like a charm.
It’s starting to show it’s age, too, though. The B and C keys failed. This wasn’t that big a deal, as she uses a USB keyboard, but it’s still something that needed to be fixed.
Then the hard drive went out.
Now, LadyQuill has had hard drives crash before. This computer had a separate partition set aside, called DataDrive, with all of her files on it. The most important stuff was backed up to “the cloud.” So, while a crashed drive for most anyone else is a total disaster, for her, it wasn’t much more than a low-level annoyance; the DataDrive partition was even still accessible. She started working from a bootable CD while I handled the tech support duties.
Yes, I’m the one who needs to speak to tech support. The reasons will become clear.
I checked the Dell website, and found she still had 70 days left on her warranty. Then I called the 800 number.
The first tech I reached--I’ll call him L1--had an accent, but nothing I couldn’t deal with. His biggest problem, though, was that the warranty was due to expire. He tried four different times to get me to extend the warranty, and finally passed us through to the next level.
That’s where the real fun began.
The second tech, L2 for short, was totally and completely chained to his script.
“Look,” I said. “I can tell you this hard drive is bad.
“My wife keeps three different versions of Linux running on her laptop. If one of them crashes out and refuses to boot, she can switch to another. This system had Ubuntu, Debian, and Arch installed, and none of them will boot. The system will boot just fine from a CD or a Knoppix thumb drive, though.
“Now, she has tried three different Linux installs on it and none of them work. One of them ran a hard drive test, and that program said there are over 600 bad sectors in the Master Boot Record. This drive is hosed, and my wife would like a new one under the warranty.”
“Well, we can’t just send you a new drive,” L2 said. “Here’s what we’re going to do. We’re going to use the Maintenance Partition to wipe your hard drive and put Windows Vista back on it, like when you bought it. Once Windows is back up and running, that will probably fix your keyboard problem, too.”
Right. Installing Windows Vista solves everything, and the two keys that have not worked for weeks--under multiple Linux versions, too--will magically start working again. Immediately after this, Icehawk the Barbarian will headline on Broadway and Vidad will be the opening act for the Stones’ next tour.
“I’m sorry, but we accidentally wiped out the maintenance partition,” I answered.
That was actually my fault; I tried to install MySQL on the laptop, screwed up the instructions, and fried an Ubuntu install, and then wiped out both the Windows partition and the maintenance partition in the repair process...but L2 didn’t need to know that.
“My wife doesn’t use Windows. We installed Ubuntu on it the day it came home. They didn’t even give us the CDs.”
In the course of speaking to these two, I burned up nearly an hour and a half. I could not get L2 to budge an inch; the only possible solution was to wait for them to send us replacement CDs, then restore the maintenance partition, then restore Windows, and that would fix anything that could possibly be wrong with it. And, on the very remotest of possibilities that it did not...then we would need to take the laptop to the certified Dell shop downtown--which would very likely then need to send the laptop to Dell for the actual repair.
Really?
While waiting for the CDs to arrive, we decided to short-cut the entire issue. We took the laptop in to the shop, and explained the situation. The guy behind the counter looked mystified; he did not understand why Dell bothered to involve him, but he said he would try.
Of course, that meant that LadyQuill was without her computer.
...can you say withdrawal symptoms...?
The shop tried three times to speak to Dell, and got even more of a runaround than we did. Finally, on the fifth day of laptop cold turkey, they called me and asked me to call Dell. “They should give you a reference number,” he said, “which will authorize us to repair it under the warranty.”
Okay, I can do that.
What I did not know at the time was that Dell had sent LadyQuill a Customer Satisfaction Survey.
She ignored it at first, but by the fifth day without her laptop, she was steamed. Not only did she score them straight zeroes across the board, but she wrote in two or three paragraphs for each and every question. The final draft was over three pages long, and ended with “I will never buy another Dell product, ever again.”
I called Dell, and got a different guy named L1, and L1 tried yet again to convince me to extend the warranty. “If the warranty dies, then you won’t get free maintenance anymore,” he said, desperate to change my mind. “You’d have to pay someone to change out the hard drive if it died then.”
“If the drive dies, I’ll fix it myself,” I said. “In fact, if the drive had waited another 71 days to die, I would have had it fixed within three hours, including driving time into town, and my wife would have had an operating system on it in less than an hour after that. I’m only on the phone with you because the computer is still under warranty. You’ve kept us jumping through hoops for over a week. Would you please put us through to someone who can actually help us?”
I had decided that L1 was not really tech support. His entire job is to convince the caller to buy more warranty, whether they need it or not. Deflated, he finally abandoned the sales pitch, and passed us on to L2--who, at any other tech support phone bank, would have been L1.
L2 started in on the same “okay, let’s get out the CDs we sent you” script, and I told him the same thing I had just told L1.
“All we want is a new drive,” I said. “The computer is in the shop. If you’ll authorize them to fix it, you don’t have to do anything. In fact, if you’ll ship me the drive, I’ll even do the work, and you can save yourself a few hours by not bothering to install Windows on it.”
“I’m going to look at your case records,” L2 finally said. “Let me see if there are any other options.”
I heard his voice change. I distinctly heard a kind of strangled "squeak" sort of noise, like you'd expect a stalking cat to make when the mouse whips out a flaming sword and cloak of invulnerability. I'm making the assumption that he stumbled across that Customer Satisfaction Survey.
“I need to go speak with my supervisor,” he said, very quietly.
I was on hold for quite a while.
When L2 came back, he said “If I send a new hard drive to the same address where we sent the CDs, would that be okay?”
I pressed him on the keyboard, and he added that to the order without skipping a beat.
The spare parts arrived less than twenty hours later. I brought the laptop home the same day. And exactly 47 minutes after she cut open the box, LadyQuill was running Linux on a laptop without a trace of Windows software on it anywhere.
Allan Davis is a writer/photographer/database programmer in southeastern Nebraska. Before he was a programmer, he was a tech, and though woefully out of practice, can still change out a laptop hard drive with the best of them.
Just don't ask him to install MySQL.
The Slushpile Survival Guide
A Manuscript's Odyssey, Part 5
Part One | Part Two | Part Three | Part FourAs ridiculous as it may seem now, a year ago, when we were first ramping up to launch STUPEFYING STORIES, we worried about whether we'd be able to attract enough submissions to make it work. Ergo at that time we decided to make it a sticking point that every manuscript received would receive the full attention of the entire original editorial team. Every new submission that came in would be posted on our private file-sharing site, read by everyone, and then the team would discuss the story and decide whether or not to accept it.
It was a nice vision.
It was also insanely impractical.
Within a few weeks we'd completely overloaded our original file-sharing site and exceeded its capacity. Not too long after that we'd completely overloaded our original editorial team and exceeded their capacity, too, and they began to show signs of serious story-fatigue. As the trickle of submissions became first a stream, then a flowing river, and then a raging torrent, our submissions-handling process needed to evolve quickly or die.
It evolved, in fits and starts.
We went from sharing every individual file that came in to posting zipped-up weekly round-ups. We went from "everyone reads every submission" to "each editor takes a portion and forwards only the best stories to the entire group." We went from a voluntary opt-in system in which editors were allowed to pick the stories they wanted, to assigning blocs of work and nagging people when they fell behind. We started pre-screening stories and rejecting the obviously unsuitable submissions before they ever made it as far as the slush pile. (Believe me, read a few hundred stories and you will develop if not an infallible sense of what's good, at least the ability to catch the unmistakable whiff of True Crap the moment you see the first line. Or sometimes even just the title.)
Sidebar discussion:Every now and then some well-meaning person asks, "Why not do what [magazine] does? Let the slush pile accumulate for a month," (or two, or three), "and then pick a Saturday, have everyone come over to your house, order in some pizzas and beer, and deal with it all in one afternoon and evening. It'll be fun!"Well, for one thing we're an Internet-based company, spread out over two-thousand miles and three time zones, so that puts a serious crimp in the idea of our all meeting at anyone's house. (In fact I don't think we've ever all met in person.) For another, on those rare occasions when we do get together, we can't even agree on which beer to buy. So for us to reach agreement on which stories to buy in the space of just a a few short hours...
We went from "let's identify promising writers and work with them" to "if you can't be an advocate for the story as-is, reject it."
That last one was a difficult step to take. We've all come out of writing group backgrounds and have painful memories of what it was like when we were just starting out. We all have this innate desire to behave as if we are still in a writer's workshop, and to identify promising new talents and then spend the time it takes to coach them through the rewriting needed to turn their interesting student-grade projects into polished professional work. And to be honest, of the stories we've published so far, a few of my favorites came to us in just exactly that way.
But ultimately, we had to let go of that. As the first winds of the Great Submission Blizzard of 2011 began to howl and the story-drifts began to pile up in the lee of the garage, it became apparent that we had to make a choice: we were either running a writing workshop and trying to teach people how to write or building a fiction publishing company. There simply was not time and energy enough to do both.
And then the Heavens opened up, and it being winter, the torrent of stories became an avalanche, and we began to realize that we were in real trouble.
...to be continued...
Saturday, June 23, 2012
Open Mic Saturday
Good morning all, and welcome to Open Mic Saturday. This is the place
to share your news and perhaps do a little bragging. If you're writing a
novel: how much progress did you make this week? If you're writing
short stories: did you finish anything or submit anything this week? If
you've sold or published anything recently, when is it coming out and
where can we find it? In short, as a writer, what kind of progress did
you make this week?
Or what else is on your mind, that you feel like sharing with the group here?
Or what else is on your mind, that you feel like sharing with the group here?
Monday, June 18, 2012
The Slushpile Survival Guide
A Manuscript's Odyssey, Part 4
Part One | Part Two | Part ThreeHow do you help boost your manuscript up out of the undifferentiated muck of the slush pile so that it gets the level of editorial attention you want? The rules are simple and should seem familiar...
In fact, they're so simple and familiar that as I was writing this column, I got déjà vu all over again, broke off for a few minutes' search, and sure enough, I wrote a column about this years ago. Liberally sampling from my own earlier article, then (and bearing in mind that it was written back in the days of printed manuscript submissions and print publications):
[...] The following numbers are gleaned from conversations had with a number of major magazine editors back in the late 1980s but still should be reasonably indicative.
In an average month, Joe Editor, head honcho at Stupefying Stories Magazine, [Huh? Was I prescient or what? ~brb] receives 600 manuscripts and publishes eight. How does he bridge the gap between the two numbers?
- 100 manuscripts are rejected on receipt, because they're either
- addressed to the previous editor who quit five years ago, thus indicating that the writer has not looked at a recent issue of the magazine
- addressed to "Ms Jeo Edtori," and if the writer can't even get that much right, what hope is there for the rest of the manuscript? [I will tolerate misspellings of my name -- after all, I've been listening to people mangle the pronunciation of it all my life, so what's a typo or two? -- but I've decided I will no longer tolerate submissions from people who can't make the effort to get the name of the publication right. ~brb]
- addressed in crayon, or submitted in an envelope covered with cutie-poo pony and butterfly stickers, in the apparent and misplaced hope that this will somehow draw attention (it does, but not the sort of attention you want) [This still happens, only now it takes the form of photos, graphic images, or animations and Java crapplets embedded in the cover email. Doing so still indicates that the would-be author is a hopeless putz. ~brb]
- or have a return address indicating the submission is from a known crank or jerk that Mr. Editor would never in a million years publish even if he or she was the last living writer on Earth or any of the nearer planets [This is one area where technology has made an enormous difference. Thanks to auto-responders and email filters, it's now possible to establish a "Known Twits" list and stop the real jerks before they ever make it as far as your inbox -- until they figure out what's going on and get a new email address, which they always do. ~brb]
- 100 manuscripts are rejected based on the rest of the cover letter, which either describes the submission in such tedious detail as to remove all desire to read the manuscript or else includes palpable bullshit or even threats. (Yes, people have been known to send cover letters that include lines like, "My good friend Gordon Dickson read this story last week and said you'd really love it," [Gordie died in 2001], or "Don't even TRY to steal my story because I have COPYRIGHTED it and I have a VERY GOOD LAWYER!!!!")
- 100 manuscripts are rejected based on the first page of the manuscript, which either shows that the writer has no knowledge of standard manuscript format, thinks a hideously overused cliché is a marvelously original title, has sent a stained and shopworn wad of paper that's obviously been bouncing around for awhile, or is simply so bad a writer as to be beyond all hope of redemption. [Okay, the "stained and shopworn paper" thing never happens anymore, and I don't agonize over standard manuscript format as that's just more cruft we have to strip out in the process of coverting the ms. to .epub. However, the "is simply so bad a writer as to be beyond all hope" part is such a big topic that it deserves its own column, and will get that column soon. ~brb]
- 100 manuscripts are rejected based on the first two pages of the manuscript, which are decently written but such an obvious setup for a "twist" or "pun" ending that Mr. Editor jumps to the last page and—yup, sure enough, the narrator is a lobster in an aquarium in a seafood restaurant! And given that the whole story hinges on keeping this fact hidden from the reader until the very end, this is also where Mr. Editor's interest ends.
Which leaves Joe Editor with a considerably more manageable stack of 100 manuscripts, in which to find the eight that are well-written, interesting, the right length, and not too much like something he already has in inventory to be worth buying. And if he has the budget for it he'll probably end up buying ten manuscripts, just in case next month's batch of submissions only includes four acceptable stories.
There now: that doesn't look so daunting now, does it?
...to be continued...
Labels:Slushpile Survival Guide
Saturday, June 16, 2012
Open Mic Saturday
Good morning all, and welcome to Open Mic Saturday. This is the place
to share your news and perhaps do a little bragging. If you're writing a
novel: how much progress did you make this week? If you're writing
short stories: did you finish anything or submit anything this week? If
you've sold or published anything recently, when is it coming out and
where can we find it? In short, as a writer, what kind of progress did
you make this week?
Or what else is on your mind, that you feel like sharing with the group here?
Or what else is on your mind, that you feel like sharing with the group here?
Friday, June 15, 2012
To your scattered websites go
As the Friday Challenge continues to evolve into whatever it is that it's evolving into, the FC crew are branching out to other interests and other sites. For at least the next few Fridays I'd like to use this Friday morning post to start collecting links to our members' various projects and productions. For example, today:
Henry Vogel has just posted chapter 9 of his novel-in-progress, Scout's Honor. Read it today at Cliffhanger TwoFifty.
David Goodman (a.k.a. Vidad, a.k.a. David the Good) has added more images to his online art gallery. While it will eventually be moving to a new site, you can check out the work-in-progress today at FoundMyself.com. Also, David wants us to plug his latest album, The Brainspider Affair, so here's the link to it on Amazon. I haven't listened to it. For all I know it sounds like someone pounding on a bag full of cats with a rug-beater. But hey, maybe that's your thing. There are samples on the Amazon site, which will tell you much more about his music than any amount of blather by me will.
M. David Blake was recently interviewed for the Clarion West Write-a-Thon, and the interview was supposed to be published today, but we haven't received a live link yet. Check back later.
CORRECTION!: M. David Blake was recently interviewed by the ever-enterprising AmyBeth Inverness, and you can read the interview now at her site. He is also participating in the Clarion West Write-a-thon again this year, but the link for his profile, at the time of this update, is not yet live on the site.
And of course I'm up to my armpits in STUPEFYING STORIES stuff, but most of that is behind the scenes at the moment.
Anyone else have a link to a project they're working on that they'd like to share? Let me know.
Ciao,
~brb
Henry Vogel has just posted chapter 9 of his novel-in-progress, Scout's Honor. Read it today at Cliffhanger TwoFifty.
David Goodman (a.k.a. Vidad, a.k.a. David the Good) has added more images to his online art gallery. While it will eventually be moving to a new site, you can check out the work-in-progress today at FoundMyself.com. Also, David wants us to plug his latest album, The Brainspider Affair, so here's the link to it on Amazon. I haven't listened to it. For all I know it sounds like someone pounding on a bag full of cats with a rug-beater. But hey, maybe that's your thing. There are samples on the Amazon site, which will tell you much more about his music than any amount of blather by me will.
CORRECTION!: M. David Blake was recently interviewed by the ever-enterprising AmyBeth Inverness, and you can read the interview now at her site. He is also participating in the Clarion West Write-a-thon again this year, but the link for his profile, at the time of this update, is not yet live on the site.
And of course I'm up to my armpits in STUPEFYING STORIES stuff, but most of that is behind the scenes at the moment.
Anyone else have a link to a project they're working on that they'd like to share? Let me know.
Ciao,
~brb
Thursday, June 14, 2012
World Enough and Time: The Nature of Criticism
True story.
LadyQuill and I joined a local writer's group. Their meetings consisted of reading stuff to each other, plus a writing exercise on occasion. At one of these get-togethers, one of the other members read this rambling reminiscence story about a woman he knew twenty years earlier.
"She brought him up on stage," he read, "and she embarrassed him."
Then he moved on to the rest of his story.
The writing was good; his skills were there, the sentences were well structured. But there's that whole "show, don't tell" guideline that he was completely ignoring--not just once, but at several points throughout the piece.
The real kicker came when LadyQuill tried to offer "show don't tell" as advice to him. After all, LadyQuill has two books and a plethora of magazine and online articles to her name; she should know a little bit about writing and selling what's written. But her honest advice was not welcome.
"This isn't a critiquing group," we were told. "We're just here to listen. That way, no one gets any hurt feelings."
Okay. No hurt feelings, I can see that. Maybe.
If I take off my glasses, shield my eyes, lean in close, and squint, maybe.
Writing is about taking the images, and thoughts, and concepts, out of your head, and plunking them down on paper for the entire world to peek at. Writing requires both the imagination to develop the ideas AND the skillset to present them properly. If you don't have the writing skills to get your ideas across, the whole thing falls apart, no matter how cool and interesting the original concept might have been. And if you don't have a thick enough skin to accept criticism and advice, then how in the heck do you expect to improve?
"I don't write for publication," he said. "I write for me. I don't care if it ever gets published."
Ah, okay. Critique not necessary if it's not for public consumption, I can see that, too. But if it's not for public consumption...then why the BLEEP! did you read it out loud...? Were we not "the public" in that particular scenario...?
LadyQuill and I didn't attend too many more meetings of that particular writer's group.
To me, criticism and critique should be treated as the advice and opinions they are. On occasion, there will be some really good advice in there (like "show it, don't talk about it"). Sometimes the advice will be absolutely horrendous (like, "you should change your barbarian hero to a woman and have her talk to her opponents about their feelings").
One of the reasons I originally started doing Friday Challenges was to get critiqued. I actually wanted to know what was wrong with my writing and how I could improve it. I'm sorry, but "cool" and "nice" are probably not words used in an honest critique.
You--any of you reading this--you are my "public." If I confuse you, or irritate you, or the absolute worst, BORE you...I want to know it. I need to know it, or I'm going to keep making the same stupid--and preventable--mistakes.
How about the rest of you? Do you have any views on criticism and "creative suggestions?" What's the worst (or best) critique you've ever received?
Wednesday, June 13, 2012
Ultimate Geek Fu
Today's topic was going to be a review of Prometheus, but on further reflection: meh. We can dispose of the entire thing by citing a simple truism: Prequels Always Suck.
I mean, really. The Phantom Menace. Caprica. Young Indiana Jones. X-Men: First Class. Butch and Sundance: The Early Days. Can anyone here think of a prequel -- not a franchise reboot, like Batman Begins, Casino Royale, or the most recent Star Trek movie, but a same-continuity prequel -- that did not totally bite? Because we were talking about it at some length last night, and we sure couldn't.
And if you want to go deeper: do you have a theory as to why prequels always suck?
Let the arguments begin...
Meanwhile, over in Philip K. Dick land, another load of aspiring contenders for the PKD Award showed up this week. Steampunk, zombie, steampunk, zombie -- ah, here's one about steampunk zombies, I guess it had to happen sooner or later --
I suppose I should count my blessings; at least the flow of paranormal romances has slowed. But looking at all these new releases leaves me with one burning question:
What the Hell happened to science fiction?
I mean, really. The Phantom Menace. Caprica. Young Indiana Jones. X-Men: First Class. Butch and Sundance: The Early Days. Can anyone here think of a prequel -- not a franchise reboot, like Batman Begins, Casino Royale, or the most recent Star Trek movie, but a same-continuity prequel -- that did not totally bite? Because we were talking about it at some length last night, and we sure couldn't.
And if you want to go deeper: do you have a theory as to why prequels always suck?
Let the arguments begin...
Meanwhile, over in Philip K. Dick land, another load of aspiring contenders for the PKD Award showed up this week. Steampunk, zombie, steampunk, zombie -- ah, here's one about steampunk zombies, I guess it had to happen sooner or later --
I suppose I should count my blessings; at least the flow of paranormal romances has slowed. But looking at all these new releases leaves me with one burning question:
What the Hell happened to science fiction?
Tuesday, June 12, 2012
The Slushpile Survival Guide
A Manuscript's Odyssey, Part 3
Part One | Part TwoWhen last we checked in with our hypothetical manuscript it was sitting in the DMV Waiting Room of the Damned, a.k.a., the STUPEFYING STORIES slush pile, waiting for its number to be called and for me to find the time to continue writing this series. The latter has finally happened, so let's assume the former has as well and usher the manuscript in for its big chance: its audition with the First Reader.
Writers seem to share a lot of misconceptions about First Readers. Writing group folklore to the contrary, First Readers are not embittered failed writers who use the power of their petty positions to crush the dreams and hobble the careers of competing writers. Nor are they constipated nit-picky martinets, eagerly seizing on any excuse to disqualify a submission. ("A-hah! He used a hyphen when he should have used an em-dash! REJECT!") Dogbert's Publishing Company to the contrary, we aren't actually in this business simply because we relish the sadistic joy of rejecting stories all day long.
Rather, First Readers are an essential part of any publishing operation, ours more so than most, and they're here for the same reason as the rest of us: because they're eager to be the first one to discover some new treasure, and bring it to the world.
Some days I think of our First Readers as being like grad students working on an archaeological dig, carefully sifting through the lithic debitage to find that one fragment or fossil that's going to rewrite the history books and change the world. Other days I envision them as being more like newcomers in a mining camp, knee-deep in a cold creek, panning for gold and hoping to discover the nugget that will make their careers.
Unfortunately, to find those nuggets of pure gold, you've got to pan a lot of gravel.
How much? Consider these numbers. When we're on-schedule (and we've been way off schedule lately, but that's another column), we publish about ten stories a month.
In December alone, we received about five hundred new story submissions.
Our submissions numbers are erratic: we're a very minor, penny-a-word, third-tier (at best) market, and the submissions ebb and flow in direct relationship to how well we stick to our publishing schedule. (And in relationship to the academic calendar, too. We always get a big gush of submissions at the end of every semester.) In December we received about 500 new submissions. In January, slightly over 300. In February slightly under 300, in March slightly over 200, in April and May slightly under 200 each, and as of June 11 we've received 77 new submissions month-to-date, so we're on-track to come in at or above 200 again.
In short, at this time, in our market, the odds against our hypothetical manuscript being accepted for publication are roughly 20-to-1.
So considering those raw numbers, what are the odds that your story will rise out of the common muck and gravel and be accepted for publication? Surprisingly good, if you just pay attention to a few small but very important details....
...to be continued...
Labels:Slushpile Survival Guide
Saturday, June 9, 2012
Open Mic Saturday
Good morning all, and welcome to Open Mic Saturday. This is the place
to share your news and perhaps do a little bragging. If you're writing a
novel: how much progress did you make this week? If you're writing
short stories: did you finish anything or submit anything this week? If
you've sold or published anything recently, when is it coming out and
where can we find it? In short, as a writer, what kind of progress did
you make this week?
Or what else is on your mind, that you feel like sharing with the group here?
Or what else is on your mind, that you feel like sharing with the group here?
Wednesday, June 6, 2012
No More Summer Running
RIP Ray Bradbury. Perhaps he's drinking dandelion wine with all his old colleagues.
Sigh.
I grew up on Ray Bradbury's short story collections. The Illustrated Man, The Martian Chronicles, The Golden Apples of the Sun, R is for Rocket, S is for Space, I Sing the Body Electric; yeah, sure, I read Heinlein, Clarke, Norton, and Asimov, but Bradbury's short stories were the ones that made me say, "Hey! I want to do that!" Somewhere in my archives there are piles of really bad Imitation Bradbury stories I wrote when I was a teenager, that haven't seen the light of day in the thirty-plus years since, and which I should probably burn now, purely as a public service.
Half a lifetime ago I was at a big con in -- Atlanta, I think -- waiting to go into a hall that was closed for the moment, and turned around to find that the man standing next to me was Mr. Bradbury. I was still frozen in awestruck fanboy mode when he leaned over, read my name tag, and then stuck out a handshake, said how pleased he was to meet me, and started talking about how much he'd liked a story that I had just had published. I wish I could remember which one. I'd only made it as far as, "Buh -- buh -- buh -- Bradbury!"
Yeah, he really was that kind of a good guy. The world is poorer for his passing, but he left a terrific body of work and some huge footprints to follow.
Good legacy, for a writer.
-Henry
Sigh.
I grew up on Ray Bradbury's short story collections. The Illustrated Man, The Martian Chronicles, The Golden Apples of the Sun, R is for Rocket, S is for Space, I Sing the Body Electric; yeah, sure, I read Heinlein, Clarke, Norton, and Asimov, but Bradbury's short stories were the ones that made me say, "Hey! I want to do that!" Somewhere in my archives there are piles of really bad Imitation Bradbury stories I wrote when I was a teenager, that haven't seen the light of day in the thirty-plus years since, and which I should probably burn now, purely as a public service.
Half a lifetime ago I was at a big con in -- Atlanta, I think -- waiting to go into a hall that was closed for the moment, and turned around to find that the man standing next to me was Mr. Bradbury. I was still frozen in awestruck fanboy mode when he leaned over, read my name tag, and then stuck out a handshake, said how pleased he was to meet me, and started talking about how much he'd liked a story that I had just had published. I wish I could remember which one. I'd only made it as far as, "Buh -- buh -- buh -- Bradbury!"
Yeah, he really was that kind of a good guy. The world is poorer for his passing, but he left a terrific body of work and some huge footprints to follow.
Good legacy, for a writer.
-Bruce
Later:
I keep thinking of the end of Truffaut's 1966 (?) film of Fahrenheit 451, in which all the people who have memorized books to keep them alive are walking around, reciting them. That seems like a fitting way to honor Bradbury: by reading one of his stories aloud tonight.
I wonder which one I'll chose? Going back to The Illustrated Man seems like the right thing to do, since that's where my lifelong affection for Bradbury's writing started, but there are so many good stories...
I wonder which one I'll chose? Going back to The Illustrated Man seems like the right thing to do, since that's where my lifelong affection for Bradbury's writing started, but there are so many good stories...
Ah, here we go: "The Exiles."
"Their eyes were like fire and the breath flamed out the witches' mouths as they bent to probe the cauldron with greasy stick and bony finger.
'When shall we three meet again
In thunder, lightning, or in rain?'
How about you? What's the Ray Bradbury story most on your mind tonight?
-Bruce
Tuesday, June 5, 2012
And we're back...
Sorry for the site outage this morning. I was trying to fix our chronic URL redirection problem and instead put the site into an infinite redirection loop. Getting out of it turned out to be both easier and trickier than expected. It was easily done, once I knew how to do it. (What, document the API? We don't need no steenkin' documentation!)
Everything should be back to normal now. Well, as normal as we get, anyway.
Everything should be back to normal now. Well, as normal as we get, anyway.
Saturday, June 2, 2012
Open Mic Saturday
Good morning all, and welcome to Open Mic Saturday. This is the place
to share your news and perhaps do a little bragging. If you're writing a
novel: how much progress did you make this week? If you're writing
short stories: did you finish anything or submit anything this week? If
you've sold or published anything recently, when is it coming out and
where can we find it? In short, as a writer, what kind of progress did
you make this week?
Or what else is on your mind, that you feel like sharing with the group here?
Or what else is on your mind, that you feel like sharing with the group here?
Wednesday, May 30, 2012
MEN IN BLACK 3: More Of The Same or Exactly The RIGHT Note?
The Daughter and I went to see MIB3 yesterday while it rained here.
Let me just say that while my daughter and I share a voracious reading habit, our reading MATERIAL is wildly different. We’ve been known to cross over into each other’s territory, but for the most part, I read and write science fiction and she reads and writes fantasy.
Even in terms of the MIB franchise – I love it for the aliens, she loves it for Will Smith...(;-))
I’m NOT going to iterate the plot here. If you really want to know the entire movie before you see it, go here: http://en.wikipedia.org/wiki/Men_in_Black_3 to get the complete lowdown.
The Daughter and I are here to review the movie and first of all I want to point out that if you’re shy of emotional issues, then this MIB is not for you. Where the others were a joyous romp all over the tropes of alien occupation, invasion and secret societies; MIB3 for the first time deals with feelings. The Daughter: And not just superficial feelings between Will Smith and an alien princess (ahem…Men in Black 2), but real, substantial feelings that resonate not just with blissful lovebirds but with the human experience at a deeper level.
Therein lies its strength.
Io9 recently posted on “trilogies”, the best and the worst – it’s worth a read! Read it here: http://io9.com/5912471/best-and-worst-movie-threequels-of-all-time. If I was writing the piece, I would now add the MIB franchise to the BEST, especially if you drop the second, painfully hideous flick (sorry Rick).
Where the first two movies were alien romps with gross beings and fantastic laser guns, and while the third one has these, there is a far deeper story here. Even more amazing, the character who is pushing for the deeper story is J, Will Smith’s character. Smart, sassy and obnoxious for the first two movies, it’s as if he grew up in the interval between MIB2 and MIB3. He is, in fact, older in this movie than in the others! Both The Daughter and I noticed that Will Smith has aged albeit gracefully The Daughter: Meanwhile Tommy Lee Jones is wizened and equipped with his usual endearing stoicism, he just sort of looks old. MIB1 was made in 1997 and MIB2 in 2002, so that means that Smith was a “kid” of 29 and is now 43. Those years, especially with children added in, can age a person, especially when he and his wife worked full time as actors as well as having a family life and everything that entails in these early years of the 21st Century.
That explains the new depth of character that Smith gives Agent J, and it seems to me that the main issue broached in the movie is one that Smith may have had to face when he was 13, and one he has likely pondered as a dad.
Another actor The Daughter and I discussed was Emma Thompson. Winner of 40 awards including Emmys, Oscars and Golden Globes whose acting credits run from Beatrice in Shakespeare’s MUCH ADO ABOUT NOTHING to the voice of the cat woman, Captain Amelia in the cartoon TREASURE PLANET. She has played such eccentric and varied characters as Nanny McPhee and Karen Eiffel. We could just see her agent handing her the script for MIB3 and her trying to fend it off, and crying in her distinctive British accent, “No, no, please! Not another American film! Especially about alien invasions! I refuse to be known as That British Sci-Fi Actor! Look what happened to Sigourney Weaver!”
We imagined the agent begging her and finally, exasperated, she would grab the script and begin to read. When she’s done, she would have sighed and clutched the pages to her chest, leaned back and said, “Now THIS is intelligent.”
Because above all things, MIB3 is smart, sassy and has fascinating characters – finally.
Don’t get me wrong, the gross aliens are still there: Humans in fanciful costumes, Bowling Ball Head, a gigantic fish who tries to eat J (and who just has to be related to the subway alien, Jeff), as well as the ubiquitous Worms (who are always abandoning Earth at the moment of truth) and the unsurprising revelation that Lady Gaga is an alien living on Earth. The Daughter: I KNEW IT! Also, one must note the distinctively retro angle they took on the aliens at the 1969 MIB headquarters. Garish colors; flaky pointed heads; and bulky costumes make them look oh so corny. Yet the viewer takes pleasure in this knowing that it was deliberately done and stands in contrast to the sharp sleekness of the contemporary MIB headquarters.
But two new aliens gave us pause by their depth. Griffin, a five dimensional being who can appear any way he wants to in our three dimensions and who views time however he wants to as either spectator or participant is both winning and thought-provoking. Brilliantly played by actor Michael Stuhlbarg, we fell in love with him and his earnest, vaguely creepy comments. The way he viewed time as endlessly branching possibilities that eventually collapse into the “present” we are familiar with, made me remember the importance of seemingly small events and the possibility that they can be significant. He iterates this well when he says something like, “No one is that important to the time line.” Agent J replies that something Griffin assumes is there – isn’t, Griffin amends, “Oh, he’s one of the ones who IS that important.”
But Boris The Animal (“My name is BORIS IT’S JUST BORIS!”) is especially...alien. In a movie full of Humans in costumes, this alien is truly creepy as only an “almost-but-not-exactly-Human-with-unsettling-differences” can be. The Daughter: the worst moment is when his weird “film canister” eyes fall out during his final scene, in order to pull back into his disgusting carcass-esque body. His biology is both bizarre and almost understandable and while his attitude is unrelentingly foul (making him a bit one-dimensional) he is the perfect villain for the MIB. There are even echoes of J’s issue in a scene between Borises – but I’ll leave it to you to figure that out. The movie is rich with allusions and metaphors and perhaps even a parable or two.
While I wouldn’t go so far as to say that MIB3 is the greatest science fiction movie of all time, I would be willing to say that it is one of the Ten Best SF Movies of All Time – and for this critic of SF movies, that’s going WAY out on a limb.
See it. I’m pretty sure you won’t regret it. The Daughter: This is a gross, exciting sci-fi movie that’s for women, too…and not in the same way that say, TRANSFORMERS stuck in a romance in order to please the girlfriends that were dragged along to that movie. It’s just not a silly hack-and-slash/blinking lights film. It’s like…quality.
So then: let the arguments begin!
Labels:Ultimate Geek Fu
Monday, May 28, 2012
The Old Goat Prepares to Move On
This won't be my last column here at the Friday Challenge, but it will be one of the last. I still have a goodbye column to write; but this isn't that column. This column is a bit of an introduction to my new writing project, the one I mentioned in the comments section of this weekend's Open Mic Saturday. I'm talking about the Cliffhanger TwoFifty.
Let me lead into what the Cliffhanger TwoFifty is by telling you about its ancestor. Way back in 1990, I landed my first IT job. It was most definitely an entry level position; making software tapes for customers and handling data conversion when a customer chose to upgrade to the latest, greatest version of the company's software. At the time, PCs weren't powerful enough to handle very much in the way of business software. A lot of business software was written for and run on mini-computers, including ones from companies which used to be big names and the industry but exist only in our memories, today.
I did all of my work on mini-computers, using a standard terminal for the time. The terminal could display 24 lines of text with 80 characters per line. One slow afternoon, on a whim, I decided to start writing a story to display on my terminal when I logged off of the computer. Thus began the Adventures of Penny Pretty (extra credit to the first person who identifies where I stole the name from), which I planned as a sort of modern-day Perils of Pauline (look it up if you're so young that doesn't mean anything to you). The first chapter briefly introduced Penny, introduced danger, then ended with a cliffhanger. I didn't tell anyone about the story, just logged off one afternoon and left it for my co-workers to discover. The next day, the very first question asked of me was, "When are you going to write the next chapter?" That wasn't always an easy question to answer.
The restrictions the terminal placed on me were brutal. Like I said earlier, 24 lines, 80 characters per line. That's not a lot of space in which to resolve a cliffhanger, advance the story, then introduce a new cliffhanger; but they were rules I couldn't break. Anything beyond 24 lines meant part of the scrolled off the top of the screen, never to be seen by potential readers. I had to work and edit and trim virtually every chapter to get it to fit on a single screen. But Penny was popular with my co-workers. Printed copies of all of the chapters made the rounds among employees (and even some of the more open-minded managers) and more than once I was asked to logoff the computer so someone could read the latest chapter. I ended up writing around 20 chapters in four months. Then I was transferred to a new position in the company and had neither the time nor the terminal required to continue Penny's adventures.
I hadn't thought about the Adventures of Penny Pretty in years, but the story resurfaced a few weeks ago as I was thinking, yet again, about trying to write a novel. I've never written a novel. I've never even come close to writing a novel. Somehow, I just can't quite get past the size of the task. I can't see the finish line from the starting line. I've tried tricking myself by setting a goal of writing a full chapter, but I'm apparently too smart to be fooled by that trick. While I was trying to figure out a new trick, Penny's adventures suddenly popped up and started waving madly, trying to get my attention.
Many of the "rules" for the Cliffhanger TwoFifty have been taken directly from the Adventures of Penny Pretty. In each chapter, I'll be forced to resolve a cliffhanger, advance the story, then end on a cliffhanger. The big difference is that I'm not restricted to 24 lines, each 80 characters in length. I was free to choose any length I wanted for my chapters, including having no set length at all. But I want the restrictions because they increase the challenge of writing each chapter. Also, having to fit each chapter into a certain number of words gives a simple goal for each chapter. I know there are lots and lots of chapters to come, but what's most important is fitting the chapter I'm writing into the framework for the Cliffhanger TwoFifty. It's a trick, but it appears it's one I'm not too smart to fall for.
The last part of the puzzle was setting my chapter length. You've probably already figured out that chapters are going to be about 250 words in length. It's not a hard and fast rule; I can go over 250 words but will do my best to keep to within 10 to 20 words of that number. Why 250 words? Well, a while back, Bruce wrote a column about how publishers count words (or at least how they counted words in the days of typewritten manuscripts). As a rule of thumb, a single typed page (double-spaced, of course) was counted as 250 words. I decided to go with that, essentially choosing to write a novel one type-written page at a time, publishing each page online for all to read.
The first chapter of the Cliffhanger TwoFifty is already up. It was published two hours before this column was. Go on over and give it a read. It's short and won't take very long. Leave a comment, if you like. Like all writers, I love to read comments about my work. Tell your friends. Link your sites to it. I plan on having fun with it and hope you will, too.
Let me lead into what the Cliffhanger TwoFifty is by telling you about its ancestor. Way back in 1990, I landed my first IT job. It was most definitely an entry level position; making software tapes for customers and handling data conversion when a customer chose to upgrade to the latest, greatest version of the company's software. At the time, PCs weren't powerful enough to handle very much in the way of business software. A lot of business software was written for and run on mini-computers, including ones from companies which used to be big names and the industry but exist only in our memories, today.
I did all of my work on mini-computers, using a standard terminal for the time. The terminal could display 24 lines of text with 80 characters per line. One slow afternoon, on a whim, I decided to start writing a story to display on my terminal when I logged off of the computer. Thus began the Adventures of Penny Pretty (extra credit to the first person who identifies where I stole the name from), which I planned as a sort of modern-day Perils of Pauline (look it up if you're so young that doesn't mean anything to you). The first chapter briefly introduced Penny, introduced danger, then ended with a cliffhanger. I didn't tell anyone about the story, just logged off one afternoon and left it for my co-workers to discover. The next day, the very first question asked of me was, "When are you going to write the next chapter?" That wasn't always an easy question to answer.
The restrictions the terminal placed on me were brutal. Like I said earlier, 24 lines, 80 characters per line. That's not a lot of space in which to resolve a cliffhanger, advance the story, then introduce a new cliffhanger; but they were rules I couldn't break. Anything beyond 24 lines meant part of the scrolled off the top of the screen, never to be seen by potential readers. I had to work and edit and trim virtually every chapter to get it to fit on a single screen. But Penny was popular with my co-workers. Printed copies of all of the chapters made the rounds among employees (and even some of the more open-minded managers) and more than once I was asked to logoff the computer so someone could read the latest chapter. I ended up writing around 20 chapters in four months. Then I was transferred to a new position in the company and had neither the time nor the terminal required to continue Penny's adventures.
I hadn't thought about the Adventures of Penny Pretty in years, but the story resurfaced a few weeks ago as I was thinking, yet again, about trying to write a novel. I've never written a novel. I've never even come close to writing a novel. Somehow, I just can't quite get past the size of the task. I can't see the finish line from the starting line. I've tried tricking myself by setting a goal of writing a full chapter, but I'm apparently too smart to be fooled by that trick. While I was trying to figure out a new trick, Penny's adventures suddenly popped up and started waving madly, trying to get my attention.
Many of the "rules" for the Cliffhanger TwoFifty have been taken directly from the Adventures of Penny Pretty. In each chapter, I'll be forced to resolve a cliffhanger, advance the story, then end on a cliffhanger. The big difference is that I'm not restricted to 24 lines, each 80 characters in length. I was free to choose any length I wanted for my chapters, including having no set length at all. But I want the restrictions because they increase the challenge of writing each chapter. Also, having to fit each chapter into a certain number of words gives a simple goal for each chapter. I know there are lots and lots of chapters to come, but what's most important is fitting the chapter I'm writing into the framework for the Cliffhanger TwoFifty. It's a trick, but it appears it's one I'm not too smart to fall for.
The last part of the puzzle was setting my chapter length. You've probably already figured out that chapters are going to be about 250 words in length. It's not a hard and fast rule; I can go over 250 words but will do my best to keep to within 10 to 20 words of that number. Why 250 words? Well, a while back, Bruce wrote a column about how publishers count words (or at least how they counted words in the days of typewritten manuscripts). As a rule of thumb, a single typed page (double-spaced, of course) was counted as 250 words. I decided to go with that, essentially choosing to write a novel one type-written page at a time, publishing each page online for all to read.
The first chapter of the Cliffhanger TwoFifty is already up. It was published two hours before this column was. Go on over and give it a read. It's short and won't take very long. Leave a comment, if you like. Like all writers, I love to read comments about my work. Tell your friends. Link your sites to it. I plan on having fun with it and hope you will, too.
Saturday, May 26, 2012
Open Mic Saturday
Good morning all, and welcome to Open Mic Saturday. This is the place
to share your news and perhaps do a little bragging. If you're writing a
novel: how much progress did you make this week? If you're writing
short stories: did you finish anything or submit anything this week? If
you've sold or published anything recently, when is it coming out and
where can we find it? In short, as a writer, what kind of progress did
you make this week?
Or what else is on your mind, that you feel like sharing with the group here?
Or what else is on your mind, that you feel like sharing with the group here?
Friday, May 25, 2012
The Final Friday Challenge
There, I bet that got your attention. But first:
Re: The 5/18/12 Friday Challenge, "First, Begin at the Beginning..."
Yes, as rycamor couldn't resist posting, the six beginnings you were to evaluate in this challenge came from six famous published works. Cutting to the chase, then, the selections were:
When I first launched the Friday Challenge in March of 2005, it was with one idea in mind. After what was then 25 years of being a successful, published, professional writer and two-term member of the SFWA Board of Directors, I was getting a constant stream of email from a tremendous number of people who couldn't seem to find the answer to one very simple question:
How do I become a writer?
Because they couldn't find this answer, these people collectively were wasting a lot of time, money, and energy on self-help books, seminars and workshops, and college-level creative writing programs, all in a desperate search for that tightly held secret -- that magical incantation -- that je ne sais quois that would enable them to make the leap from saying, "I want to write," to being able to say with a straight face, "I am a writer."
In my more cynical moments, of which I have no shortage, I came up with a number of alternative ideas. Perhaps to become a Real Writer you must have a sheet of Magic Paper™ -- parchment made millennia ago in ancient Biblyos from the hide of the Golden Fleece, but still possible to find today if you have enough money and know the right --
Nah. On second thought mail fraud prosecutors are a notoriously humorless bunch, and I doubt if any of them have ever seen Dumbo. Okay, next idea. How about if it requires calling together a Dark Triumvirate consisting of one Hugo Winner, one Nebula Winner, and one Philip K. Dick Winner, and kneeling in the center of the Triangle of Power while they lay hands upon you and, invoking the names of past SFWA Grand Masters, repeat the ancient incantations that --
Nah. While this would gag would be fun to do once at a con, I've met too many young women (and a few men) who truly believe that becoming a successful writer does involve kneeling before a SFWA Grand Master, or at least a couple of book publishers and a magazine editor or two, and I know far too many industry pros who would be unable to resist the temptation.
After a few more ideas, none of which were any better than the foregoing two, I came up with The Friday Challenge. At heart, everything we have done here together for the past seven years has been based on this one very simple idea. To wit:
To become a writer, you must:
After decades of participating in writers' workshops and critique groups, though, I've found that the two places where most would-be writers fall down are in steps 3 and 4: listening and learning. This is because, let's admit it: it's damned hard to sit quietly and listen to someone else's criticism of something you've written.
Our stories are our children. In some cases we've carried them around inside our heads for years. When they do finally come out into the daylight, we want to believe that each and every one of them is an Athena, emerging fully grown, armed and armored, ready to peal to the sky a clarion call that will make Ouranos and Gaia tremble. No one ever likes to hear, "Hey, Athena. Your sandal's untied."
So right from the start, The Friday Challenge was designed to make it easier to learn how to listen and learn. The design points were:
You can't please everyone all the time.
No one critic is right all the time.
Writing for professional publication is not like writing for your mom to post on the refrigerator door. As a writer, you must develop a thick skin, or at least the ability to fake having one. If you do make it to being professionally published some day, your work will sometimes be criticized unfairly -- sometimes praised unreasonably, which is always more embarrassing -- sometimes damned by people whose opinions you respect and sometimes loved by people you thought you despised.
The hardest thing for a writer to learn is how to take criticism: how to figure out what's valid and what's not; who you should listen to and who you should ignore; how to avoid going into a tailspin over a bad review or becoming irrationally exuberant because of a good one; and when you should shrug off your best friend who loves you but is totally missing the point, and listen to and learn from your worst enemy who also happens to be absolutely right.
This is how you learn to become a writer. This is what defines us as writers. We learn to dig deeply into our hearts, guts, and souls, and pull out some words that seem important. We put those words out there for other people to read, and with luck, get paid for our work once in a while. We suffer the slings and arrows of outrageous critics and ignorant Philistines, and console ourselves by saying they only seethe with bitterness because they wish they could do what we do half as well as we do it. We accept the praise of our fans magnanimously, and then tomorrow, we get up and do it all over again.
And once in a rare while, when the time is just right, and the stars align perfectly, and Serendipity smiles down upon us, we can capture lightning in a bottle, and string together some words that take on a life of their own. Then we write a story that makes Ouranos and Gaia tremble, and puts a noticeable dent in the Zeitgest --
And when that happens: that, my friends, is a feeling like no other.
Seven years ago, this is what I -- we -- set out to accomplish with The Friday Challenge: to help people find the bridge that goes from "I want to write" to "I am a writer." Looking back on it now, I can't help but feel a certain sense of pride. We've done some very cool things, these past seven years. A lot of terrific talent has come through this site, and I have made some wonderful new friends, both online and in the real world. I would be remiss if I did not give special thanks now to Henry Vogel, who has been my unfailing Dotar Sojat and the constant Voice of Reason; M. David Blake (a.k.a., "M"), who stepped in heroically and kept the site running while I was preoccupied by some pretty horrendous family issues; David Yener Goodman (a.k.a., "Vidad"), who designed the site banner and has been our consistent behind-the-scenes source of creative madness; and Kersley Fitzgerald, our ever-thoughtful den mother, who has kept us boys from getting too far out of line.
But this list of credits and acknowledgments is much too short. Thanks also to Arisia, who has been a stalwart from the beginning; Guy Stewart, an old friend made new again by his involvement here; Allan Davis Jr., no relation to Sammy; Waterboy, "they also serve who stand and wait;" the legendary Snowdog, whose name will live on in infamy, but a little later; Leatherwing, XDPaul, KTown, rycamor, Ben-El... The list goes on and on, and would go on much longer, except that HaloScan got acquired by JS-Kit, which in turn became Echo, which was replaced by DISQUS, and thus seven years of accumulated comments have gone down the drain.
Thanks, everybody, including those who only read and lurk.
But...
"The time has come," the Walrus said, "to speak of other things."
It's been fun, these past seven years, but whatever we set out to accomplish when we launched The Friday Challenge, it's long since been accomplished. I've gotten to know some great people. I've had the chance to watch some talented amateurs become published pros. The Friday Challenge, proper, has become -- well, a challenge to keep going, and most of what it used to do has now moved over to STUPEFYING STORIES. My time is finite, and as STUPEFYING STORIES continues to grow and demand more of my time, something's got to give. Ergo, after a considerable amount of thought and backstage discussion:
This is the final Friday Challenge.
This site will continue to exist. We, the site authors, have at least a few more columns in us, and the Slushpile Survival Guide practically writes itself. Next Wednesday's Ultimate Geek Fu will, of course, review Men in Black 3, assuming one of us can rouse him- or herself out of our deep apathy long enough to go see the thing. But the writing challenges proper end as of today, which does make the site name and URL somewhat problematic. We'll have to reconsider that.
All that lies in the future, though. Right now, I want to lay my virtual hands upon you and offer up this closing benediction.
Re: The 5/18/12 Friday Challenge, "First, Begin at the Beginning..."
Yes, as rycamor couldn't resist posting, the six beginnings you were to evaluate in this challenge came from six famous published works. Cutting to the chase, then, the selections were:
- Dorsai!, by Gordon Dickson. First published as a serial in Astounding in 1959, this book and its sequels became the backbone of Dickson's writing career. Dorsai! did not win the Hugo Award for best novel in 1960, but only because it was competing against Heinlein's Starship Troopers, which did win that year.
- Beau Geste, by P. C. Wren. The first in a series of six novels, the source for at least four major film adaptations and inspiration for countless others, this is the definitive novel of life in the French Foreign Legion, and even the 1999 version of The Mummy pays homage to it. Whatever you think you know about the French Foreign Legion, it comes from this book.
- The Man in the High Castle, by Philip K. Dick. Winner of the Hugo Award for Best Novel, 1963. Have I mentioned that I'm not only a past winner of the Philip K. Dick Award for Best American Novel, I'm also one of the judges on this year's Philip K. Dick Award jury?
- Stand on Zanzibar, by John Brunner. This dystopian New Wave novel won the Hugo Award in 1968, the BSFA Award in 1969, the Prix Tour-Apollo Award in 1973...
- "By His Bootstraps," by Robert A. Heinlein. This classic 1941 novella is quite possibly the definitive time-travel paradox story -- it's either this one or Heinlein's "All You Zombies" -- but it's not often reprinted, because of its unusual length. Still, as I can attest: once you've read this one, you'll never forget it, and you'll never look at other time-travel stories in the same way.
- Star Wars, by some guy named George Lucas. Never heard of it. Anybody else here ever heard of this one?
The Final Friday Challenge
Good grief, is it really the Summer of 2012 already?When I first launched the Friday Challenge in March of 2005, it was with one idea in mind. After what was then 25 years of being a successful, published, professional writer and two-term member of the SFWA Board of Directors, I was getting a constant stream of email from a tremendous number of people who couldn't seem to find the answer to one very simple question:
How do I become a writer?
Because they couldn't find this answer, these people collectively were wasting a lot of time, money, and energy on self-help books, seminars and workshops, and college-level creative writing programs, all in a desperate search for that tightly held secret -- that magical incantation -- that je ne sais quois that would enable them to make the leap from saying, "I want to write," to being able to say with a straight face, "I am a writer."
In my more cynical moments, of which I have no shortage, I came up with a number of alternative ideas. Perhaps to become a Real Writer you must have a sheet of Magic Paper™ -- parchment made millennia ago in ancient Biblyos from the hide of the Golden Fleece, but still possible to find today if you have enough money and know the right --
Nah. On second thought mail fraud prosecutors are a notoriously humorless bunch, and I doubt if any of them have ever seen Dumbo. Okay, next idea. How about if it requires calling together a Dark Triumvirate consisting of one Hugo Winner, one Nebula Winner, and one Philip K. Dick Winner, and kneeling in the center of the Triangle of Power while they lay hands upon you and, invoking the names of past SFWA Grand Masters, repeat the ancient incantations that --
Nah. While this would gag would be fun to do once at a con, I've met too many young women (and a few men) who truly believe that becoming a successful writer does involve kneeling before a SFWA Grand Master, or at least a couple of book publishers and a magazine editor or two, and I know far too many industry pros who would be unable to resist the temptation.
After a few more ideas, none of which were any better than the foregoing two, I came up with The Friday Challenge. At heart, everything we have done here together for the past seven years has been based on this one very simple idea. To wit:
To become a writer, you must:
- Write something.
- Put it out where other people can read it.
- Listen to what those other people have to say about that which you have written.
- Learn from the feedback you receive.
- Apply what you've learned, write something else, and return to step 2.
After decades of participating in writers' workshops and critique groups, though, I've found that the two places where most would-be writers fall down are in steps 3 and 4: listening and learning. This is because, let's admit it: it's damned hard to sit quietly and listen to someone else's criticism of something you've written.
Our stories are our children. In some cases we've carried them around inside our heads for years. When they do finally come out into the daylight, we want to believe that each and every one of them is an Athena, emerging fully grown, armed and armored, ready to peal to the sky a clarion call that will make Ouranos and Gaia tremble. No one ever likes to hear, "Hey, Athena. Your sandal's untied."
So right from the start, The Friday Challenge was designed to make it easier to learn how to listen and learn. The design points were:
- We would present it in the form of a challenge because that way, it's not your brain-child being tortured, it's mine, and if the results turn out badly -- well, it was my stupid idea in the first place. Blame me and move on.
- We would present a new challenge weekly because that furnishes an incentive to move on quickly, and to learn from, apply, and let go of the critiques you receive.
- We would encourage -- in fact, beg for -- everyone including passive lurkers and readers to participate in the criticism sessions, in order to teach the two simple lessons that seem hardest for aspiring writers to learn:
Writing for professional publication is not like writing for your mom to post on the refrigerator door. As a writer, you must develop a thick skin, or at least the ability to fake having one. If you do make it to being professionally published some day, your work will sometimes be criticized unfairly -- sometimes praised unreasonably, which is always more embarrassing -- sometimes damned by people whose opinions you respect and sometimes loved by people you thought you despised.
The hardest thing for a writer to learn is how to take criticism: how to figure out what's valid and what's not; who you should listen to and who you should ignore; how to avoid going into a tailspin over a bad review or becoming irrationally exuberant because of a good one; and when you should shrug off your best friend who loves you but is totally missing the point, and listen to and learn from your worst enemy who also happens to be absolutely right.
This is how you learn to become a writer. This is what defines us as writers. We learn to dig deeply into our hearts, guts, and souls, and pull out some words that seem important. We put those words out there for other people to read, and with luck, get paid for our work once in a while. We suffer the slings and arrows of outrageous critics and ignorant Philistines, and console ourselves by saying they only seethe with bitterness because they wish they could do what we do half as well as we do it. We accept the praise of our fans magnanimously, and then tomorrow, we get up and do it all over again.
And once in a rare while, when the time is just right, and the stars align perfectly, and Serendipity smiles down upon us, we can capture lightning in a bottle, and string together some words that take on a life of their own. Then we write a story that makes Ouranos and Gaia tremble, and puts a noticeable dent in the Zeitgest --
And when that happens: that, my friends, is a feeling like no other.
#
Seven years ago, this is what I -- we -- set out to accomplish with The Friday Challenge: to help people find the bridge that goes from "I want to write" to "I am a writer." Looking back on it now, I can't help but feel a certain sense of pride. We've done some very cool things, these past seven years. A lot of terrific talent has come through this site, and I have made some wonderful new friends, both online and in the real world. I would be remiss if I did not give special thanks now to Henry Vogel, who has been my unfailing Dotar Sojat and the constant Voice of Reason; M. David Blake (a.k.a., "M"), who stepped in heroically and kept the site running while I was preoccupied by some pretty horrendous family issues; David Yener Goodman (a.k.a., "Vidad"), who designed the site banner and has been our consistent behind-the-scenes source of creative madness; and Kersley Fitzgerald, our ever-thoughtful den mother, who has kept us boys from getting too far out of line.
But this list of credits and acknowledgments is much too short. Thanks also to Arisia, who has been a stalwart from the beginning; Guy Stewart, an old friend made new again by his involvement here; Allan Davis Jr., no relation to Sammy; Waterboy, "they also serve who stand and wait;" the legendary Snowdog, whose name will live on in infamy, but a little later; Leatherwing, XDPaul, KTown, rycamor, Ben-El... The list goes on and on, and would go on much longer, except that HaloScan got acquired by JS-Kit, which in turn became Echo, which was replaced by DISQUS, and thus seven years of accumulated comments have gone down the drain.
Thanks, everybody, including those who only read and lurk.
But...
"The time has come," the Walrus said, "to speak of other things."
It's been fun, these past seven years, but whatever we set out to accomplish when we launched The Friday Challenge, it's long since been accomplished. I've gotten to know some great people. I've had the chance to watch some talented amateurs become published pros. The Friday Challenge, proper, has become -- well, a challenge to keep going, and most of what it used to do has now moved over to STUPEFYING STORIES. My time is finite, and as STUPEFYING STORIES continues to grow and demand more of my time, something's got to give. Ergo, after a considerable amount of thought and backstage discussion:
This is the final Friday Challenge.
This site will continue to exist. We, the site authors, have at least a few more columns in us, and the Slushpile Survival Guide practically writes itself. Next Wednesday's Ultimate Geek Fu will, of course, review Men in Black 3, assuming one of us can rouse him- or herself out of our deep apathy long enough to go see the thing. But the writing challenges proper end as of today, which does make the site name and URL somewhat problematic. We'll have to reconsider that.
All that lies in the future, though. Right now, I want to lay my virtual hands upon you and offer up this closing benediction.
Don't be content to work the traditional tropes. Don't follow precisely in the footsteps of those who have gone before. Don't set your sights on being merely "good enough" to get published, and don't let "what they're buying now" be your sole guide.
Write a story that makes Ouranos and Gaia tremble! Write a book that makes a difference! Write something that thirty years from now will have schoolchildren and reporters looking you up, to ask, "Mister (or Ms) [your name here], what was it like, to be the author who wrote [your title here]?"
NOW GO THOU AND WRITE!
Thursday, May 24, 2012
Critical Thinking
Clone Wars
Your mission, should you choose to accept it, is to help me with an article for work. I think I know where I stand, but I'd like to know what you think, too.
Human cloning: ethical or no?
Giving specific consideration to:
- Methods of development
- Existence of a clone
- Motivations for cloning
And my goal is to be realistic; no Michael Keaton in Multiplicity!
******
Update:
Vidad, where are you? I'd like your take on it.
Your mission, should you choose to accept it, is to help me with an article for work. I think I know where I stand, but I'd like to know what you think, too.
Human cloning: ethical or no?
Giving specific consideration to:
- Methods of development
- Existence of a clone
- Motivations for cloning
And my goal is to be realistic; no Michael Keaton in Multiplicity!
******
Update:
Vidad, where are you? I'd like your take on it.
Subscribe to:
Posts (Atom)




