but the demons thing i only figured out just now
I'm nearing the end of today's writing tasks, and it's not even 8:30 PM. What the crud am I gonna do with myself for the rest of the night? Answer: Probably replay PixelJunk Eden until either my eyes fall out or my thumbs fall off, whichever comes first. Then go to bed early. LUXURY.
During today's short story revision session, I finally moved out of the babble stage and into the drafting process. This shift got me thinking about how I revise stuff. Like I said before, some stories are more fun to revise than others (which isn't the same as being easier or taking less time) and some revision strategies seem more appropriate to some stories than others. But I'm starting to realize that every story I revise requires all my revision strategies, though not all in the same proportion. Which is to say, each time I produce a new version of any given story, the process moves through (loosely speaking) three phases, remaining in each phase for whatever period of time is required and revisiting those phases as necessary.
And I'm gonna blog about those phases, because 1. someone reading this might find such a blog post useful or at least interesting, and 2. blogging about this sort of stuff forces me to think about it closely and concretely terms, and that usually helps to refine and improve my process.
So. Here are the three (loosely speaking) phases of revision I wind up spending time in:
Identifying problems. I wouldn't be revising the story in the first place if it didn't have problems. So the first step of any revision is to identify those problems. This may involve my printing out the existing draft and scribbling on it a bunch, then translating those scribbles into a neat and orderly list. Sometimes the list isn't so neat and orderly. Usually neatness and order break down several items as I discover that the problems are fractal--every problem contains a multitude of sub-problems, each of which contain sub-sub-problems, and so forth down through the layers of the onion whose core is made up of DESPAIR.
I'm finding the DESPAIR quotient non-negotiable. There is always at least one hot second, usually more, during which I just know the story is worthless, nothing will make it better, there is no justifying the time and effort I've spent on it thus far, and shame on me for even thinking I might submit it in any form to professional paying markets. Lately I've been dealing with DESPAIR by simply writing that down on my list: "Problem #92: Story is garbage and should be buried in the compost under the used tea bags and moldy zucchini peelings." And then I just keep going.
It's sort of like rock climbing that way. Several years' practice at the climbing gym didn't "cure" my gut-level fear of heights; instead, it taught me how to keep climbing through an attack of acrophobia rather than freezing up and hanging there trembling until I came off the wall. It's also sort of like the meditation ideal of acknowledging the negative thought in a neutral way. Yep, that's a thought I'm having. Next?
Finding Solutions. This is where I spent the first week I had the current story on the metaphorical workbench. It was fun! Basically, for each listed problem, I opened up a new document and babbled to myself about it, restating the problem, brainstorming possible solutions, and pouncing on new ideas as they arose.This process spawned new documents and more enthusiastic babbling as other facets of worldbuilding or character creation or backstory came to light.
And just as the problem-identification phase has its demon DESPAIR, the problem-solving phase has its own demon: DEPRECATION. "Yeah, you're having fun babbling, sure, but are all these hundreds of words actually getting you closer to a new draft? No. They are not. Basically you are wasting your time. You are pretending to get work done when you actually aren't working at all. That's why you're having fun. If you were actually doing anything worthwhile, it would not be fun." That's what the demon says. I'm working on responding to the demon with "Yep, you're totally right" in my most neutral and boring interior voice while I continue babbling away uninterrupted.
That demon actually means well, but it's laboring under a big misconception. It thinks that finding a solution and implementing it should happen simultaneously. And, well, maybe another writer can go right from "here is the problem" to perfectly polished final draft words all in one go; I, at this time, cannot. I need to give myself room to just talk out a problem with myself in a process- rather than results-oriented way. Once I realized this, life at the metaphorical workbench got a lot more liveable.
Implementing the solutions. This is the phase where I start drafting the new version of the story. I decide to begin doing that today not because I thought I'd successfully addressed every single problem I'd identified thus far, but rather because I'd addressed those problems relevant to the first couple pages of the story. Also I suspected that I'd gotten to the point where the solutions I'd come up with so far would obviate some of the problems still waiting to be addressed. And so they have.
The demon hiding in this phase is PERFECTIONISM, and I have to ignore it. I'm still not trying for perfectly polished prose at this stage. I'm just writing a new draft that implements the solutions to the previous draft's problems. If the protagonist has new and better reasons for their actions, if I've chosen to include a more appropriate memory from their backstory than the one I had before, if the facts of the case are now altered to close the previous draft's plot holes, if each paragraph of the new draft serves a valid story purpose, then the draft is a success.
After all the problems are solved and a new draft is in front of me, then I can worry about polishing the prose to a fine shine. But that's line edits, which I don't really consider part of the revision/rewriting process. Until the revision is complete and every line on the page can justify its existence in the story, there's no point editing those lines for style, spelling, grammar, and flow. They might still get replaced, after all.
I expect I won't make it out of revision and into line edits without having to revisit every phase a couple times. I'll hit a place in the draft where I can't continue without brainstorming some more. I'll probably identify more problems whose solutions will require rewriting bits of story I already rewrote. The three phases are very fluid and lead into each other in unpredictable ways. But if I can tell myself which of the three phases I'm currently working in at any given moment, that helps keep me from trying to do all of it at once, and that in turn keeps things possible.
All the above requires the usual caveat, which is: Different writers do things differently. The above strategies are mine (all mine!). They may not be yours nor that of another favorite author. All strategies are valid to the extent that some writer somewhere finds them effective. And which strategies a writer finds effective will change over time--one's best process is an evolving rather than static thing.
Main thing is, it's not wrong if it works.
from the end of a pretty darn good week you get a pretty darn good view
- 1,164 words (if poetry, lines) long
- 1,009 words (if poetry, lines) long
As promised, the Friday Fictionettes for Week 1 of both August and September are up. They didn't go up on Friday, but given the overdue I'm overcoming, Saturday in the early afternoon is practically on time. So here they are:
- August 2, 2019: "Eyes in the Rain" (etext, audio) - "I first saw those eyes in the cafeteria, looking at me through the rain. It was raining everywhere in those days. Nothing could keep it out. The rain passed through roofs the way that elementary particles pass through the largely empty space of a living body. It passed through our clothes and glazed our living bodies like a second skin. It joined us for lunch, it slept in our beds, and it threatened to wash everyone’s sanity away."
- September 6, 2019: "The Best Revenge" (etext, audio) - "I’d never personally witnessed a deathbed curse, let alone been the subject of one. They tend to be something that happens to a friend of a cousin’s daughter’s classmate’s uncle’s co-worker. You never hear about it from the people who get cursed. I found out why. You mention that you’ve been cursed, people start to look at you funny. They start wondering if maybe you deserved it."
It's been a good week, writing-wise. There were no dud days. Even the day I spent biking most of the way across south Longmont, all the way from County Line to Hover and back again, while the Chevy Volt was getting serviced at the dealership from 8:30 AM until 6:00 in the afternoon, I still got all the things done: Submission procedures and short story revision at the Java Stop (highly recommended; a more comfortable space I haven't been in since that late night computer and video game cafe that used to be on The Hill closed), freewriting over a chicken sandwich at 300 Suns (they have a full kitchen now and a new menu, y'all!), and fictionette work and blogging back home late in the evening.
It's amazing--not surprising, exactly but still amazing--the difference a week like this makes in my overall outlook. Weeks where I barely eke out two good days between days of I can't even leave me feeling scared and despondent about everything that still needs to get done. I look back at how little I accomplished in the previous seven days, and I despair of what remains on my plate. But a week like this one, a week in which every day I hit every assigned task--except blogging, and that's kind of sort of optional anyway--I look back on this week and get a generous impression of how much I can get done in a week. Which makes the stuff currently on my plate look like an ordinary meal.
(Pardon the food metaphors. John and I just had an amazing dinner. I put together some caprese, he baked butter fan rolls to serve with spaghetti, and we made apple fritters as a dessert experiment. Talk about a lot on our plates. There are most certainly leftovers. John's probably gonna put up a photo on twitter, but he hasn't yet.)
Anyway, I'm optimistic about my short story revisions and oddly excited about getting the Friday Fictionettes Project all caught up by the end of the month. Like, 1. it's going to happen, and 2. it'll be awesome. Happy weekend, y'all!
things that make rewrites hard (a non-exhaustive list)
- 1,633 words (if poetry, lines) long
Over the month of August, and not counting those stories that just needed a quick once-over before being submitted, I successfully revised to completion (as defined by "I'm willing to submit it to all the top pro markets") one story. That's it! One. One measley flash-length short story.
Revision is hard.
One thing that made the task so hard to complete was skipping a bunch of the days I was supposed to work on it. And not always because I was busy driving to Kansas, cheering for and hanging out with my Boulder County Bombers peeps, and recovering from all of the above (hi! I'm a lifelong introvert! Unusually high levels of peopling will require unusually long levels of downtime afterward!) But sometimes it was just because I know revision is hard, so I run away.
This may be a bit of a catch-22.
But I'm discovering that it's really only some rewrites that are hard.
The aforementioned quick once-over before manuscript submission is relatively easy and--well, I wouldn't call it fun, not when I'm stressing out over "I should have had this submitted by now, this is taking up a lot more time than I budgeted for, whyyyyyy" while I white-knuckle my way through the piece line-by-line. But it's oddly compelling. Unless midway through I decide the piece isn't actually going to be submittable, I'm going to do it and I'm going to finish it so that I darn well can submit it. So. Not fun, but easy, for certain values of "easy."
There's also the revision process that's more like a controlled demolition of the existing draft so that the components can be used to build a new story. That one actually is fun. So while it's not easy or quick to complete, it's easy to return to it day after day.
The revisions that suck like supermassive black holes are somewhere in between. That's when a story is mostly there, but it needs fixing on a deeper than line-by-line level. But I can't see how to do it. Sometimes I can't even describe the problem(s) in a useful way. And I can't make myself feel, on a gut-instinct solid-knowledge level, that any amount of pushing words around will improve matters. I start to feel like any changes I make will only break those few things that actually work.
That's what it was like revising last month's story.
But I got it done on time and I submitted it to Uncanny Magazine with two hours to spare before deadline and got to log the rejection 3 days later so YAY! And I mean YAY because, YAY, moving closer to 100 rejections in 2019, but also YAY, one more story I can submit to all the usual places!
And the fact that the next three places I sent it rejected it in under 24 hours just means three more rejections toward target 100 and also three more steps closer to finding the editor who will love it. And those three places are in fact well known among working short story writers for preternaturally speedy rejections. We all send our new stuff there first because 1. hey, they might say yes, and 2. if they say no, they'll do it quickly, so you can send it to the next place sooner. Their slush pile is big, and they publish only a very small percentage of it, and they would even if they only published stories found in the slush pile, which they don't. But we jump in that slush pile anyway, because that's the only way to give them the chance to tell us yes.
Those are the things I tell myself, consciously and repeatedly and determinedly, because they are true. And I need to focus hard on their truth whenever that sadistic little voice in my head pipes up saying "This piece got four rejections in four days; shouldn't you take the hint and accept that you wasted all that effort last month producing GARBAGE?!" Because that little voice totally lies.
(And that's something else that makes revisions hard.)
coming soon to a horror fiction podcast near you
I signed a contract shortly after getting back from Kansas, which means it's real. So! Announcing a forthcoming Nicole J. LeBoeuf publication: My short story "Lambing Season" will be featured in an upcoming episode of the podcast Tales to Terrify. It will probably be before the end of the year. If I learn more, I'll announce it here. I'll definitely announce when it's out.
While you wait, why not subscribe to the podcast and put some fantastic horror and dark fantasy fiction in your ears on a weekly basis? Tales to Terrify episodes come out each Friday. Your host, Drew Sebesteny, will typically lead off the episode by relating the supernatural legends of a particular North American town. Then there'll be a story or two. Often, the first will be from someone writing today, and the second will be an earlier classic. The production is always top notch and narrators do a great job. Tales to Terrify episodes made my drive to and from Salina that much more enjoyable. I would definitely recommend them for your commute.
Previously at the intersection of me and Tales to Terrify: Episode 350, featuring my story "First Breath" (originally published in the anthology Blood and Other Cravings and recently reprinted by the Denver Horror Collective) as well as Victoria Glad's 1951 classic, "Each Man Kills" (which was originally published in Weird Tales). "Lambing Season" was first published in NAMELESS Digest #3.
In other news, I intend to release two Friday Fictionettes a week for the month of September: the one that's due, and the one that's precisely a month overdue. In that manner the project will be all caught up and back on its proper release schedule by September 27. So this Friday you can expect to see the August 2 release, working title "Eyes in the Rain", and the September 6 release, working title "the one about time travel and deathbed curses".
The Friday Fictionette project is a flash fiction subscription service powered by Patreon. For $1/month, you get a new story-like object every first through fourth Friday (that's the aforementioned proper release schedule) in the electronic text format of your choice, as well as access to all the archived Fictionette since August 2014. For $3/month you also get to download the MP3 where I read it to you, as well as the archived audiofictionettes going back to April 2015.
If you yourself like to write, you may enjoy the Monday Muse feature, where I share the writing prompt associated with the upcoming Friday Fictionette so you can play along at home. The Monday Muse posts are unlocked, which is to say, free for all regardless of whether you subscribe.
Hey, tomorrow I might actually wind up blogging about how rewrites are hard. I've been mentioning that for a while, but as it turns out, blogging regularly is also hard. You may have noticed.
A bunch of yay and also driving
- 29 words (if poetry, lines) long
- 46 words (if poetry, lines) long
Hello. I have just driven through a lot of Kansas. This weekend is the War of Wheels tournament in Salina, and I'm here to cheer on the Boulder County Bombers Screaming Mimis as they compete. It's going to be a lot of fun and very exciting and I am looking forward to it but what I'm really looking forward to right now is a good night's sleep because, woo, driving through a lot of Kansas.
Currently I'm at the Ambassador Hotel and Convention Center, and it's... weird. Which I supposed I should have expected. I know better than to take the cheapest hotel Google finds me. I mean, I've seen what happens when teammates do that. They come up to you at the afterparty asking wistfully, "Does your hotel have towels? Clean ones?" But in this case, the very cheap price was tacked onto a convention center. They host conventions! How bad can they be? Also, free breakfast.
And, well, they're not sketch. They're just weird. OK, from the outside they look sketch. To start with, the signage is difficult to make out--I went up and down the block a few times before I spotted it; Google unhelpfully told me "turn left (after the Subway restaurants)" and, well, that describes the driveways of about four hotels as well as an ice cream shop (Braum's) and something that looks like a rebranded Steak & Shake (Spangles!). All I could see was a big red A on black sign presiding over a seriously depopulated parking lot in front of an extinct Irish pub. But inside, it's this huge, cavernous space, four or five levels of balconies jutting out over what's unmistakably a hotel and convention center lobby, with lots of brass banisters and foliage-topped half-walls partitioning out the wide carpeted areas containing tables and chairs and, incongruously, random toy dispensers. You know, you put in a quarter and you get out a little plastic egg with a trinket inside? Yeah. And those toy dispensers make more light than the actual interior lighting of the space, which is super dim. I mean, I described it as "cavernous" advisedly. It's like a town carved into the walls of a great big cave. Also it kind of reminds me of the Christie Lodge in Avon, that one time I stayed there, only, like I said, not as well lit, and instead of pho there's BBQ.
And the place is simply deserted, undoubtedly because there are no conventions going on at the moment (unless you count the "Welcome Baptist Church!" signs visible through the windows near the locked and unlit convention center entrance; maybe it's a convention every Sunday morning) and also because the roller derby tournament hosts reserved their special rate block with the Quality Inn on the other side of the highway. I've run into a total of... three other guests, I think. Hardly anyone seems to be staying here right now. This underground cliff-dwelling is a ghost town. Or, at least, so it seems tonight. Maybe I'll get a better sense of the hotel's current population when I go over for the complimentary breakfast in the morning.
My room is pretty basic. It has the usual assortment of hotel furniture. There is a bathtub, which puts it ahead of some hotel rooms I've stayed in. Honestly, I can't complain.
But back to the actually writing, about which, this blog.
This week has been rough in terms of productivity. I managed about half of a late-starting Monday before getting pleasantly distracted by John's playing Dicey Dungeons. (That's an excellent fun time, by the way. Totally worth whatever Steam is charging for it. I may end up buying it myself.) Then neither of us managed much sleep (and not for lack of trying), so my Tuesday turned into pretty much nothing but recovering from that sleepless night in time to be functional at derby practice. I missed my daily submissions procedures and everything.
Then Wednesday I opened up my mail and found responses to five different submissions.
That's a lot. I've just gotten used to the idea that, with my one-sub-each-workday challenge, I may well have a rejection to log more days than not. OK. Fine. But five? Five submission responses? Accumulated only over 48 hours? That's... well, that's something that only happens when you have a lot of manuscripts out on submission at once. Which isn't something I've ever had before this year.
Here's the thing. Only two of those five responses were rejections.
One of the remaining three was from the Denver Horror Collective, which just reprinted "First Breath", to square away payment details with me. The contract said X amount within Y days of publication, and, hot damn, that's exactly what happened. That's always nice. Well, I say "always," but it's not like I get to deal with the post-acceptance part of the submission process often enough for "always" to mean a lot. This was only my second sale of 2019.
The other two? Were my fourth and fifth sales of 2019. Which is to say: ACCEPTANCE LETTERS. Yay!
I may have yelped and run out into the living room shouting, "It's a two-acceptance day! Eeeeee!" And then I may have tackle-hugged my husband. If so, he took it in stride.
One of those acceptance letters was for an old poem ("Your Disembodied Friends Would Like to Remind You") that I pulled out of the archives for a serious overhaul in order to submit it to a brand new horror quarterly. The other was for a previously published story ("Lambing Season") I'd submitted for reprint to an established podcast. Both should go live later this year. As usual, that's about all I can say until things develop further. In the meantime, please enjoy imagining me doing the happy dance. Any kind of happy dance. What kind of happy dance would you do? That one will be fine.
(If you are wondering, "Fourth and fifth? What happened to the third publication?" the answer is, "Didn't I mention that I sold a poem a couple weeks ago? I sold a poem called 'At Night, the Dead' a couple weeks ago. It'll be out later this year." Again, more details later.)
So my week may have slid into a rough patch, but Wednesday's inbox goodies really perked it right up! ...just in time for it to get all chaotic again what with the solo road trip and the roller derby tournament.
all right fine i'll stop denying reality are you satisfied
- 867 words (if poetry, lines) long
Hey lookit it's a Friday Fictionette! The one that was due on July 19th! At this rate, I'll be caught up... well, never, actually. The past few releases have taken more than a week each. I do not like that, and I expect I'll do something about that real soon now. But I did what I could do today, which was to finish and upload the one for July 19th.
It's "The Indecisive Lifeguard," a title with which the protagonist will almost certainly take issue. But his ability to argue is currently limited. Still, if you put your ear right up close to the granite, you just might get to hear his side of the story. (Ebook edition available for $1/month Patrons; audiobook at the $3/month tier.)
I was hoping to be able to upload that fictionette and blog about it on Friday, but, well, Friday was not a day of Doing All the Things. Friday so rarely is. I should not be surprised by this. I always start off Friday telling myself, "I don't care how tired I am after biking several hundred pounds of food uphill! I will not nap!" And then I get done with my Boulder Food Rescue shift, and I remember why naps are necessary. And then, just about the time I'm recovering from that, another physically and/or socially taxing thing will happen (e.g. Friday night dance skating lessons), which means writing doesn't happen.
This is a pattern. This is a trend. Next Friday will not magically be better. Your humble, introverted, and aging author has finally realized that this means Fridays cannot be workdays. Mostly. There will probably be exceptions. But for now, Saturday will have to be the Day of Doing All the Things, and Friday will have to be the Day of Doing Minimal Things that Saturday had been.
Flexibility! Adaptation! Serious troubleshooting! Honest self-observation an' stuff! It's harder than it looks, innit.
we pause in our endless slog through the Great Overdue for some good news
So I've spent the last week or so getting even farther behind and am now in the middle of a frenzied new push to Do All The Things Every Day, which is why you're getting a blog post again at last.
I did say I'd let you know when the latest reprinting of my story "First Breath" was out, didn't I? Well, as of... er, about a week ago, actually--sorry?--it's out! The Denver Horror Collective is soon to release their local horror anthology, Terror at 5280', and in celebration of that they're posting some stories to their website ahead of release day. My story is not in the anthology proper, but it's part of the run-up festivities, and you can read it here.
In other very pleasant news, I got an acceptance response to a recent poetry submission. Since nothing's real until contracts are signed, further details will have to wait until probably September. But the acceptance letter was definitely real, for pre-contract values of real.
For those keeping count, we're up to three acceptances in 2019, two of them poetry. The poem that just got accepted, I more or less wrote on the bus from Boulder to Longmont. Clearly I should be writing more poetry.
In case you're interested in how the submit-every-day, get-100-rejections challenge is going, I shall paste in the table with all the 2019 numbers. They are good numbers. I am quite proud of them.
|Jan||Feb||Mar||Apr||May||Jun||Jul||Aug||Total for 2019 (so far)|
In other news, revisions continue to be hard, and Friday Fictionettes continue to be way behind schedule. More about that quite possibly tomorrow if I manage to Do All The Things again.
i share with you the casserole of my people
No news today, just a recipe. Because I win at casserole, is why. And you can too! Here is how.
First, acquire seven medium-sized mirlitons. Seven is a good number. If you can't find mirliton, chayote will do. BECAUSE THEY ARE THE SAME THING. If you don't already live in a climate and neighborhood where everyone's growing them all over their backyards, I am sorry. I'm with you. I get homesick about it sometimes. If you can't just run out and pick some, and you can't find them in your usual grocery store, you might have luck with an international market. Here in Boulder, I can usually find them at the pan-Asian market over at Valmont and 28th, and I've never not seen them at the Longmont Packing Company, which is a Latin grocery and butcher shop over at Ken Pratt and South Pratt.
Take those mirlitons and boil them for a while. Half an hour? Forty-five minutes? Stick 'em with a fork. If you'd eat a potato that felt like that when you stuck it with a fork, it's probably done.
When they're cool enough to handle, slice each mirliton in half and scoop out the seeds. The seeds are kind of flimsy but the flesh around them might be kinda tough; scoop the tough bits out too. Peel the mirliton halves and chop 'em up.
Put the chopped up mirliton in a pot over medium high heat. Don't add water; just mash up the mirliton. This is a very watery squash. Use a potato masher or a fork or, if you've got one, hit 'em with an immersion blender until they're about like lumpy mashed potatoes. Add as much bouillon as would make a couple cups good rich broth. I used chicken, but you can use whatever you like. Add a tablespoon or two of butter or your favorite vegan substitute. Add black pepper, cayenne pepper, and salt. Leave the whole mess to simmer, stirring occasionally. You want to boil off as much of the liquid as you can without burning anything.
If you like shrimp, now's a good time to prepare a pound of raw shrimp. If it's frozen, defrost it. If it's got shells on, peel it. Chop it into a nice nubbin size, large enough that your mouth knows it just got a treat but small enough to get several in every spoonful. Ham is another option, chopped to the aforesaid nubbins and added directly to the simmering mirliton mess. Or keep it meatless. It'll be delicious whatever you do.
Meanwhile, heat some olive oil in a pan. Chop up and sautée a respectable-sized onion, two or three ribs celery, a fistful of parsley, and some three or four scallions. Garlic wouldn't go amiss, but it won't be missed either. I meant to put some in but I forgot. Oh well. As long as we're talking onions and celery and New Orleans cuisine, you'll be thinking green bell pepper belongs in there too, and you're not wrong, but my mom always left out so I tend to do the same. Anyway, sautée this mess until the onion's soft and translucent, at which point you'll add your shrimp if you're doing shrimp and cook it 'til it just turns pink.
If the stars are aligned and all things are in harmony, your savory vegetables will be done and your optional shrimp just pinkened about the same time your seasoned mirliton mush will be mostly liquid-free. If the stars are not particularly cooperative, you can soak up the extra liquid with half a cup or more of bread crumbs. Actually, just add the bread crumbs regardless. I mean, it is a casserole. Combine the two messes into one big mess, stir it up good, then decant it into a 9 x 13 baking pan. Put more breadcrumbs on the top. Plain? Italian style? Panko? You know what you like. Make it happen.
Bake at 350 degrees F until done. "Done" to me means that there have been visible bubbles percolating up through the casserole for a while and that the breadcrumb topping has gotten some definite golden brown crisping action around the edges. Bake it until it's whatever "done" means to you.
Let sit about ten minutes, then eat it while it's hot. Leftovers may be reheated or eaten cold, optionally right out of the baking pan.
And that is, more or less, The Casserole Of My People.
a list of things which are not excuses followed by a list of things which are good things
- 1,299 words (if poetry, lines) long
Last week was eventful. Not the good kind of eventful, either. I had a headlight to get replaced on a car, a sudden flood of water from the ceiling to investigate, and, most worrisome of all, a computer that wouldn't power on. It all pretty much hit last weekend and overshadowed the week. Not that these things are precisely what made last week so dire in terms of productivity, but it can't have helped, you know?
In any case, the headlight was easily taken care of. The mysterious leak less so, as it involved coordinating with my upstairs neighbor; thankfully, the maintenance crew who responded to the emergency call took point on that. As for the computer...
Well, it's amazing how much I was able to get done, or at least could have gotten done, despite not having up-to-date backups of my Scrivener files available. These days I mostly do my composing and editing on 4thewords, which meant all my current projects were accessible as long as I could remember my 4thewords password. Which I could. And so many of the places I submit stories to use online submission management systems (Submittable, Hey Publisher, Submission Manager) that I never had trouble keeping up with my daily submissions; I just logged onto whichever system I'd submitted a given manuscript through last and downloaded a copy. I had recent enough versions of many useful things on the two Asus laptops that were my previous two workspaces before this Dell. And I was able to keep up with email via the webmail options my domain host offers.
Which is not to say I didn't breathe a huge honking sigh of relief when, after the Dell onsite technician installed the replacement motherboard not 6 days after the power-on failure (always spring for the extended warranty if you can afford it; Dell's is particularly good), the computer booted up to windows and demonstrated that all my data was sound. And you can bet I initiated better backup habits that very night. (Did you know Mega.nz offers 50 gigs cloud storage on just their free account?)
It turns out I could have accessed and backed up my data at any time. I assumed that my hard drive would be buried under intricate layers of machinery, but no, it is surfaced for customer access just like the battery is. I could have yanked it out and slipped it into a usb shell that I already possess and ported my entire life back onto the old Asus machine that became my workstation during that week. Well. Now I know, should a similar calamity befall me in the future.
(And it might. I seem to average one computer crisis per year. I'm kinda death to laptops. Again, spring for the extended warranty every time you can afford it--it is so worth it. I know mine's got me covered through December 2021 or thereabouts.)
However. During that time I kept up with my daily submission procedures and nothing else. Failed to do my short story revisions. Got another week behind on Fictionettes, Just kinda sucked in general. It was like my own personal physical/mental/emotional system wouldn't power up any more than my Dell would.
But the first two days of this new week have been a lot better. Like, oodles of percents better. And I have good things to report! To wit:
The Friday Fictionette that was due July 5 is finally out. It's "A Practical Guide to Your Magical Hero Destiny" (ebook, audio), which is an ironic title because you don't actually get an instruction manual for that kind of thing ha ha ha are you kidding? I'm hard at work on the July 12 release as we speak, with hopes of getting entirely caught up by sometime this weekend.
Since I last blogged, I've received notification that two more of my submissions have survived the first slush-culling and have been "bumped" to a secondary round of consideration. Both of them are currently unpublished drabbles, or 100-word short stories, which I had considered long shots unlikely to find favor at any market. You just never know.
And I'm going to suggest that you go ahead and subscribe to The Epitaph, the newsletter of the Denver Horror Collective, for no particular reason other than that you are clearly a fan of Denver-area horror writers, right? Or at least one particular writer who resides in the Denver area and writes things that might be classified as horror? Anyway, it's only monthly, so it won't fill up your inbox like some newsletters I might mention. And you may be intrigued by what shows up there.
And that's the news for now. With any luck I'll manage to post more tomorrow.
the hardest working little story in my stable
- 1,129 words (if poetry, lines) long
- 1,362 words (if poetry, lines) long
So this blog post is mainly to announce that my short story, "First Breath", will be reprinted again. I'm not sure exactly when and I don't think I'm at liberty yet to say exactly where, but I have Signed a Contract so it's pretty darn definite.
I'm tickled to now be able to call this story "my most reprinted story." It will have been reprinted a whole two times. Go little story, go! On the other hand, I'm less than impressed with myself; my last two prose sales--that is, counting only short stories, not poetry--have been reprints of this story. And while I remain quite proud of this story, it first saw print eight years ago, you know? I've been writing all sorts of things since then! I would very much like to get an acceptance letter for a new thing! It would help reassure me that I am still capable of writing publishable stories!
But I'm not complaining too hard here. Yay, a second sale in 2019! The numbers game works!
Speaking of the numbers game, here are those numbers:
Meanwhile, I'm still behind on all things Fictionette. But as of Monday, the Friday Fictionette for June 28th is up: "Right on Time" (ironic title, that--ebook here, audiobook here). Like many stories, it's about how things can always get worse. In this case, things get worse when the wrong miracle happens to the absolute most wrong person. Also, as of today, I've released the Fictionette Freebie for June 2019 to the world at large. You no longer need to be a Patron to access the Friday Fictionette for June 14, "Love in the Time of Lizard People".
I have a whole 'nother rant in me about how REWRITING THINGS IS HARRRRRD but how about we save that for tomorrow? Yeah, lets.