Interesting write up of To Be Men

Blogger, Powered by Robots, had some interesting things to say about voices, writing, and To Be Men: Stories Celebrating Masculinity.

I decided to write about this because I’ve gotten a hold of a review copy of the To Be Men: Stories Celebrating Masculinity anthology edited by Sirius Métier and published by Superversive Press. It was published digitally about two weeks ago (as I write this) and seems to be doing pretty well, both relative to its Amazon reviews (five so far, and all five star ratings) and in terms of sales.

One thing the twitterati forgot about when they were raking male authors over the coals, was the intended audience of the story being written.

Read the rest, and his follow up posts based on each story, here.

Time and Distance: The benefits of cycling.

One of the reasons I work on multiple projects at a time is because my writing process is unlike anything else in my life. Most other aspects of my life are filled with clearly defined steps, checklists, and algorithms. Exceptions are clearly defined by “if,then” statements. Loops are set up in very specific ways. This includes the laundry.

Writing is the one thing I do that doesn’t work that way. It’s why I don’t outline (waste of time; I don’t stick to it; I write them AFTER).

Give me a beginning and/or an end, a theme or a moral point, and I can make it all work. Give me an already written ending and a song and I’ll give you a story (more about this when it’s official).

Think of a finished story as a sequence of scenes, numbered from 0 to N. Chances are, it’s been marinating in my head for some time and exists in one form or another as a set of notes, scribbles, and research references in a Scrivener file, waiting on me to get stuck on my current project and in need of something else to work.

A work in progress (WiP) might originally start out as scenes 5, 12, 18 … 52. Of course, at the time I’m writing them, I don’t actually know that, but you get my point. It’s not unusual for me to realize that I need to cycle back as I’m writing scene #18 and then come up with #13-#17 or go back and fix #12 so it works with #18.

Yesterday I spent the whole day writing (for the first time in awhile as I’d gotten side-tracked by other projects; I spent the whole day in pajamas and I think I ate).

There is nothing quite like time and distance to make you see that scene #156 is no longer a good fit. There’s also nothing quite like time and distance to make it easy to gut #156 if that’s what the story needs.

And by gutting, I mean opening up a new Scrivener scene document, and typing it out fresh after getting myself solidly set inside the character’s head. It is being inside the character’s head that allows me see that scene 156 no longer works.

It’s an entirely different process that “editing” an existing set of words and polishing the hell out of that turd hoping no one will notice what it is.

This is why writing takes time–and I’m talking writing here, not typing. All kinds of time go into “writing.” Research time. Down time (like a hobby or reading for pleasure).

Time spent cycling back to read what you’ve written so that you can get into your viewpoint character’s head before you move forward.

Time spent looking stuff up as you go along when you realize you need an essential piece of information (like can they really match bullets to specifics guns–the answer turns out to be a resounding NO!).

Time spent arguing with your characters because they don’t want to go where you want them to (aka writer’s block, at least in my case).

Is it worth it? I guess it all depends. I’m not a big fan of typing*.

Typing: Julie was a dog lover.

Writing: Julie tossed a TV dinner into the microwave for her husband and rushed out to the grill to make sure that Precious’s steak didn’t get overcooked. Great Danes were known for their particular tastes and she hoped he liked the kobe beef as much as the butcher seemed to think he would. Of course, the butcher had been under the impression that it was for her husband, and she hadn’t enlightened him. He wouldn’t understand. No one would. No one but Precious.

*For a better explanation about the difference between typing and writing, I recommend Writing to the Point: A Complete Guide to Selling Fiction (The Million Dollar Writing Series)

 

 

Now LIVE! on Kobo

Kobo was actually the easiest one to set up. Added bonus, they are part of OverDrive, a system that allows libraries to lend eBooks. So, if you’ve wondered how to get your work into libraries, this is one venue. I think it’s also available through other aggregators.

But why would I want to “give” my eBook to libraries? First, you’re not “giving” anything. Second, having your book in a library is advertising. Someone who enjoyed your work might just decide to check out and see what else you’ve written. Gasp! What a concept.

Rejection 101: A Writer’s Guide is now available on Kobo.

Didn’t need an ISBN for this either. Yes, this means they’ll have different ISBNs, but I don’t expect this to be something that needs tracking to justify the cost of an ISBN.

Now LIVE! on iBooks

As I said before, the self-pub plunge is as much for the benefit of the experience as anything else. iTunes Connect was easy enough to navigate. iTunes Producer, like most Mac programs, a breeze.

Easy set up. One glitch because I didn’t have the latest version of Java installed.

Review was MUCH faster than Amazon.

And now I’m live on iBooks with Rejection 101: A Writer’s Guide.

One of the nice things I noticed about this is that it’s very easy to set up promo codes.

No, didn’t need an ISBN for this either.

I took the self-pub plunge

Most of my author friends are self-published or hybrid writers. I often feel “out of the loop” when it comes to the details of the self-publishing process, so I decided it was time to take the plunge. At the behest one of them, I took the six blog posts about my workshop experience and why a rejection is an opinion (not a death sentence), and created a book: Rejection 101: A Writer’s Guide

Although it took all day, it took far less time than I thought it would.

I already had the KDP account set up, but I had never worked with the KDP system or Vellum (the layout software).

Here’s the run-down of what it took to go from a series of blog posts to a finished product.

I chose an image off DepositPhoto.com, and fired up Pages. This probably ate up most of my time. It had been awhile since I’d worked with Pages for anything other than writing, but it all came back to me. Create a black background. Add image on top. Check the reflection option. Add the fonts for the title and author. I spent more time playing around with fonts and colors, to be honest. Way too many choices, most of them bad. Saved it, changed the type of file, and done. Reopened it in Preview in order to adjust the ratio of image width to height, per Vellum’s suggestion. That took like another minute.

Next, Vellum. Great software, took about ten minutes and one very specific question posted to a group, and I had it figured out — the front and back matter, the chapters, the headers, dividers, everything–bam, bam, bam. It was amazing. By contrast, I was struggling with Jutoh for days before I threw my hands up in disgust and wished I’d never heard of it. With one press of a button, Vellum generated everything for all the platforms/venues/formats, all in one step: Generic ePUb, GooglePlay, iBooks, Kindle, Kobo, Nook, and Print (i.e. a PDF).

It took longer to actually proof the PDF, Kindle and iBooks files (by looking at every page inside the file) than it took to put the book together, and that includes futzing around with the fonts and colors. (BTW, leave the extra pages in the PDF alone. They’re there for a reason.)

Vellum is pricey, but worth it (works only on Mac). You can play with a full version for free, but you have to have a license to hit that magic button that spits out all the stuff you can then upload to the various venues. No, you don’t need Vellum if you’re doing KDP because you can upload a .docx or .PDF or .rtf file instead, but that doesn’t mean that all your versions will look the same if you wide (other platforms).

Uploading to KDP was simple enough. The one snag I hit was with the paperback version, which took two tries to get right, so maybe fifteen minutes to re-do.

Did learn that you don’t need an ISBN–Amazon will “give” you one.

There was a 24-hour turnaround on the approval process.

Voila. That’s it, in a nutshell. Even a rocket surgeon can do it.

Up next, publishing on iBooks, Kobo, and Nook. Also CreateSpace, D2D, all this stuff I’ve heard of but never had a reason to look into too deeply.

When the heroes are bad guys

“Make your characters interesting.”

Don’t recall exactly where I got this little bit of writing advice, but I was thinking about it when a few someones came up to me and asked if I’d seen Lucifer. I think it was prompted by “The Devil You Know” (an unpublished short story of mine) which featured The Duke of Hades.

Fast-forward a couple of weeks and I’ve got the first disk of season one and I’m setting myself up for another Hollywood disappointment—my standards for anything coming out of Hollywood have fallen so much that I’d rather watch Korean dramas with subtitles (which I hate because they’re distracting).

Nevertheless, hat tip on Lucifer. I loved it. From the first episode. And no, it wasn’t all because of the eye-candy, or the arrogance, but because they somehow managed to make him interesting in a good way.

Plus, I seem to have a soft-spot for anti-heroes.Continue Reading

A rejection is an opinion, not a death sentence (part five)

Part One

Part Two

Part Three

Part Four

Mar. 1st, 2018

The fifth story was an exploration of dragons.

The first thing the buying editor admitted to was the fact that she did not articulate what she wanted as well as she thought she had. Unfortunately, that wasn’t apparent until she got the stories and it was too late to do anything about it. This brought up another important point about things that influence editorial decision-making. When they get a lot of stories that aren’t quite right (for whatever reason) the pressure on their time increases. They need to keep an eye on these time pressures, so they are more likely to buy stories that don’t need work.

Read the rest here: Rejection 101: A Writer’s Guide

Part Six

A rejection is an opinion, not a death sentence (part four)

Part One

Part Two

Part Three

Feb. 28th, 2018

 

The theme for story four was “chances,” and although there were plenty of clues in the submission call that it was to be a romance anthology, it was never explicitly stated. Two people that take chances to be together didn’t say “romance” to everyone in the group, and I can see why that would be the case. If you don’t write romance, your version of “two people taking chances to be together” could manifest in other ways—a father and daughter trying to find each other when war comes to their world. Therefore several well-written pieces just didn’t make the cut because they were not, technically, romances.

Others had romantic elements, but the romance wasn’t the main focus, but a sub-plot.

But romances are right up my alley and since one of the examples in the call was “Anthony (conquerer) and Cleopatra (conquered)” that was the first plot bunny I chased down the wrong hole. For four days. Yep, I gave up on it some time late on Thursday and went to bed knowing I’d have Friday and the weekend to start fresh. Fun times. Fun times.

Read the rest here: Rejection 101: A Writer’s Guide

Part Five

A rejection is an opinion, not a death sentence (part three)

Part One

Part Two

Feb. 27th, 2018

The story for the third week had to do with strangers dealing with each other. And it was another one of those that made me scratch my head, especially the part about not wanting to read anything icky since it was a parent-child editorial team. No definition of “icky” was provided.

In retrospect I realize that my fear of putting in any details about sexual attraction actually kept me from adequately fleshing out the emotional aspect, which was something they did want. But, apparently, I can’t write anything that doesn’t tend towards having a romantic aspect of some kind—yes, it’s a personal flaw and probably not one I will fix since I like my romantic tensions too much.

This story started with an image of a blonde woman in a white suit and pumps, holding a pearl white briefcase, getting ready to go through a stargate.

I had no idea she was going to end up in Hell, no idea I was going to use a character I’d used in another (unpublished) story, no idea it was going to be about what it ended up being about, no idea that I was going to play off the Persephone/Hades myth. I had no idea I was going to bring in the concepts of war being hell, of military traditions, or a statement on totalitarianism.

Read the rest here: Rejection 101: A Writer’s Guide

Part Four

A rejection is an opinion, not a death sentence (part two)

Part One.

 

Feb. 26th, 2018

The workshop’s second assignment was another difficult one. The theme was “Broken Dreams” and the editor specified that she didn’t want the “Boulevard of Broken Dreams.” Even with the 8000-word limit, I wanted to skip this uncomfortable subject.

But I had to try. Otherwise, I’d be wasting my time and money, and losing a chance at getting some valuable feedback and insight on how to do it better later.

I’d been researching privateers for some reason (probably because something shiny flew by and led me there) so the first thing that came to me was to do a story about a guy that got cashiered and lost his opportunity for command. This turned out to be one of those cases where I was doing pure discovery writing (I had no end in mind at all) and no idea how to get there. I started with a character and waited to see where he took me.

After a couple of false starts, the character took 5500 words to take me here:

Read the rest here: Rejection 101: A Writer’s Guide

Part three.