short story on Kindle

My short story Opening the Eye is now on Amazon as a $0.99 ebook. This story first appeared in Horror Library vol 2.

This story is in that hazy ground between urban fantasy and horror. If you enjoy that sort of thing, please check it out. If you like it, please leave a review. It won’t show up in most Amazon searches unless there’s a certain number of reviews.

If you don’t enjoy that sort of story, don’t read it. If you’re related to me, you don’t want to read this one. Trust me.

I’m not going to turn this blog into a plea for people to read these things, but I will briefly mention when they’re available in new places, such as the Nook or the Apple bookstore.

This is an experiment. (I have experimental conditions and everything!) But more on that later this week.

publishers versus self-publishing

People keep asking me why I use a publisher when self-publishing has become more and more possible over the last few years. Today, 38% of Amazon’s top 100 titles are self-published. Authors with a long track record in publishing, like Bob Mayer and Joe Konrath, extol the advantages of self-publishing your work rather than going through a publisher. Dean Wesley Smith and Kristine Kathryn Rusch, authors with decades of respectable mainstream publishing behind them, make solid business cases for skipping publishers and selling directly to your audience.

These authors write fiction. How well do their arguments apply to non-fiction? Well enough, if you want to do the work or pay someone to do the work. Here’s what you must do to produce a professional-quality nonfiction book. (If you want to produce an amateur, feeble book, you can skip any or all of these.)

  • Tech review: Someone who knows the subject has to review your work. Even if you crowdsource an initial tech review, as I’ve done for my BSD books, you still need an acknowledged subject matter expert to double-check your work. Your technical reviewer will expect paying. Most publishers pay a couple grand for tech review, or offer a cut of the royalties.
  • Editing: An editor is not a proofreader. An editor helps transform your manuscript from the disjointed babblings of a subject matter expert into something that can be understood by your reader. You can expect to pay $1-2/page for a decent technical editor.
  • Copyediting/proofreader: This is your proofreader. $1-2/page, again.
  • Layout: A good book is invisible. The layout disappears from the reader’s perceptions, leaving only a stream of words flowing from the book in the reader’s brain. I have never met a technical person who really had this skill. There are people who will format your manuscript for publishing on Kindle, Smashwords, and other ebook retailers, as well as paper formats for CreateSpace or Lightning Source. This runs anywhere from $100 for a novel up to $500 or more for complicated technical documents.
  • Publicity: Different publishers offer different levels of publicity. My publisher, the inimitable No Starch Press, publicizes every book heavily, in every appropriate channel. Other publishers just put new books in the catalog and let the author hope. Publicity can cost as much as you want to spend.
  • Graphics: Most authors can’t draw, even if they think they can. Publishers usually have internal artists recreate author art. You need to make sure that your own art is adequate.
  • Management: Your book has a project manager who keeps track of all the disparate threads of producing your book. If you self-publish, that project manager is you.

    Overall, you can expect to spend a few thousand dollars self-publishing a professional-quality book, and a fair amount of extra time. Miss any step, handle any step less than perfectly, and your book will suffer.

    What do you miss out on when you self-publish?

  • Translations: Advances for foreign language rights range from $1000-$2000, plus royalties if and when the advance is earned out. You will not be able to pursue translation rights — you don’t have the contacts or the contract expertise.
  • Bookstores: You will not see your self-published book at Barnes & Noble. End of discussion.
  • Competence: Nonfiction publishers are experts at helping non-authors produce good, readable books. A good publisher will help you make your book the best it can be. If you’re not a writer, anything you self-publish will read poorly, no matter how much outside help you have. If you think you’re a writer, but you’ve never worked with a publisher, you have a lot to learn.
  • Cameraderie: You’re a team with your publisher. They will work with you. You’ll make friends. Everybody wants the book to succeed, and believes that the book can succeed. It’s hard to put a price tag on that.

    Nonfiction authors have some potential advantages, however. If you have a truly unique book, with no competition, you can do well self-publishing. If you want to compete in an existing, well-established topic, however, you’ll have a much harder slog. I wouldn’t recommend self-publishing a FreeBSD book, for example.

    How do these affect me?

    I want an editor, tech editor, and copyeditor who are interested in producing the best book possible. An editor I hire is not going to tell me “Wow, this book is horrible and pointless.” An editor who works for my publisher will voice his concerns to the publisher, and the publisher will intervene as necessary. I can honestly say that none of my publishers have ever had to have this meeting with me, but I want them to have the freedom to do so.

    Publicity? I have enough trouble with the little publicity I do now. I resisted blogging, Facebook, and Twitter for years. The less I talk to people, the more people like me. (It’s not that I’m an obnoxious person, but a little bit of me goes a long way.) An outside publicity person is an excellent idea. I try to give my publisher’s publicity person everything he asks for, follow his suggestions, and get out of his way.

    Bookstores: I don’t see my books in stores in Detroit, but I know that some people buy my books in bookstores. It seems that Amazon owns my publishing career.

    Graphics: I am an author, not an artist. Producing the graphics for PGP & GPG took as long as writing the manuscript itself. I need outside help with art.

    I don’t want to do all this for my technology books. The tech publishing industry is in much better shape than the fiction industry, and I’m confident that I will be able to find a home for my nonfiction. I might self-publish my fiction some day, just to escape the submission treadmill. But I haven’t given up on that mainstream success… yet.

  • NYCBSDCon Video

    The video of my NYCBSDCon 2010 talk, BSD Needs Books, is now available at http://blip.tv/file/4844882. At the moment, it’s the top link on BSD TV.

    This is the first time I’ve seen my own presentation, at any conference. I’ve always suspected that I look daft in front of an audience. It turns out that the slim chance I was wrong was a nice thing to have.

    next tech book outline

    My big project for the holidays was completing an outline for the next tech book.  I’m glad to say that the outline is done. I can’t yet give the title, but I can say:

    • It’s huge:  29 chapters in a 25-page outline.
    • I have a tech editor, a respected figure in the relevant community.  He’s currently reviewing the outline.
    • No Starch Press wants it.
    • I expect to spend a year writing it, so I would expect a release in early 2012.

    The book’s length is a concern. I want to write books small enough for me to hold comfortably in the bathtub. I’m a big guy, but a 29-chapter tech book pushes that limit.  I might trim some content, or cover some parts in less detail, to meet that goal.

    I don’t announce book titles far in advance, due to problems that’s caused me in the past.  (Some day I’ll write up that story, but not today.)  I expect that I’ll be far enough along in a few months to announce the title, so:  I’ll announce it during my presentation at BSDCan 2011.  (And now that I’ve made a public commitment to that date, I’ll have to get cracking!)

    I have achieved pole position

    I sold my short story Wednesday’s Seagulls to short-story.me a few months ago. They released that story as part of their second “best of” anthology collection in November. I’ve wanted to check it out, but the holidays and my efforts to outline another nonfiction book interfered.

    The order of stories within a volume takes more thought than most people realize. Most of the big-name editors have their own occult ordering methods, but there’s a few general rules.  The first story in the anthology is the story that, in the editor’s opinion, is most likely to hook the reader and compel them to read further. The last story is the one that, in the editor’s opinion, is most likely to leave the reader with the a good impression of the anthology.  While I’m proud of my previous antho sales, my work therein is buried in the comfortable middle.

    Wednesday’s Seagulls is the first story in this anthology.  I have been awarded pole position.  Merry Christmas to me!  You can get the anthology in print and on Kindle.

    I really must learn to write faster.  Maybe if I give up eating and sleeping…

    TechChannel interview published

    The video interview I did last month is now available on-line.  It’s about NetFlow, and is based on the Network Flow Analysis book.

    I can’t bring myself to watch it.

    (Two posts in one day.  This can’t be good.)

    UPDATE: No, it’s not good. Apparently, WordPress doesn’t show the links on the front page, even though it shows the complete article. You must click to the individual article to see the link to the interview. I’m sure there’s a perfectly good reason WP behaves this way, but it still feels bogus.

    another brush with glory

    One of my friends, SF writer Colin Harvey, just had his second mass market paperback hit the shelves.  Damage Time is a post-peak-oil police novel set in New York City.  The chilling bit is how he successfully combines the ideas of memory extraction with social networking.  And murder, of course.  (Where you have police, you get murder. Without police, people just get killed.)

    If you look in the acknowledgments, you’ll find the line “and Michael Lucas hunted cliches relentlessly…”  That’s me.  I’ve got my name on another book!  Well, okay, in another book.  Close enough.  Sort of.  And apparently I’m relentless, too.  Maybe that’ll encourage me to get out of bed in the morning.

    If you read SF, I highly recommend Damage Time.  Exciting, gritty, stolen memories, appalling and believable.

    NYCBSDCon is at our throats

    NYCBSDCon is this next Friday, Saturday, and Sunday, 12-14 November 2010.  If you’re anywhere near NYC, you need to attend.  If you’re not anywhere near NYC, you need to get to somewhere near NYC, and then attend.

    I’ll be speaking on Sunday.  This talk could be subtitled “How I Reduce Suckage in My Books.”  Writing decent tech books is a skill you can learn.  I can honestly say that the slides are done, but in truth is that I still need to reduce slide suckage.  I’ll be reducing suckage up until the moment I present.

    asking me for opinions on your writing

    Occasionally someone will ask me to read their work and either comment or tell them where they should submit it. Some of these folks I know, some I don’t. It’s flattering to be asked, but my answer is: no.  I could describe my reasoning in great detail, but the inimitable John Scalzi has a far better article than I do.

    On rare occasion, I make the mistake of saying “yes, I’ll look at your work.”  One of the following will result.

    1. I will give you my honest opinion of your first page.  You will respond by dedicating the rest of your life to making me miserable.
    2. I will give you the metaphorical equivalent of a pat on the head.
    3. I will say you lack the fire.
    4. I will tell you that publishers require sentence to have both a noun and a verb, and that you cannot use emoticons in published work.
    5. I will “accidentally” erase your manuscript, your email, and my hard drive, so that I can honestly claim that losing your work was part of a much larger accident.
    6. I will put off looking at your work in favor of paying work or spending time with my family.  I will feel increasingly guilty about this.  I will begin avoiding you.  The importance and difficulty of evaluating your work will grow in my mind until it assumes unbearable proportions.  I will take a week out of my life to evaluate your work thoroughly.  By this time you will have married your third spouse, adopted four feral children and a platypus, and moved to Aruba to fulfill your lifelong dream of being a beachcomber.

    Note that none of these result in you getting anything you want.

    If you really want to get my opinion, I suggest you either pick a response you like, or roll a die.