Marscon 2018

Just as much of a recap as I can manage after an exhausting weekend at Marscon:

This is the typical post-convention blog recap which is really just an excuse to plug the names of the people who I worked alongside or whose panels I attended.  A warning:  I’m writing this in a stage of near delirium-inducing exhaustion, and sometimes I have to refer to the program guide to keep straight who was on which panel.  If you are one of the panelists I worked with and you notice a name mentioned on the panel who shouldn’t be there (or a name there that shouldn’t be there), let me know and I’ll make corrections.

Friday:

While the trip down (on Thursday) was uneventful, Friday started out a little weird in the food department.  I usually make it a point to make my first meal at a new hotel a room service meal, just to settle in.  Problem:  I couldn’t get through to room service from my hotel room phone.  After several tries, I gave up and went down to their breakfast buffet.  Learning that my guest badge wouldn’t be available until noon, and remembering how that went at Ravencon (as this was only my second convention as a panelist, I had no idea if this was standard practice or not, but the badges weren’t available until after some early panels started running at Ravencon), I waited until lunchtime to get my badge and welcome packet, and when it was actually there on time I went to lunch.

I ordered a panini sandwich and — in my biggest culinary mistake of the convention — a “starter” (which I interpreted as “appetizer”) portion of calamari.  Out comes this plate of calamari (which, admittedly, was pretty good) that was larger than any TWO plates of anything else on the menu.  I needed a to-go box… and discovered that the mini-fridges the hotel provides aren’t big enough for to-go boxes.  (I still was able to put it away by repackaging it in a ziplock bag I happened to have, but still a bit frustrating).  Oh, and cold, left-over calamari is not mankind’s most appetizing meal, but at least I had dinner taken care of.

First, I attended (not as a panelist) the Fandom Generations panel. I’ll be honest, this panel — which, whatever the write-up said, basically turned into a discussion of “by what path did you become a con-goer” — was not the most interesting of topics for me, but I wanted to attend at least one panel before I started being on them, and this one had Toni Weisskopf (Editor, Publisher, and apparently even the Art Director of Baen Books… and co-author of Greasy Grimy Gopher Guts, which I proudly own a signed copy of) on it. The panel seemed to have trouble sticking to the topic (or any topic, really), but it was still fun.

Next was my first panel as a panelist: Costuming in Fiction: Creating the Total Package. I had this panel alongside fellow author Pamela Kinney and Charlie Stayton, a developer of card and role-playing games who — as came out during the panel — has occasionally worked as a technical consultant for historically-set films.  I had an excuse to wear my Sherlock Holmes hat (and discovered it was too hot in the panel rooms to wear that heavy a hat for every panel), and used it in a discussion of how certain items of costuming are so iconic that the character is expected to wear it, even if (as was pointed out during the panel was true of the deerstalker) said item never appeared in the text of the book.

We talked a lot about why costumes matter in fiction, how to consider what the costume says about the character, as well, and probably several other costume-related things I’m forgetting at this time (I’m writing this while recovering from the con in my hotel room, dead tired and a little fuzzy-headed, so… don’t expect much from this blog). The panel went pretty well, I thought, but the sore spot for me was that I accidentally left all of my give-away swag back in my hotel room, and there were people who wanted to grab some from us panelists; I did have a small business-card sized thing for one book, but that was it. *sigh*

I skipped the Opening Ceremonies. Hard call, but especially in this cold and flu season (despite getting a flu shot a few weeks ago) I think it’s important not to skip meals when at public events like this… even if that meal was cold, leftover calamari.  It also gave me a chance to grab the missing swag I forgot.

Not that I needed it for my next, uh, “Panel”: Fantasy Draft League, where I faced off against Baen editor Jim Minz. According to the panel description, this was supposed to be “Fantasy football, but hold the football. Our authors assemble an adventuring party from fantasy characters and duke it out to determine the one bracket to rule them all.” Both of us “panelists” had no idea what the rules for such a thing would be, figuring whoever came up with the panel idea would have had some.

Maybe they did, but whoever came up with this panel wasn’t on the panel, so we came up with rules of our own for this “Fantasy Fantasy league” style draft: We would pick teams that fit various fantasy staple trope characters (such as the Knight Paladin, the Big Dumb Barbarian, the Wizard, the “Face”, the Rogue, the Supply Officer, the Goalie (okay, we threw that one in here as a nod to the sports fantasy element; in this case, the person best capable of defending the home base while the main party is elsewhere), and the “Substitute” (who would be able to go out and sub for any role if someone was… unavailable)). Then, once we picked our teams, the audience would vote on which character “won” that position. When all of that was done, we have a vote on whose team would work together best.

In the end, it was a tie; my team of King Arthur (legend), Cohen the Barbarian (Discworld), Lina Inverse (Slayers), Vlad Dracul (Dracula), Bilbo Baggins (The Hobbit\Lord of the Rings), Xanatos (Gargoyles), McGonagall (Harry Potter), and “Wiz” Zumwalt (Wiz Biz) went toe to toe with Jim Minz’s team of Buffy (Buffy the Vampire Slayer… TV version), a Balrog (Lord of the Rings… though I nearly challenged the notion that a Balrog fit as a barbarian, here; I was prepared to argue the merits of picking Cohen the Barbarian over Conan the Barbarian, not Cohen vs. a bloody Balrog), Gandalf the Grey (again, Lord of the Rings), Achmed the Assassin (I’m afraid I missed his full name, and which series he was from), Milo Anderson (Monster Hunters International), Granny Weatherwax (Discworld), and Sauron (yet again, Lord of the Rings).

I next attended (but was again not a panelist on) the “Building a Space Station” panel. This panel had a team of scientists and engineers, moderated by Toni Weisskopf, talking about the logistics and motivations behind building a space station. I’m not going to go into my full reaction to this panel, because I probably would have to name names, but I personally thought it would have been a more enjoyable panel had there been one fewer scientist on it.

And, for my last Friday panel, I was a panelist on Research, Point of View, and Filtering, alongside fellow panelists Rowan Worth and Y.A. Guest of Honor Maria V. Snyder.  Honestly, I was a little dubious, as this was a pretty heavy topic for a 10pm panel, and one of the expected panelists (Kim Iverson Headlee) was late, and chose to sit in the audience instead of up front, when her prior panel ran long.  However, we summoned up enough energy to have a fairly entertaining little panel, energizing the audience at least a little, and (surprisingly) it ended up as the best attended of that day, for me.

Then there was Saturday.  I did not get enough sleep Friday night (sadly not because I was having fun with room parties or whatever, but because I had trouble getting comfortable on the hotel beds, which made getting to sleep difficult and woke me up way too early.  It made the whole, busy day just a touch more difficult for me.

I opened the day (after breakfast) with a seat as a panelist in the Allen Wold Writing Workshop.  I’ve participated in this workshop, before, from the “other side” of the table (as a participant), but this was my first experience as one of his other author-guests.  This workshop is an institution at many of the conventions I attend, so I was proud to be invited to be a part of it.  I was a little afraid to bring a pen and paper, or my laptop, because I was worried I’d start acting like a participant instead of a guest out of habit.  I enjoyed myself, and I think I was able to add some meaningful contributions to the workshop, so I think it was a success.

I may never know just how successful, however; there was a Part 2 to this workshop where the guest-panelists could see, roughly, how much improvement (at least in the 100 word hook paragraphs that were produced in the workshop) the participants could make based off of their comments; sadly, I was scheduled on another panel at the same time Part 2 took place, so I missed it.

After the workshop, I retreated to my room for a couple hours before my 3pm panel, “Questions to Ask before Creating a Fictional Culture,” alongside Christopher de Matteo, Jim Beall, and Donna (D.M.) Patterson.  I am not sure how this panel went, actually.  There were times I was expecting the audience to interact or make comments and they didn’t (it’s especially unnerving when you’re trying to end your point with something you think should get a big laugh, and the result is complete silence).  There was a moment where I thought that the panel had completely lost the audience and then suddenly we had a series of relevant questions related to the topic.  I think the panel went well enough, but I couldn’t read the audience reaction at all.

After that panel, I had to run back to my hotel room and dump some things off before heading to the 4:30 Baen Traveling Road Show.  This is something Baen puts on at dozens of conventions where Baen’s cover art is presented (and promoted), and bits about the artwork or the book itself are discussed.  Baen gives away a lot of books at these panels (I did not get a book, this time; ah, well) as well as other swag (I did get an interesting bit of swag, but I’m not sure how to describe it.  A… plastic logo pendant for Baen Books on a string of mardi gras beads?  I’m not sure what this was supposed to be, exactly).  I don’t always go to it, but I’ve always found the ones with the aforementioned Toni Weisskopf presenting are can’t-miss shows, so I went.

That was fun.  We got to see a piece of cover art intended for a future David Weber book that even David Weber hadn’t seen yet, there was a discussion about how a particular anthology editor\writer (Eric Flint) and his anthology’s cover artist (I’m afraid I didn’t take notes, and I don’t want to get the name wrong, but he’s the regular cover artist of the Grantville Gazette) had a friendly rivalry going where the cover artist would draw a piece of artwork (with increasingly complex scenarios) and the editor’s story contribution would be made while trying to fit the cover art into a scene of his story.  A few other things like that.

When that presentation ended, I scrambled to find a meal before my 7pm panel on “Worldbuilding 201:  Filling in the Details” about getting into the smaller details of worldbuilding.  This panel was with Maria V. Snyder, Pamela Kinney, and Chris de Mateo, all of whom I had worked with on a panel earlier in the convention.  I think that helped make this panel a little more lighthearted and fun, and I think the audience reaction was largely positive.  The panel ran a touch long, though within the margin of error.  (It’s generally a good idea for each “hour long” panel to run for 50 minutes, so as to allow guests coming in to set up and people to move between panels without having to hurry too much; we nearly hit the full hour, however.  Marscon, I will note, had a strange system this year where some panels had moderators but most didn’t, and while a panelist stepped up to take charge on every panel I either worked or attended, there was a lot of discussion about that among the guests.  Someone stepped up on this panel, too, but he wasn’t keeping track of time).

When that was done I had to immediately head to the room next door for Mapping Your Novel, at 8pm.  I was again paired with Maria V. Snyder (and it was just the two of us on the panel, this time), and we were both clearly flagging by this point (neither one of us wanted to bother with our whole “introduce ourselves” spiel, beyond letting everyone know our names), but I think we helped inform the crowd (which asked a lot of questions, was engaged in the discussion, and reacted positively when more amusing things were discussed) and I had fun.

My final panel on the day was “It Takes a Village (Traveling at 80% of the Speed of Light)”, alongside Mark Wandrey and Drew Avera.  I was absolutely totaled, by this point, and this was my third panel in a row, so I’m not sure how much I was able to contribute.  I don’t think I embarrassed myself, at least, even if I didn’t get around to discussing all of the points I had come up with for the panel.  There was a very small crowd and we ended the panel a little early because none of us wanted to keep talking, I think.  I was so tired I don’t remember much of what we talked about, to be honest.

I did have other “fun” things I was hoping to attend, after that, but between the lack of sleep the night before and all of the panels that day I was just too worn out to do much else.  I was also starting to get a little hoarse at the end of that last panel (from talking so much; I was fine by morning), so I figured I’d just call it a night.

I certainly did NOT have trouble getting to sleep that night (while I woke up a little earlier than planned, it wasn’t that much earlier), but I was still feeling a bit worn out in the morning.  Still, I had enough energy to go to the panel “Freelancing in the Publishing Industry,” presented by Chris Kennedy and Toni Weisskopf.  I might have skipped it, since I wasn’t one of the panelists, but I knew this was in the rumored “room with the comfy chairs,” and I was able to get one of said comfy chairs by getting there early enough.

The comfy chairs led to a relaxed atmosphere, and the discussion was very interesting.  It actually started with a description of the difference between hiring an employee and contracting a freelancer (including the tax and regulatory concerns, which even in Baen’s case make employing freelancers preferable to full-time employees, in some situations).  Mentally, I was comparing my purely self-publishing experience searching for and hiring freelance editors and cover artists like Keith RA DeCandido and Joel Christopher Payne with the experiences of Chris Kennedy, a self-published author turned full-fledged small press publisher who has a regular stable of freelancers he works with, with Toni Weisskopf who is a long-time industry veteran as well as the publisher, editor-in-chief, and art director for the largest independent science fiction publishing house in the country, heading a company with several full-time employees as well as commanding a much larger stable of freelancers on a regular basis.  There were more similarities than I was expecting, to be honest, which was a pleasant surprise.  (Though, as you might expect, both publishing houses have been in this field longer than I have and have larger budgets for this kind of thing than I do).

I originally had planned to follow Toni Weisskopf for a couple more panels (her next panel was Beyond Infinity, which I’d hoped to go to, and it would have been followed by the even more interesting Hard Science: Gift or Curse panel, which might have been of benefit to the Rink of War for when I get around to turning that into a novel), but without the lure of the comfy chairs I figured I needed more physical rest if I was going to be in any sort of shape for my final panel of the convention.

That last panel was at 1pm, “The Name Came First,” alongside Guest of Honor Carrie Vaughn as well as fellow panelists Tara Moeller.  At one point, there were supposed to be as many as five people on this panel…

Which would have been real overkill, as there weren’t even five people in the audience for most of this panel (for a GoH panel, attendance felt… uh… low), with only two people at the start and two more wandering in about fifteen minutes later (though several others popped in by the end, though they were late enough for me to wonder if they were waiting for the next panel).  We started not by introducing ourselves, but by asking if we wouldn’t be better off moving the whole panel over to the hotel bar.  Had it been Saturday night instead of Sunday morning, I suspect we would have.  We did, eventually, get on with the topic — which was suggestions for answers to the “what do we name our characters?” question, evolving into a discussion of naming conventions, apostrophes in names (yay or nay), etc.

And then the convention was over.  I was originally supposed to meet some family members local to the convention who I only get to see once or twice a year after that, but one of them had hurt their back and the other came down with the flu, so those plans were scrapped.

Overall thoughts:  This was only my second convention as a full-fledged guest, but I could tell there were some oddities.

  • Almost every panel I was on had a “who’s the moderator?  Oh, wait, we don’t have one?” conversation before the panel started.
  • Unless it’s a regular and long-established panel that’s a con tradition, it’s expected that the person who suggested the panel will be on it; that didn’t seem to be the case with ANY of the panels at this con.
  • I didn’t realize quite how busy I was until I started putting this together.  More panels as a guest than at Ravencon 2017, and I sat in the audience on a few others besides.  I think I’ve got a better idea on how much I can manage for the future, but I really do need to get enough sleep at night, despite the hotel beds, if I’m going to try and manage this kind of schedule at future conventions.
  • Panel attendance seemed lighter than I remember from past conventions, both as a guest and as a regular con-goer, and it wasn’t just me who noticed.  Considering the number of attendees I was expecting (the hotel sold out and an overflow hotel was needed), I wouldn’t have thought that likely; I’m not sure if it was just a case of no interest in the panels, or if the weather or something else had prevented some people from coming.  I’m honestly wondering if it might have been partly because of the flu epidemic that’s been so fierce, this year.
  • I love the Marscon Con Suite, because it provides full meals for free (which can really reduce the cost of attending a convention).  Somehow, I never went.  I also never found (or even seriously went looking for) the Green Room.  Mostly that was because of the “I  accidentally wound up with two and a half meals worth of calamari from my calamari appetizer” issue, but when the event ended and I realized I never even went looking for these rooms, I was surprised.
  • I also never made it to the Dealer’s Room.  I was just either too busy or too tired (or both) to do so.
  • I’m not going to attribute this to anyone, but I will say I overheard one of the major author guests saying:  “Is Barnes and Noble TRYING to put themselves out of business?”  (Not sure what sparked that comment, but I’ve had the same thought a time or two).
  • Several guests and\or former guests who had been planning to attend anyway were unable to because of deaths in the family or health issues.  More possible support for my “attendance was lighter than usual due to the flu” theory.
  • I wish every panel I was on was in the comfy chair room, even if that was one of the smaller panel rooms.  I was really uncomfortable sitting in some of the chairs the hotel provided, but those chairs were really nice to sit in, and made for a very cozy atmosphere for discussion.  Maybe it’s not really appropriate for every possible panel, but I think several of the panels I was on would have benefited from that room (and I know my knees and back would have).

And… that’s it.  I’ll get back to work on my regular blog posts soon.  If you would like my take on any of the panels listed above (as I had been doing with last year’s Ravencon Panels blog series) please let me know, and I’ll start on that once the “This Book Cannot Make Any Money” blog series is complete.  Until next time, have fun out there!

2017 Year In Review AND An Out-of-Order This Book Cannot Make Any Money post…

As promised last weekend, today I’m going to do my “Year in Review” for 2017.  After that, I’ll be giving my Marscon schedule (since it arrived this week), but first, an announcement:

“This Book Cannot Make Any Money” was submitted to KDP Print and  is now live on the Amazon store, though in print form only. Keep in mind that I was never able to get a print proof (the reason I decided to do this series NOW rather than a few months from now was that KDP Print had announced they were now offering print proof options, which made me want to try them out. I’m a bit frustrated to learn, in the end, that I wasn’t in the beta group offered the ability to buy print proofs).

Not having a print proof is both good and bad for the “This Book Cannot Make Any Money” series. It’s good, in that I’m forcibly unable to “cheat” and spend money on the proof copy, and must only use the “free” online reviewer tools to see how things come out. It’s bad because, well, I know from working with Createspace that print copies can look dramatically different in real life than they do in the virtual proof on-line.

You can go ahead and buy a (print) copy now (I will not be able to get around to working on an ebook copy until after Marscon), but be warned that these may be (ahem) misprints, at least until after I’ve had a chance to go through the print copy.

Now for the Year in Review:

I had two publications in 2017.  One was the short story (really novella), “A Gun for Shalla,” published in the “Worlds Enough: Fantastic Defenders” Anthology.  I have no idea how, exactly, the sales have been for it, but the reviews have generally been very good to excellent.  The point of an anthology like this is not to turn a profit, necessarily, but rather to cross-pollinate the fanbases of multiple authors, and good reviews help with that.

As far as the books I actually have stats on, however:

In Treachery Forged sold 195 ebook copies and one print copy.  Yeah, my print sales never do well.  One hundred ninety five copies may sound small, but it’s been out for four years and there were no new books in the series released this 2017, so that’s not too bad.  I expect sales of this book to go UP in 2018, as I intend to get the third book out.  It remains my best-SELLING ebook (though it is no longer my biggest money-maker, as we’ll get into later).

In Forgery Divided sold 182 ebook copies and TWO print copies.  While it’s only in its second year, I’m still satisfied with those sales, as — again — there were no new books in this series in 2017.

The Kitsune Stratagem sold 32 ebook copies and three print copies.  The Kitsune Stratagem has ALWAYS underperformed, and I have yet to understand why; I honestly believe it’s my best book, but it always seems to get the fewest sales no matter what I do as far as marketing for it goes.  I’m hoping to “re-launch” it when I get the next book in the series out, but its low sales have reduced the priority of that next book significantly.  I really, really want to get back into this series, however.  There’s an outside chance I’ll get to its sequel in 2018, but I doubt it.

One oddity:  While The Kitsune Stratagem is my worst-selling full-length novel in eBook form, it ALSO is my best-selling print book… with fifteen print sales, lifetime.  I really, really wonder if print books are worth it, sometimes, considering how much time they take out of my writing.

To the Rink of War is a special case.  I don’t really count it as a “book,” because it isn’t one:  It’s a short story, or rather (by the standards established by the SFWA)  a novelette.  Priced at $0.99 (which is the LOWEST I can set the price; no, I can’t make it free) I literally get nothing more than pocket change from each sale.  And, until this year, I could just about count the number of sales on my fingers (that’s hyperbole… but only just).  But, well, there was a bit of a surprise resurgence of interest in this story.  With 58 ebook sales (there is NO print version), I’ve literally tripled its lifetime sales in one year.  Not great, but enough of a spark of interest that I thought I might re-visit the story, taking both it and its intended sequels and knitting them together to form a full-length novel.  A novel is important enough I could afford to spend some money on things like a new book cover, better editing, etc.  Originally I was going to try and get that out in 2018, but a radical shift in priorities makes that… unlikely.

Finally, there was The Merrimack Event.  The Merrimack Event managed a grand total of 2,911 sales (which already makes it my second-best selling book, in terms of lifetime sales).  In addition to that, however, this book was my first foray into the Kindle Select story, which put it into the “Kindle Unlimited Lending Library.”  That is Amazon’s version of a “Netflix for Books,” a sales model I am dubious of, which nevertheless made this book the top-EARNING book of my career.  I had 4,869,121 page reads through KULL.  In addition to all that, I also signed an audiobook contract which earned me a $500 Advance, and should also start earning royalties at some point.

I’ve seen some authors go into financials (and I actually wrote it all out, but decided I was oversharing a bit).  I will give you a bit on my expenses, though:  I spent a grand total of $10 on marketing (not counting convention expenses, which I view more as research and networking, but some authors think of as marketing), gave away two (print) books (one to a cover artist, one to the cousin\IP attorney who helped me with my audiobook contract), and never ran a price discount on anything.  I did spend about $150-200 on swag, but most of that was for the keychain-sized plushie Fennec Foxes that I’m not going to be doing much with until Ravencon, at the earliest.  Given that I sometimes see authors report having spent thousands of dollars a year on marketing, often accompanied by deep discounts or even freebie giveaways, I think that’s notable.

So, a reasonably good year.  I hope to do better in 2018, but there you go.

Now, for my Marscon Schedule:

·         5pm   Fri      Room L        Costume in Fiction: Creating the Total Package

·         6pm   Fri      Large Auditorium   Opening Ceremonies

·         7pm   Fri      Room 5        Fantasy Draft League

·         10pm Fri      Room 7        Research, Point of View, and Filtering

·         10am-12pm Sat     Room 5        Writer’s Workshop

·         3pm   Sat     Room L        Questions to Ask When Creating a Fictional Culture

·         7pm   Sat     Room 8        Worldbuilding 201: Filling in the Details

·         8pm   Sat     Room 7        Mapping Your Novel

·         9pm   Sat     Room L        It Takes a Village Moving at 80% of the Speed of Light

·         1pm   Sun    Room 7        The Name Came First

 

Obviously, I’ll be too busy at the convention next weekend for a normal blog entry, though I may be able to write a (BRIEF) recap from the hotel, if I’m feeling up to it.  I should resume the “This Book Cannot Make Any Money” posts soon, however, starting with the second part of that darned book cover post.

This Book Cannot Make Any Money — An Unexpected Issue

So I’ve actually done the work needed to write the next several blogs in this series (part two of the cover and a bit on book design), but I’ve run into one unexpected difficulty.

The whole idea behind this book was to test out the KDP Print (beta) system, now that they’re offering print proofs. I had to work ahead of this blog series, because I wanted to get the proof back in time for Marscon and (at least with Createspace) shipping can take a long time.

So, I uploaded the files to KDP print and went to order a proof… and, uh, no print proofs are available. The whole program is in beta, and some options are available for some writers and not others, and I happen to NOT have the option to order a proof.

Uh… okay. I can still do some proofing for it (there is one flaw on the cover that the only online proofing tool they offer shows), but this is a set-back as far as this blog series is concerned. I’m sending in a request to be added to the beta program’s author proof copies, but I’ve got no idea if that’s even an option.

I’m still going to write those next two blogs, but it might wait until after Marscon. However, the print book might be released before I can finish this series, if that becomes my only option for getting a copy of it in time for the convention, and will certainly be released before the eBook version (a VERY unusual thing, for me).

As this series is now behind the production anyway, I’m going to be suspending it until I get back from Marscon. Next week, I’ll do a “year in review” post (which I probably should have done this week, but until earlier this evening I was still thinking I’d be working on this series for today’s blog), and then… well, I probably won’t have a blog that next week, as that’s Marscon weekend.

But, since I promised a cover reveal in this blog entry, here you go (keeping in mind there will be a few minor changes, including one or two corrections to the back-of-the-book blurb, before it goes to print…)

This Book Cannot Make Any Money — Cover Art Options

(Sorry for the delay in posting this article; it was ready to go, minus a couple links, on Sunday; website troubles made it so I couldn’t post until today).

After last week’s post, it should be no surprise to learn I’m not done with the edits for This Book Cannot Make Any Money. I probably won’t be done with that until the book is published.  With the methods mentioned last week, I hope to have the thing “fully” edited before my anticipated release date, but only just.  And, as has been shown by my past experience, even a “fully” edited manuscript might have errors which require post-publication edits.

The Merrimack Event, for example, had been edited multiple times over 13 years time.  More than half a dozen people touched that manuscript, making corrections.  I scoured every sentence to the best of my ability all the way up until the minute before I sent it to Kindle.  Yet there were over thirty errors found after publication I had to go back and fix… and I can tell you that most of them (including every then-than error, which is the thing I get the most nit-picked about in the reviews) were in the manuscript from its original rough draft, six people, thirteen years, and umpteen edits ago.

I’m not giving myself thirteen years to edit This Book Cannot Make Any Money.  I’m hoping to have this book out (the eBook version for certain, and hopefully at least a proof copy of the print version, as well) by my appearance at Marscon, all without encroaching on my writing time for the next Law of Swords book (which I also hope to have done by Marscon, but only to send it to my editor and not to publish).

Marscon is… *checks* less than a month away. *gulp* So I’d better get started on those OTHER things needed to publish this thing. With that in mind, lets talk about book covers.

Let’s start by exploring a no-muss, no fuss option for book covers that, yes, would even fit in my $0 budget. Namely, finding a FREE!  PRE-MADE! book cover from either a free (even) for commercial use, royalty and\or copyright-free stock art site (Pixabay, for example, has several fantastic-looking book covers available) or a professional cover artist who happens to have a few free (though this specific example offers paid-for “additions” like a Createspace-ready wrap version or certain types of marketing images featuring the cover).

This option can work for you… and if you have zero artistic talent and NO eye for art, maybe it’s the best option.  There are big disadvantages, however — you’re not able to ask for a free custom cover that actually fits your book (you might get lucky; for example, if your book features a robot detective (heh), a pre-made cover may feature a generic robot that would work for you), you might have to share your cover with other people (especially if you go with something like the Pixabay option), and — quite frankly — the cover you DO find may not fit the dimensions of your book, forcing you to either crop it, stretch it, or try something else.

Besides, I like the branding potential in always having a custom-illustrated cover for each book of mine.  I may not have any money, but I do have some freeware, and a clip-art site.

So, lets get started…

To begin with, you need to figure out what you’re capable of producing on your own.  Me?  I know the software, and I studied design, but I can’t DRAW anything fit for anywhere more public than a refrigerator.  I don’t expect to win any awards for a free cover I’m making for myself, I really hope nothing I make ends up on Lousybookcovers.com.

But, while I don’t like the idea of pulling someone else’s already completed book cover off of a stock art site, pulling ELEMENTS to make the artwork work from a stock-art site like Pixabay or a clip-art site like OpenClipArt.org should be fine.  And with software like GIMP and Inkscape, you can take those elements and blend them together into a cover that will work just fine for your book.

But what should those elements be?  Well, here are a few suggestions:

  • If you are not a skilled artist (which I am not), do not try to mix media.  It’s hard enough to manipulate single-media images to work (I don’t usually frequent Reddit, but it does have some good examples of what happens when you DON’T do it well); trying to get multiple images from different sources and media will increase the difficulty exponentially.
  • The same goes for art styles.  Mixing manga style artwork and classical renaissance artists could become a real disaster if you don’t know what you’re doing.  Even skilled artists sometimes fail to recognize problems in mixing styles.
  • A few authors use book covers which are designed around a single symbol (for example, this one).  This can work, as it does in the example, but only if it fits the story.  As a collection of disparate story fragments from different genre, that’s definitely not going to work with this book.
  • Oh, yeah, speaking of that — it is vitally important your cover fits both the genre of your book and your story.  Sure, maybe you’ve found a truly attention-grabbing picture of two monkeys swordfighting, but if you’re writing a romance novel that doesn’t have a single monkey in it (swordfighting or not), your audience is going to be annoyed at the bait and switch.  They’ll leave negative reviews (hurting your sales) and won’t buy from you again (hurting your career).

Okay, enough don’ts.  So, what am I going to do?

Well, let’s see.  In addition to the poetry (and I’m not going to market this thing to poetry readers), this collection features fragments from stories with elements of sword and sorcery fantasy, historical fiction set in the Roman era, classical Greek mythology, something that would have been set in the Rink of War universe, and a burger-flipping robot detective story.

Hm…

Well, I’ll see what I can do.  Cover reveal in my next blog, complete with an explanation of everything I did to put it together.  With Christmas and a few other events coming up, that may not be next week, but we’ll see.  I’ve got to hurry if I’m going to finish this series by Marscon.

This Book Cannot May Any Money — Editing Phase: When You Have No Resources

This post is a week and a day late, and it turns out I probably could have gotten it out last week, after all.  Ah, well.  On the plus side, the extra day is giving me a chance to make the following announcement:  The signatures have been signed and the contract is now fully executed!  I can now announce that The Merrimack Event will be turned into an audiobook by Tantor Media!  Tantor is a major player in the audiobook world, and I’m looking forward to working with them.  Audiobooks from Tantor will appear in all of the major (and some of the minor) audiobook outlets, including, yes, Audible, iTunes, Hoopla, and others.

But still, sorry about the delay in this post.  I’m trying hard not to let this project interfere with my next novel, which makes finding the time to work on this series a bit difficult at times.  It’s been even harder to manage that with this particular blog (I needed some solid, uninterrupted hours I could work on it for one editorial technique I’m presenting), but I finally managed to find enough time.

Now, if I wanted to talk about editing in general, I’d discuss all sorts of things.  For example, I’d want to cover the differences between developmental editing, copy editing, and proofreading (I did cover that in my Self-Publishing Roundtable).  I’d talk about what to look for in a good editor.  I’d probably talk about style guides, the differences between the Chicago Manual of Style, the AP Stylebook, Words Into Type, and Merriam-Webster’s Guide to Punctuation and Style, and I’d discuss why — if you are self-publishing — you might want to create a house style guide.

But that’s not the case with this series.  This series is covering the worst-case-scenario, the “you have no money, no (useful) friends, no ability to barter for anything, and almost no resources” type of self-publishing.  In this sort of situation, you probably don’t care about the distinctions between those different types of editing, you aren’t going to be employing any editors, and you can’t afford style guides of any variety.  You need to self-edit.

Self-editing is mostly about going back to make things internally consistent.  It’s about making your writing as good as you possibly can on your own.  It’s less about the technical, and more about getting things to flow.  And yet if you do it right, you can produce a product just as good as you can by hiring out the edits… but “doing it right” can be a bit hard to manage.

So, I now have enough content for “This Book Cannot Make Any Money” to declare the “writing” part of this book complete.  If I include the story fragment from the last blog in this series featuring the malfunctioning burger-flipping robot detective with the faux french accent, the book will be somewhere between 40-50k words long… which is VERY short for me, but is a reasonable novel length in some genres (such as certain types of romance novels, pulp westerns, and even some varieties of Mystery novel).  I don’t think I ever came up with a title for that piece, so (as a working title) we’ll call it the “Detective Hummer” story.  Time to edit!

But back up a moment, here. Usually, when writing, instead of stopping mid-story and re-writing, I note issues that I want to “fix” before I let anyone else see it, or things which I want my editor’s opinion on.  In the case of “Detective Hummer,” I had these notes:

  • This story wasn’t started with any form of plot or plan in mind; I started building one as I continued writing.  I need to be sure to check that there are no “plot-breaking” points in the story.  (This turned out to just be a story fragment, however, so that isn’t a problem).
  • Originally, I started describing Hummer to establish the ‘sci-fi’ elements for the story.  A malfunctioning robot working as a burger flipper was just supposed to be a set piece; it wasn’t supposed to become the main character.  I should see if I need to add more details about Hummer (and comparable details to the other burger-flipping bots) so that readers will have enough details to figure out what’s going on.
  • I rushed, a bit, through that scene in the police station.  I need to be sure I included enough elements to explain why Hummer was able to get into Evidence Lock-up without being stopped.  I also need to make sure, in a scene that by necessity had very little dialog, that there are enough details and things so you don’t violate the (often over-applied, but there is a kernel of wisdom in the saying) principle of “Show, don’t tell.”

Now, there are undoubtedly more issues than that, but those were the ones I remember coming up as I was writing.  Ideally, I write these down, and then set the story aside for a couple months so it goes “cold” for me.

But I don’t have that luxury with this piece — this is a demonstration piece, so I need to have this story fragment ready to go by the time my blog on Book Design comes out in a few weeks.  Rushing through edits only gives you bad editing, so I need to start editing NOW!

All right, time to check the editing budget.  I need to hire a good editor who works fast!  *glances at the budget*  Oh, right.  The budget is US$0.00.  Uh…

Well, that’s okay.  I’ve been able to negotiate a trade of services for editing, before (babysitting for editing in a couple cases; I nearly traded one of my mother’s quilts in exchange for a line edit of a book, once).  No problem!  Oh, wait, that takes a while to negotiate, and we’ve just established I don’t have any time.

Well, they’re never as good as a human editor, but there are some pieces of editing software like Hemingway… oh, wait, that costs money.   There’s Grammarly, too, and there’s a free version… that doesn’t include any of the elements that might make it more effective that LibreOffice’s native spelling and grammar checker.  To get the effective parts of that software, you need to pay for the premium version, and in the budget, we have… (checking again) $0.  *sigh*

Well, what about replacing the editor with a team of quality beta readers?  I know a number of successful writers who do that!  *checks rules of this blog series*  Oh, sigh.  I have to pretend I don’t have any friends or family who have any experience in this whole “writing” process, which eliminates the pool of people from whom I’d get beta readers.  *sigh*

Okay, pure self-editing it is!

Several years ago, I wanted to build my own houseboat, hoping I could use it as a writing getaway (I never finished this project, mind you, so don’t ask for pictures).  I recall reading a chapter in one boat-building book that was talking about boat motors.  It went into all of these details about what the ideal boat motor was (which included general advice like, look for a motor built in the 1980s or earlier, because the boat motors manufactured today aren’t built with proper marine-grade materials… or something like that).  At the end of the chapter, however, it started talking about options for if you COULDN’T find an appropriate boat motor.  It ended by saying (paraphrasing, because I don’t have access to that book now) that if necessary, there were ways to modify most lawnmower engines so that they could work as trawler motors.  While he didn’t recommend it, the author felt the need to tell you how to use this option because it was better to use a lawnmower-converted into-a-trawler-motor than to not build your boat for lack of a motor.

In that spirit, I DO NOT RECOMMEND pure self-editing.  It is the worst possible option that I think the self-publisher can take when it comes to editing… but I’d rather see a good book self-edited than not see the book at all (and self-editing is better than no editing).  So, I’m going to go through several options, and I would suggest you use several of these techniques if you find yourself stuck self-editing your own work.

Now, the first thing to do is just to re-read the story yourself, keeping those initial thoughts (mentioned above) in mind.  This is FAR better done if you actually have time to let the story get “cold” in your mind, first, but as I said before I don’t have time for that; I started self-editing almost the moment I ended the last blog, and I’m still a couple weeks late.  Still, you can catch some things, especially if you already have in mind what you’re looking for.  You will not catch everything, but you will catch a number of things, and your story fragment (or book, or whatever you’re editing) will be all the better for it.

Now, because people tend to see things different on a screen vs. in print, print out a copy of your story and read it again on paper, making notes on paper you’ll transcribe back to the computer later.  You’ll see things you missed the first read on the computer… (though the computer read could show you things you miss in print, too).  Again, pay special attention to those things you’d already identified as needing work when you were writing it.  You still won’t catch everything, but with each successive pass there will be fewer things you need to fix… (but a caution:  You may introduce new mistakes trying to fix the old if you aren’t careful, so BE CAREFUL).

Next, we’ll try the “reading backwards” method.  This is a technique that may help compensate for not having the time to let the story fragment get “cold.”

Now, you might be surprised to learn the technique does, in fact, work the way it sounds.  Sort of.  But this doesn’t mean you should be reading your sentences backwards, word for word.  If I had to read the whole story as “.hour an than more little in began Burger Bungalow at shift Hummer’s.  system transit public the to back hurry to had it then And” I would not only find no mistakes, I would soon be driving myself crazy.

No, in this case “Reading Backwards” means to read, paragraph by paragraph (some people do it sentence by sentence, but I think that’s a bit extreme), the manuscript in question.  This helps isolate each paragraph, and it reduces the “I meant to write it this way so I see it this way even if its wrong” effect that most self-editors encounter.  Or so I’m told — I’ve never noticed, one way or another, whether it helps with this.

But I do think it can help if you read your story this way, correcting whatever grammatical or typographic errors you find along the way, then think really hard about what the context was needed in order for the paragraph you just read makes sense.  Then scan back a few paragraphs and SEE if that context is there.  Maybe you did write the context down earlier in the story, but if it isn’t in the text recently enough to be fresh in your readers’ minds they are going to get lost, and that needs to be fixed.

Finally, I present two variations of a method for the final copy edit.  Both work the same, but there are slight differences.

The first is reading aloud to yourself.  You are checking both for grammar and flow with this one — if you stumble while reading (at least, if you stumble for reasons that can’t otherwise be explained by a sudden allergy attack, the phone ringing, your water heater exploding, that kind of thing), check to see if something is wrong with either the grammar or the flow and fix it until you can read it without stumbling.

This method catches most errors… if you can read your own work properly.  The problem is that most people (even reading aloud) read what they INTENDED to write, not what they actually wrote.  Letting your writing get cold helps with this, but it doesn’t completely fix it.

Which is why some people try a variant method:  Getting your computer’s pre-installed screen text reader to read it out loud for you (I tried using Narrator, which comes with Windows 2007; a horrid  voice which I can only get to work by copy-pasting the story into a text document, but its (barely) functional.  Most operating systems come with one, but if yours doesn’t there are plenty free versions for download — I haven’t tested them, however).

You will hear your text AS IT IS ACTUALLY WRITTEN, instead of as you intended to write it.  That is immensely valuable, and will make errors stand out dramatically.  When you DO find an error, pause the narrator and make the correction.

It is also time consuming, sometimes hard to understand thanks to the synthetic voice, and easy to lose focus on.  It’s great for short works, but if your book is, say, 150,000 words long (three of my novels have been that long or longer) you’re probably going to have to endure this for DAYS.   The computer narrator is accurate — more accurate than most human readers — but the synthetic monotone delivery will drive you crazy after a while.  Some people can stand it, others will start getting easily distracted, lose focus, or even fall asleep during the reading.

The synthetic monotone delivery has one more drawback, as well:  It will help you find grammatical errors, but it might obscure errors in the flow and tone of your delivery.  So, this method of editing isn’t flawless.

(Note:  It was originally my intention to have a full-on demonstration of the above technique which I’d share on this blog, but setting things up so I could record Windows Narrator reciting the Detective Hummer blog entry — as I’d planned — proved to be technically unfeasible.  Sorry about that; this was supposed to be the centerpiece of this blog post, and was partly why it was delayed until this week, but it just didn’t work).

Ideally, if you want to fully self-edit your work, you would apply a mixture of the above techniques, refining your story each round through.  Not all of these techniques will work for everyone, but a blend of the ones that do work for you will improve your book immensely.

So, how effective is all of this?  Well, I’m not applying all of these methods to this project — I can’t invest the time for it, and I think I can get something good enough using just a few of them.  I think I’ll combine the basic re-read technique with the reading backwards technique (paragraph-length) and, if I can find the time, one of the last two variants (In my attempts to record a sample of the narrator, I caught two minor mistakes, but geez that thing gives me a headache; I’ll probably stick to the self-read aloud version).  Is that enough?  Well, you’ve seen the before with my last blog post.  You’ll be able to judge the after for yourself when I complete all of this.

Before you can do that, though I need to publish this thing, and before that I need to do something about cover art.  Hm… I wonder what the topic of my next blog is supposed to be?

This Book Cannot Make Any Money — Editing Phase: The Before

I’d love to start this post off with a follow-up to last week’s post on my possible audiobook deal, but I still can’t give any more details.  Things are progressing behind the scenes, however, and I wouldn’t be surprised if I have some news by next weekend.

But enough about that.  I still need more content for “This Book Cannot Make Any Money,” and I also need a “before” example for my post on editing.  So let’s try to write a short story that’ll help fill things out (keep in mind I have no outline, no plot idea, done no research to prepare for it… at the time I’m typing this, I’m not even sure what genre I intend this story to be.  Furthermore, I’m usually terribly slow on short stories, and I only have a couple hours of time each day — usually when also eating dinner or sitting with family who INSIST on talking to me while I’m trying to get things done — to write it in.  And it’s completely unedited — that’s the whole point, after all — so… don’t expect much):

HRC-2057-BB, a.k.a. Humanoid Robotic Chef 2057-Bungalow Burger (known to most of the staff as “Hummer,” both because of its full name and because of a particular noise from a minor electrical short it had developed in its first year of operation) had a lot of unnecessary programming in it.

It was originally supposed to be labelled HRC-2-CdlC (or Human Robotic Check 2-Creme de la Creme), intended for a high-end gourmet restaurant, before said restaurant went bankrupt.  It was instead sent to one of the three thousand Bungalow Burger fast food restaurants.

Bungalow Burger had added its own food prep and customer service protocols to Hummer when it had been purchased, but had never bothered to delete Creme de la Creme’s food prep and customer service protocols.

That, combined with that very old short circuit, led to some very strange conversations with its human co-workers, sometimes.

“Zey want zer burgers well-done?  Sacré bleu!  Ze flavor of zis exzellent meat will be utterly ruined!”  Zzzzt!  Hummmm….  “The customer is always right.  Two well-done Bungalow Big Burgers, coming right up.”

“Belay that, Hummer,” that particular Bungalow Burger’s human supervisor, Jeffrey Davis, said.  “Give that order to Zipper.  We’ve got a visitor who needs to talk to you.”

Zzzzt!  Hummm….  “You zay we ‘ave a viziter?  Do ze want to zee ze master chef in action?”

Davis smacked Hummer in a particular spot on his frame, nearly dislodging the silly chef’s hat he’d been ordered to wear whenever cooking.  Zzzzt!  Hummm….  “Drop that horrible fake French accent.  The police officer who wants to talk with you won’t appreciate it.  He wants to talk to you about one of your orders from a few days ago.”

“Law Enforcement Compliance Protocols engaged,” Hummer said, its voice losing all of the personality pre-programmed into it.  “I will comply with any lawful orders.  Take me to the law enforcement official.”

“Huh.  That’s a new one,” Davis said, chuckling.  “I’m guessing that’s installed in case Federal inspectors come to check up the restaurant.  Well, this has nothing to do with inspections.  Come on.  He’s waiting by the maintenance hub.”

The kitchen, if you could call it that (Hummer had been programmed with the ability to form culinary opinions, including on the quality of the kitchen equipment; both of its personalities had frequently debated with its human controller whether a flat-top grill and a bank of deep fat fryers constituted an actual kitchen or not), opened in the back to a bank of charging stations for the robot chefs and janitors that made up the bulk of Bungalow Burgers’ staff.  It was also the place they all went for maintenance, and an informal meeting room between robots and human whenever something needed to be discussed out of hearing of the customers.

A meeting in that room, per every protocol that had been programmed into it since it was brought into Bungalow Burger, meant that Hummer was to remain silent until and unless asked questions.

Davis led Hummer into the room and stepped aside.  By law, the human owner of a robot (or, in this case, their licensed representative) was both permitted and required to be present when questioned by law enforcement, so he would be sitting through the entire interview.

“Wow,” the policeman said.  He wore a name-tag labeling him as Officer Kaaya.  “Your humanoid chefs look really… human.  More than I’m used to seeing from a fast food joint.”

Hummer would never pass for a human on the streets, with obvious hydraulics making up its ‘muscles’ and metallic mesh for a ‘skin,’ but he did have several cosmetic adaptions that made him look more human than the track-motored industrial robots like Zipper, like humanoid-style walking legs and a molded body frame.

“Most of ours aren’t,” Davis said.  “One of the ‘bots we started this restaurant with was damaged a couple years after the first batch came in — a maintenance tech dropped one of its circuit boards into one of the fryers.  This was a higher-end model, bought as a replacement at a discount.  It’s got all kinds of advantages over our other ‘bots — various sensors like infrared thermometers to check the food as its cooked, UV decontamination lights to help ‘clean’ his workspace, simulated emotions for customer service, and all sorts of high tech gizmos that are completely useless for a glorified burger flipper.  Fortunately it can do that, too.”

“So, he’s less likely than any of your other ‘bots to mess up an order, then?”

“I wouldn’t necessarily say that.  He sometimes forgets he’s a burger flipper, not a fine dining chef.”

Officer Kaaya raised an eyebrow at that.  “Okay, that’s odd… but it’s not why I’m here.  Robot HRC-2057-BB, you cooked a meal two weeks ago corresponding to this ticket, right?”

It took a moment for Hummer to recognize the faded characters on a photo of an old receipt.  Culinary-grade humanoid robots were required to store data on all orders for at least two weeks for the purpose of tracking down sources of food poisoning.  They were sorted by a tracking number, which Hummer was quickly able to interpret.

“Two Bungalow Burgers, medium rare, one onion rings, one fries, and two drinks,” Hummer recounted.  “Was there a problem with our service?”

Were Hummer’s video sensors not so heavily calibrated, it might have missed the hesitant tick of Kaaya’s nose at the question.  The body language interpretation subroutine programmed into Hummer’s old front-of-house protocol interpreted that as an indication he was about to either lie or misdirect to avoid answering.  That protocol was dormant at the moment, however.

“Not at all.  However, these two customers of yours were found murdered later that evening, so we’re trying to track everything down about their day that we can.”

“Murdered?” Davis exclaimed.  “You didn’t tell me this was a murder investigation.”

“I didn’t?  Oh, my apologies.”  Even Hummer could tell that was insincere.  It did not know why Kaaya would have failed to mention the crime to its supervisor, however.  “I would still like to know, HRC-2057-BB, if there was anything unusual you might have stored in your memory bank about this order.”

The Law Enforcement Compliance Protocols demanded that Hummer comply, so he searched his memory banks.  It had perfect recollection of cooking that particular meal, and it went through things from start to finish.

“No anomalies in my routine are detected,” Hummer said.

“Maybe not with your routine, but with the ingredients themselves?  In particular, the burger meat?”

Zzzzt!  Hummm….

“Oh, no,” Davis said, his head falling into his hands.

“Incroyable!  You dare inzult our ingredients?  Zis ees an outrage!  We have only ze finest prime grade meats available anywhere in zis restaurant!” Hummer exclaimed.

“No, we don’t,” Davis said, smacking a particular spot on Hummer’s torso.  Zzzzt!  Hummm….  “We use cheap, utility grade beef.  Hummer sometimes forgets we’re a fast food joint, and not the high-end fine dining restaurant it was originally programmed to service.”

(Author’s Note:  In terms of weird research, I had to look up the cheapest grade of meat acceptable for commercial use to write the above line, which led to several articles on interpreting USDA Beef grades.  Fortunately, that was a quick bit of research; let’s hope that this little tangent doesn’t make it impossible to finish this story in time)

Kaaya’s lips twitched.  “I think I’m starting to see why you were able to get this guy at a discount.”

“Actually, the short developed after we got him,” Davis said.  “Still not sure quite what’s causing it.  But his memory is still accurate enough to pass certification, and his cooking skills are… well, better than any of the burger flippers we’ve got, here.  I just wish I knew what the restaurant that we got him from was thinking when they gave him that ridiculous faux-french accent.”

Davis had not quite been accurate in his description of Hummer’s special abilities.  He did not have ‘simulated’ emotions, he had ‘synthetic’ emotions, though the mistake was understandable.  Robots with simulated emotions were designed to react in specific ’emotional’ ways (for example, arranging their facial features to resemble a smile or a frown) to specific external stimuli.

Synthetic emotions would start much the same way, though with a wider range of reactions to a significantly wider range of stimuli.  Then, using heuristic analysis of the situations which prompted those stimuli and an adaptive artificial intelligence, they would start applying those emotional reactions to different stimuli.

In other words, robots with synthetic emotions would learn emotions.

Hummer had been programmed to have a strong sense of pride in its cooking.  That pride in its cooking had also grown to be pride in itself, being the best cook in the restaurant by far.  Having its trusted supervisor describe its accent as “ridiculous” hit those heuristic pride emotions hard.

But after having slipped its Law Enforcement Compliance protocols once after an emotional reaction, Hummer had to be careful not to react again, instead choosing another seldom-used emotional state in its place:  Stoicism.

“So, what was wrong with our meat, Officer Kaaya?” Davis asked.

“The couple who died was poisoned with a neurotoxin similar to what’s found in box jellyfish, laced with some synthetic controlling agent I’ve never heard of that delayed any reaction to said neurotoxin for several hours.  Our coroner was able to determine, after investigating their stomach contents, that the bulk of the neurotoxins were concentrated in some burger meat they had ingested about two hours before they died.  From this receipt, we’re fairly confident that said burger meat came from your restaurant.”

“Has anyone else died?” Davis asked.

“We’d have shut you down long before now if they had,” Kaaya said.  “No, the poison must have been added to those specific burgers and no others.  And, given the amount of time needed for that poison to act, we figure it must have happened while the couple was here… meaning it was done by either the staff or another customer.  Tell me, Mr. Davis, how many human staff are employed at this Bungalow Burger?”

“Uh… just three of us.  The day shift manager, the maintenance tech, and me.  Labor costs are so high, nowadays, that even high-end robots like Hummer are cheaper than employing human staff… or so that’s what corporate says.  Things are automated enough that we don’t even need to be here every day.”

“And your shift starts at?”

“Four in the afternoon, usually,” Davis said, then gave a start.  “But it wasn’t us!  Like I said, we don’t need to be here every day; none of us were here in the restaurant when this couple came through.  We were four hours drive away.  The regional manager had a meeting of all of his franchisees, upstate.”

“And it’s unlikely your ‘bot, here, tried to kill them,” Kaaya said, shaking his head.  “We’d like to check your sales records for that day, see if there are any connections between your other customers and the victims.”

Letting out a deep breath, Davis nodded.  “Of course — we’re quite willing to co-operate in any way we can.”

Hummer knew that wasn’t corporate policy — Bungalow Burgers did not permit the release of customer information, even to law enforcement without a warrant — but the Law Enforcement Compliance Protocol (which were added to its programming at the builder’s discretion, not the restaurant’s) prevented it from saying anything.

But, underneath all the protocols dictating its outward behavior, Hummer’s synthetic emotional matrix was suggesting it take radical action.  It had pride in its food — even if all it made, in its current employment, was burgers — and the thought that someone had used its cooking to kill someone hurt that pride.

Hummer needed to do something.


Technically, there was no law or corporate policy requiring that robots remain in their owner’s establishment when not engaged in normal operations.  The one concern might be keeping batteries recharged, but most modern robots had batteries that would allow them to continue normal operations for up to three days between recharges.

However, there had never been any reason for Hummer — or any of Bungalow Burger’s other robots — to leave the restaurant, either.  Leaving the restaurant was not a behavior it had been programmed with, and so Hummer never left.

But Hummer had synthetic emotions.  In order to make synthetic emotions work, there had to be a mechanism for an emotional reaction to override normal behavior.  Usually, this was limited to something simple, such as laughing at something its heuristical analysis determined was ‘funny’ during a period in which its normal programming said it should do nothing, but the level of basic programming it was permitted to override increased the greater the emotional response.

Currently, Hummer’s emotions were so engaged that it could even override the valid orders of a law enforcement officer.  Hummer didn’t want to believe that its burgers were the murder weapon for a pair of humans.  It was also curious — could it even tell if they were?

Among the ‘various sensors’ Davis had explained Hummer was equipped with were tools to detect contaminants in the food, both biological and non-biological.  They were supposed to be sensitive enough that it could tell if there were enough traces of shellfish on a mixed-use cutting board to cause an allergic reaction if food was prepped on it.  Most of Bungalow Burger’s burger-flipper bots didn’t have any sensors at all, so there were no protocols requiring Hummer to use that sensor, but the pride in his work that his original programming demanded of him was such that he used those sensors, anyway — every time he cooked, he made sure there was no contamination in any food he prepared.

So, if the burgers were poisoned, Hummer should have detected it… right?

But perhaps the poison was something that its sensors wouldn’t detect.  Hummer did a search through all of the documentation available to it, but still could not tell if this ‘box jellyfish toxin’ would be registered by its contamination sensors.  The only way to be sure would be to experiment and see.  The problem was attempting that experiment required a sample of the toxin, which should not be available in the Bungalow Burger restaurant.

The police would have a sample of the poison in evidence lock-up at the police station, however, which was why, after the store had been closed up, Hummer had left the Bungalow Burger for the first time since its arrival, several years before.

Directions to the station were easy enough to find on the net, but walking on bipedal legs it would take hours to get there.  Fortunately, public transportation was still running, and it was no longer strange to see a humanoid robot using public transportation.

Of course, once it was at the police station, Hummer’s problems weren’t over.  Robots weren’t allowed inside the station, unescorted, without identification declaring they were in the employ of the police, and all robots were hard-coded with warnings not to take orders that would have them stealing or copying those identifications.

But Hummer hadn’t been ordered to do so — it was acting on its own, in response to his emotional prerogatives.  Hummer hadn’t known the term ‘loophole’ would ever be relevant to its programming, but it was capable of exploiting one when it needed to.

There was a public charging station for robots of all designs only a block away.  The statistical probabilities of finding a robot with the necessary identification to allow them entry into the Police station was highest at that charging station.

If Hummer could even comprehend the concept of ‘luck,’ he would think himself lucky to find a lone robot at the charging station bearing an identity transponder that would allow it access into the police station unsupervised.  All it took was disconnecting the other robot’s battery and towing it down a nearby alleyway where no-one might stumble across it.  Hummer then disconnected the transponder from the police robot and mounting it into its own frame.

And into the police station Hummer went.


Hummer was not doing a good job of ‘blending in’ as he made his way to the evidence lock-up.

“Since when have we had bipedal robots?”

“I’ve never seen that ‘bot before — is he new?”

“Does that ‘bot have a spatula in its holster instead of a service weapon?!”

Hummer could hear these and other questions, but at least no-one was curious enough to follow or investigate it.  Evidence lock-up was down several flights of stairs (Hummer was programmed to navigate stairs safely, but had never tested that feature of its bipedal legs until that day), in the basement, near the coroner’s offices and the morgue.

Of course, then Hummer had to figure out where the sample of its burger had been filed.  That first involved finding any case files featuring its restaurant (this wasn’t the first time a Bungalow Burger was involved in a crime, locally, but it did appear to be the first time it was involved in a murder), then figuring out how the evidence filing system worked.

Initially, Hummer tried to plug in to the network directly, but the firewalls wouldn’t let him in.  However, the in-station computers were set up to bypass those firewalls automatically, and it was easy for Hummer to get onto those computers and give himself access.

After that, it was a quick search, and there it was… locked up.  It wasn’t hard to bypass the security on the electronic lock, however, and finally Hummer had its sample.

The contamination probe was quickly inserted and… yep.  It could distinguish the poison from the original (now spoiled) meat… and from the stomach juices and other assorted tidbits which contaminated it.

There is was.  Absolute proof that it wasn’t Hummer’s cooking that killed the couple.  That should allow the satisfaction circuit to kick in, and it could resume its days at the Bungalow Burger without a problem.

Zzzzt!  Hummm….

“Hey, does someone smell something like wires burning?” a voice called from outside of evidence lock-up.

Fine dining chef persona engages or not, Hummer knew it needed to get out of there, and as quietly as possible.  After replacing the evidence and re-sealing the evidence locker well enough to hide the fact that a robot had ever been inside it, Hummer took off, back up the stairs and out of the police station.  Its mission was complete.

Heading back to the alleyway where Hummer had left the deactivated police robot, it contemplated the truth of that statement.  Yes, logically, the synthetic emotion of pride should be satisfied by having confirmed that the deaths weren’t its fault, and emotional subroutine ‘satisfaction’ should be engaged.  It was not engaging, however.  Along the way, ‘pride’ brought out another, rarely used emotion into the mix:  Curiosity.

The meat had not been contaminated when Hummer cooked it.  It was contaminated when the couple ate it… which, given the timeline mentioned by the coroner in the file, had to have been consumed before the couple were last seen in the Bungalow Burger that night.  Davis and the Bungalow Burger’s other humans had been away during that period of time, as well.  Officer Kaaya had been right — whoever had murdered the young couple had been a customer at Bungalow Burger, as well.  But which one?

It would take a real investigation to figure out which customer was the murderer, however, and Kaaya had already marked the file as ‘closed, unsolved.’  Apparently, following through to investigate each of those customers was too much for him.

“Sacré Bleu!  If zomeone iz to zolve zis crime, it must be me!”

Which meant Hummer need to learn how to be a detective.  Fortunately, there was a certain captive police robot down a certain alleyway which was available to learn methods and techniques of investigation from.

And then it had to hurry back to the public transit system.  Hummer’s shift at Bungalow Burger began in little more than an hour.


…And that’s it for this story fragment.  No, I am NOT continuing this, at least not any time soon; I’ve already got far too many things to do, first, and I’m not really equipped to write a mystery novel right now… not even one featuring a burger-flipping robot detective.  But I will be demonstrating self-editing techniques on it in my next blog post (probably the week after next, as next week looks pretty busy), and then the (edited) fragment will be published in “This Book Cannot Make Any Money.”

A Brief Intermission, As We Have Some News….

You were probably expecting the next “This Book Cannot Make Any Money” post, today, but I haven’t been able to work on it much this week. That’ll have to be pushed to next week.

The REASON I haven’t been able to work on it, however, is pretty big news, and if you’re here for ‘self-publishing tutorials,’ some of the background information might still be informative.

I was hoping to be able to be able to talk about this news in specifics when it came out, but a change of plans means I need to wait before I can mention a few details. In the meantime, however, here’s what’s been going on the past couple weeks:

Thanks, I’m guessing, to the success of The Merrimack Event, I was approached by a literary agent (this is USUALLY the wrong way around; if you are going this route, you usually should be approaching the agent, instead; however, a quick investigation proved this agency was legitimate and well respected). This agent mostly works with already published authors (often independent authors, though not always) to sell subsidiary right — namely, audiobook and foreign translation rights.

Now, I have long WANTED to produce an audiobook format for my books, but the process for self-publishers is more daunting and\or expensive and\or time consuming than I’ve been able to manage:

First, I understand you need to turn your manuscript into a ‘script’ for the narrator (I’ve never done this before, and I’m not entirely sure what’s involved), and then you need to have your narrator read, record, and edit their recording at a high enough quality to work as an audiobook.  Actually, there’s more to it than that, but the details aren’t all that relevant.  Suffice it to say, each of those things take time.

Now, you can hire someone to do all this for you. I got an estimate for that a few years ago (even before In Treachery Forged was released). From a NON-Union voice performer (union would have cost double), it would have cost me about $1650. Yikes!  There’s also a profit-sharing model, however — you give up half of your profits, and the narrator will handle the script and editing for you.  Probably will do some marketing, too, since they earn money from it as well.  But nowadays most of the good, competent narrators will only do that if you have a good enough reputation that they can be sure they’ll earn money from it (which often means, they won’t do it at all).

Now, I still Had A Plan for getting an audiobook off the ground.  I wasn’t about to spend thousands of dollars for an experiment in audio, and I wasn’t thrilled with the profit sharing model, but I could still work things out.  My local library has a (free to use!) recording studio as part of their “MILL” (Makers In Loudoun Libraries) Program.  My mother, though retired, had many years of training as a vocalist, and was studying to do this.  I’ve been trying to teach myself sound editing using open-source Audacity freeware.

So an audiobook format was coming… but it would take time, and one thing I never seem to have enough of, nowadays, is time.  MAYBE, as an experiment, I could have gotten the tiny little “To the Rink of War” out some time over the course of the next year, but it would take me years to get even one book out, this way.

And along comes this agent, offering to try and get me an audiobook deal.  So, after a little hesitation (I am against the very concept of literary agents, and one of the big reasons I decided to self-publish was that it meant I wouldn’t have to work with one, so I had this “am I really thinking about working with an AGENT?” moment), I opened negotiations with an agent, intending to have them work out an audiobook deal for me.

Things we going slowly, but steadily.  I was going over their contract and had found a few things that needed changing — no deal-breakers, just a few elements that I (or rather, my cousin the Intellectual Property lawyer) felt needed more clarity.  The agent was agreeable to making the amendments, once their own lawyers had a chance to look over them, and I was waiting to hear back from them.  And then a Big-Name Audiobook Publisher contacted me directly, wanting to buy the rights to “The Merrimack Event.”

I considered seeing if the agent was still interested in my other books, or in negotiating the foreign-translation rights, but… well, again, I really didn’t want to deal with agents to begin with.  So I told the agency I didn’t need their services, and (*gulp*) started direct negotiations with the audiobook publisher.

I’ve… I think the correct way of putting it is “agreed to terms, in principle” with the publisher; I still have to go over or sign the actual contract (so things could still fall apart, but let’s hope not), so I’m not going to say who that publisher is, yet, but just getting this sort of interest feels like an accomplishment.

And if you think the work that I had already done setting up for future audiobook production has been wasted… well, this will only be a one book deal (their initial offer was for two books, but I kept it to one for now).  They haven’t (yet) asked for the rights to the Law of Swords books, nor for The Kitsune Stratagem.  If this works out, I might see if I can sell the audiobook rights for those other books to this publisher, too, but there are no guarantees; I Had a Plan, but now it’s a back-up plan.

And there’s still “To the Rink of War.”  That one I might still do by myself, some time over the next year or so, regardless of what happens with this publisher.  We’ll see.

Oh — an a couple smaller pieces of news.  Despite its success, there have been a number of complaints about the “then-than” issue in The Merrimack Event.  I scoured the text and found five instances where then-than were mixed up (I do know the rule, but 13 years ago I had real trouble with it).

I made these corrections in the print edition before sending it out, but I hadn’t updated the e-book because I anticipated more corrections being needed.  I kept asking people to help me find specific examples of this error, because it sounds like a more serious problem than just the five instances I found, but so far I haven’t heard of any from anyone on the specifics.  So I finally uploaded the corrected file today.  It may take a couple days for Amazon to approve the files (the old file is still available for sale), but if the then-than issue REALLY bothers you, you may want to wait a few days before then collecting the update.  (This is such a minor correction you’ll probably have to do this manually, even if you have it set for automatic updates; see here for instructions)

Oh, one last thing:  I’ll be experimenting with a couple new plug-ins for this blog this week.  I’ve had spambots hitting the comment sections of all of my posts by the hundred, lately (which is why I have to approve your comments, if you’ve ever tried to comment on this blog, before. That’s been the only defense I’ve found which actually works); I’ve already downloaded and installed one plug-in that claims it will handle that problem non-intrusively, and it works so far, but I’m still testing it.  We’ll see if I need to try another one.

While I’m fussing around with the plug-ins, I might as well look to correct some of the other problems I’ve had with this blog.  For example, the button I used to have that allowed me to “justify” the text vanished, and that’s something I might actually need for my next post.  If possible, I’ll also look for some way to disable the horrid auto-hyphenation my theme insists I use.  Hopefully things will work the first time, but starting Tuesday there may be occasional (brief) outages as I try things out.

Next week, hopefully, I’ll have the next part of the “This Book Cannot Make Any Money” series, which will be a short story (or at least a fragment of a short story) that will be the “before” example to demonstrate editing techniques on.  And maybe I’ll be following up on some of today’s news… if things reach the point that I can safely mention the NAME of that audiobook publisher.

This Book Cannot Make Any Money — Getting Started: Content

In the first part of this series, I set up my computer with a bunch of free software for the production of a book without any budget. Today, I deal with the book’s content.

Now, if you’ve been following this blog long enough to remember the original post on this concept, you’ll recall that I planned the publication of “This Book Cannot Make Any Money” as a sort of tutorial (or, rather, to borrow a term from the Youtube gaming industry, a sort of “Let’s Play“) for self-publishing a book.

But I have more than one reason for pursuing this blog series:  I want something I can use to test out the KDP Print service, and I don’t want to use one of my more substantive books.  I need something new, something unconnected with my larger series, but I don’t have time to write an entirely new novel.

I do have time, however, to compile a bunch of material from my past writing can’t be used elsewhere. Things like poetry (much of it written in high school), a short story (nearly a short-short) that doesn’t fit with anything else I’ve ever written, fragments of other stories which I’ve rejected, myself, for one reason or another, etc.  Maybe even a few of my past (or future!) blog entries to add a little more to it.  Anything I can find, from my old material, that wouldn’t be a COMPLETE embarrassment to publish (though some of those bits of high school poetry are pushing it).

And many of them have one thing in common:  Someone (and in some cases, it was me), somewhere along the way, said these bits and pieces can’t make any money.

So why am I bothering with a blog on this book’s content, if the content is already taken care of?  Well, there’s more than one thing to mention, here.  For one, once you’re done writing your book, even before editing it, you need to evaluate the content and judge whether you’ve done a good enough job to actually publish your work.

Writers have a reputation for being neurotic.  No wonder!  We have to be egotistical enough to believe that our writing will interest others while still being humble enough to allow constructive criticism.  A lot of would-be professional writers lack the confidence to believe that what they’re writing is worth publishing, and so never get published.  A lot of writers grow an ego so large that they never accept criticism, and therefore produce low-quality work.  That sort of dichotomy is a veritable breeding ground for Imposter Syndrome.

When you’re self-publishing, it can get even worse.  You need to believe that your writing is good enough to sell, but you need to keep your ego in check enough to maintain quality control.  Now, I have occasionally had quality control issues (as all of the reviews for The Merrimack Event warning about my “then-than” issue might suggest; I’m working on that, people, but so far I’ve only found five.  From the reviews, I would think I had a lot more than that, so I’m still looking for more before uploading a revised version.  If you could point specific instances out for me instead of just spouting that I have “lots” of then-than errors for the hundredth time, I’d be grateful), but mostly of the mild and technical variety.

That sort of error should be found and cleaned up, preferably (sigh) before publication, but that’s not a substantive issue that would prevent the work from being published.  What you need to look for is:

  1.  Do you have a proper beginning, middle, and end?
  2.  Do you have enough story and character development to support the plot?
  3.  Do you have enough conflict to create dramatic tension?  (This is needed EVEN IN COMEDY, if you are producing comedy-with-plot)
  4.  Is your plot premised on bad research?  If so, are your readers likely to call you out on that?
  5.  Opposite problem:  Have you added so much conflict that your plot is becoming convoluted?  Must your characters rely solely on luck to succeed?

If you’re capable of giving truthful answers to the above questions, you can evaluate your own work to determine whether it’s acceptable for publication.  (If you can’t, you need to find someone who can to read your manuscripts for you)

All of these problems can be fixed; the question becomes how much time will it take to fix them.  If you figure you’ve got the time to fix it, go ahead and FIX the darned thing and then publish it.  If you figure the amount of time needed to fix it is more than its worth, you need to be able to reject your own work.

Much of the (non-poetic) material intended for “This Book Cannot Make Any Money” comes from my older work that I rejected for one or more of the reasons, above.  Which doesn’t meant the writing is horrible; just that it would take me far too long to revise the whole manuscript into something I could publish.

What I’m going to do is add the parts of each manuscript which aren’t going to require too much time to fix up, leaving the rest behind.

But, as I said, I had something else to cover in the content portion of this blog series:  Not all of the content has been compiled, yet.  There’s still more that has to be written.

Even with a collection of previously written material like this, I still need to add enough structure to turn it from a loose collection of random writings into, well, an actual book.  Some of the material is handwritten, and needs to be typed up.  Some of it will need to be cut and trimmed down to just the acceptable portions.

But to start with, I need to make the content fit into some sort of structure; that turns it from a random collection of my outtakes into an actual book.  That may include writing some (small) bits of content to make things fit.

For example, I’m going to need to split the poetry into three sections.  It naturally fits into two — High School poetry, and haiku.  So, reluctantly, I’m going to spend some of what is normally my blog-writing time over the next few weeks writing poetry.  Bleh.  Maybe I can make it something silly, like limericks.  If I can come up with limericks connected to my existing writing, that might even be fun.

Of course, that’s not all of the “extra” writing I need to do.  It may only be a couple paragraphs here or there, but I still need to write introductory pieces for each section.  And an introduction to the book itself, which may be lengthier.  And, well, there’s one other thing that I know hasn’t been written, yet (but we’ll cover that later).

So, even though the bulk of the content of “This Book Cannot Make Any Money” is already complete, I still need to fire up that LibreOffice suite I installed last week and get to typing.  Fortunately that’s pretty straightforward — no-one here needs me to demonstrate typing, do they?  (I’ll note that I would be a terrible typing tutor; while I don’t quite use a “hunt-and-peck” style of typing, I never learned touch typing, either.  My method works for me, but that’s after more than thirty years of experience in typing “wrong.”).  The only note I think needs to be made here, for those following along at home, is that I recommend saving any files created under the old .doc extension (often called the Word 97-2003 format); I’ve found it to be more universally compatible than the newer .docx format.  I’ve encountered the weirdest glitches when trying to work with a document copied and pasted from a .docx file.

Another thing:  A lot of self-published writers recommend using Microsoft Office’s styles extensively.  I can see why — much of the software designed to automatically convert your eBook from .doc (or .docx) to .epub uses elements from those styles to determine things like chapter separations and the like.  Since I’ll be building the .epub file manually, however, I won’t bother with that.  I stick to the default style and worry about formatting the book later.

There should be at least one more piece of content I need to write that hasn’t been mentioned yet, however:  I need something unedited to use as material for a before-and-after type demonstration for a future “This Book Cannot Make Any Money” post:  The Editing process.

So, next week should be… well, whatever I come up with for that unedited material (I’m still not sure what that’s going to be; it should be short, however —  a thousand words or so, at most).  Then we’ll talk about editing your work without having the budget to hire an editor.

As a note, I am hoping to have something to announce in the next few weeks (possibly, though not likely, as early as next weekend).  If I do make that announcement, I’ll be bumping that week’s blog forward a bit.  Again, this PROBABLY won’t bump next weekends blog, but I figured I’d mention the possibility in case it did.

This Book Cannot Possibly Make Any Money — Getting Started: Software

As was in my “Future Plans” post, I’m currently working on three writing projects simultaneously:  The third Law of Swords book, the Fennec Fox Press House Style Guide (which is typically added to only as issues come up) and — in those times when I NORMALLY work on this blog — a book entitled “This Book Cannot Make Any Money.”

Work on “This Book Cannot Make Any Money” won’t prevent this blog from being written, however.  Instead, it is intended as its own blog series, allowing me to go through the process of self-publishing a book in a tutorial form, or (since I intend to actually publish the end-product of this series) maybe more like a “lets play” (to borrow from the Gamer vernacular) of self-publishing a book for my blog readers.  This is my second try at this kind of project; the first time it got bogged down and eventually swallowed by the need to deal with other things, but this time I have a more developed plan for how to handle this.

So let’s begin.

Once you’ve completed your first draft, I recommend setting a budget based on your projected worst-case-scenario projection for sales. I should add the caveat that I mean REALISTIC (not optimistic, not pessimistic) worst-case scenario.  If you mishandle things, yes, it is possible to never sell a single copy of a book, but that’s a pessimistic projection.  From past performance, I would project the worst case scenario for any of my sci-fi\fantasy genre novels as two hundred fifty ebook sales.  At $4 profit per sale (when I set the eBook price at $5.99), that means I could set a budget of $1000 and realistically expect to break even in a worst-case scenario.

But this isn’t one of my genre novels; this is a collection of material that I’ve read, or for which I’ve been told, or which I’ve even decided for myself “Cannot Possibly Make Any Money.”  With that as the premise for this project, I (at least for purposes of this blog series) project earning… no money from this book.  So my total budget is zero dollars, of which I can spend zero dollars on software, zero dollars on the cover, zero dollars on the editing, zero dollars on the book design, and zero dollars on marketing.  Okay, that was easy!

The rest of this blog series is going to be on overcoming the obstacle of having zero budget when self-publishing; how, with no budget, I can acquire the necessary software, create an original cover, get the book edited, and (easiest of all, though you might not believe it) market that book without spending one penny.

I have, or can and have borrowed from my mother:

1.  Microsoft Office Suite 2007 (IIRC, it was bought at an extreme discount through a program my workplace at the time was offering)

2.  Adobe InDesign v.6 (received as a gift; the last non-cloud version of InDesign.  I recommend sinking the costs of any software you buy in a purchase rather than creating a recurring cost by leasing it over the cloud)

3.  Scrivener, purchased during one of their half-price sales.  (I think that, with NaNoWriMo just around the corner, that’s about to come up)

4.  Photoshop Elements v. 10 or v.15 (I may be purchasing Photoshop Elements 2018 soon; v.10 came packaged for free with other software, and v.15 is borrowed from my mother)

5.  Corel Draw (whatever the latest version is; it’s on my mothers computer)

…and probably a few other pieces of software I’ve bought for my writing business (or my mother has bought for her quilting business) that I’m not thinking of right now.

But, since we’re maintaining the rule that I have zero budget for this project, I’m going to pretend I haven’t bought ANY of this, yet, and find substitutes.

I do have to make certain concessions for the series as a whole before we begin:  I have a blog, access to the internet, etc.  My blog is on a paid-for site, but its using a resource that is free and can provide a free host if necessary (WordPress).  These things I could manage to access from my local library, but the library usually won’t allow you to install software on their computers.  They might, if they’re equipped well enough, have some similar software installed on their computers you can borrow, but you can’t count on that.

So, it is a bit of an assumption that — even with zero budget to produce your book — you own or have access to a computer on which you can access the internet and are permitted to install software.  If you don’t, well, I’m sorry, I’m not sure what to suggest.

So, with the limitations of zero budget (minus that concession), what options in the software department are there?

In place of Microsoft Office:  Anything that I would normally do with Microsoft Office, I will instead — for this project only — do with the LibreOffice suite.  Now, both Microsoft Office and LibreOffice are suites of tools, but to replace the ones I actually use for my publishing work, I only need LibreOffice Writer (for word processing, replacing Microsoft Word) and LibreOffice Base (simple database software replacing Microsoft Access.  I use Access to maintain some of my notes, such as character records, which need to be kept across books of a series; due to the nature of “This Book Cannot Possibly Make Any Money,” however, I won’t be using it for this book).  LibreOffice is available for free (it better be, or I’m already breaking the rules), and will work with Windows, Macintosh, or even Linux.  (You do need to download the correct version for your operating system, of course).

An alternative to LibreOffice is Apache OpenOffice.  LibreOffice was, in fact, originally OpenOffice, but (skipping one long, complex, boring story to explain why) they split up into two organizations developing similar suites of software from a common ancestor.  LibreOffice is generally considered to be the better option, containing much of the original design team, but some people still prefer OpenOffice

To replace InDesign I’ll choose Scribus.  Scribus is also free, open-source software designed specifically to do, well, the same things InDesign does.  It’s been going strong for many years, now, and most of the bugs are already worked out!  (A word of warning:  They recommend that you install ‘Ghostscript‘ first.  I made the mistake of not doing this the first time I installed Scribus, and it caused several problems with my initial set-up.

Outside of Scribus, the only other free software I can think of that works as a replacement for InDesign is… InDesign.  A couple years back, Adobe offered a free download of a no-longer-supported earlier version of InDesign (in fact, a whole suite of programs InDesign was part of a package of), version 2.0.  It’s a bit hard to track down, and requires a software key (they provided one for the public domain at the time) which may no longer be listed anywhere, but if you can find it you can get the entire Adobe CS software suite for free.  Because of its obscurity, however, I’ll stick with Scribus.  (Scribus has a few more modern features, anyway).  If you do have the budget to BUY this sort of software, however, I wouldn’t recommend the current, cloud-only version of InDesign; instead, I would go with QuarkXPress.  A bit expensive, but it has a lifetime license (and thus is a sunken cost).

Scrivener is an odd one.  It’s a word processor designed specifically for creating books, but the Windows version (which is the only one I have) is missing several key features available on the Mac version.  Scrivener has promised a new, updated version soon (Scrivener 3.0) which should EVENTUALLY bring them up to near identical versions, but even with that the Mac version will be the first release.

The long and the short of it is that I only use Scrivener for eBook building, after the book has been edited.  Since that’s all I use it for, I will compare it not with other word processors but rather with other eBook-making utilities.  I’m at least somewhat familiar with Sigil, so that’s what I’ll be using, but I understand Calibre is popularly thought to be more intuitive and will likely have more tutorials for its use.  Nevertheless, I’ll be using Sigil to produce an ePub, which I will then convert to .mobi for uploading to Amazon.  (Calibre can do the conversion itself; Since Sigil can’t — at least not as of the latest version I’ve downloaded — I’ll instead be using a simple tool called ePub to Mobi).

The graphics suites are all that we still need to worry about.  As a substitute for Photoshop I’ll be using the popular (though a bit tricky-to-use) GIMP.  As a substitute for Corel Draw, I’ll try Inkscape (an open-source vector-based graphics utility I first saw in a package of “best open-sourced software” back in 2009.  I’ve often installed it but never used it, so this will be a bit of an adventure).  Not sure if I’ll need both of these programs, but at least I’m set up if I do.

Okay, software is taken care of.  Next time on “This Book Cannot Possibly Make Any Money,” I’ll start using these bits of software to ‘create’ the book’s content (which is already written… or is it?).  See you then.

The Print Edition is OUT!

I had a blog all written out for this weekend (the first post in the revamped “This Book Cannot Make Any Money” series), but I’m bumping that to next weekend. Why?

The print edition for The Merrimack Event is FINALLY out!

This closes the books on the most difficult book release of my career (so far, but hopefully that record will last for a long, long time). It’s been a rewarding one, but I am so relieved that its finally complete that I don’t know what to do.

Well, not complete. Amazon still hasn’t associated the print edition with the eBook edition. This SHOULDN’T be a difficult issue to resolve — Amazon needed a push to do that with two of my three previous books, too, and it was a simple (though hardly “quick”) fix — but with all the issues The Merrimack Event has had in its release, I’m crossing my fingers while knocking on wood that nothing happens to complicate the process.

In other news, I’ve finally resumed work on the third book in the Law of Swords series. Well, I’ve tried to — between various “real life” events (nothing serious; as an example, I had to make an unexpected trip out to get a watch battery replaced. No big deal, but it means a special trip out and time taken out of my work day) I’ve found myself working on this blog (well, what will turn out to be next week’s post) more than I have on the book.

Hopefully that’s not a sign of things to come.  At any rate, that’s it for this week.

Edit:  Contents closed to reduce spam attempts.