So you want to be a textbook author?
by Esther Schindler
This is a really delightful, laugh out loud description of the process. As I've signed a book contract for the 13th title to carry my name (let's not mention that I'm already behind schedule), I'm reminded that the advice applies equally well to the tech book writing market.
Sadly, many authors with contracts do not finish their books. Why? Because reviewers mug them. In comfortable anonymity, reviewers announce they liked everything about your book except its main premise. Or, interspersed with sensible praise, they make suggestions that are the equivalent of putting spandex shorts on Michelangelo's David or grafting a third arm to his back. Rule #5: Reviewers always suggest 50 pages of new ideas and insist the book be shorter. Rule #6: What one reviewer loves best another hates best. My advice for authors: Rule #7: Accept reviews with stoic dispassion and gratitude. Rule #8: Smash your hand only into soft objects.
Comments
So true in many cases. Luckily, my experience was a little bit different.
When the publisher is working on a 6 to 8 month cycle (the time span between when you start writing and when they actually start to prepare the text for publication), there's plenty of time for them to send it out to other people (some of whom you may not know at all, some of whom may actually have no background or expertise in your subject area) for "review".
This is normal and expected: your editor doesn't know what you're writing about, and they want to make sure you don't make the publishing company look stupid by printing your book. So they get CYA backup.
In my case, I lucked out. They let me pick my own "Tech Editor", someone to fact-check my technical content, proofread the code samples, and so on. The big benefit, however, came from the fact that the publisher promised me in September that the book would be available to sell at Lotusphere the following January. There was no TIME to get a bunch of bozos to review it.
Of course it was stressful for me as well, I had to get it all done in a big hurry. But it was worth it.
Well, I have done two books - and after both books I have sworn I won't do another (I am still in that mode from the last one). For geeky tech books, I can add a few others:
** You don't do books for the money; you do them for the visibility. Don't ever expect to make a killing from a tech book.
** The noteriety you get from the first book is as good as it gets; subsequent books do not add to your noteriety, just like buying that second lottery ticket doesn't effectively increase your chance of winning (i.e. 2 chances in 47 billion is about the same as 1 chance in 47 billion). The exception to this is if you wait a LONG time between books. I waited 6 years between books, and I am getting the same "bump" in noteriety that I did with the first one.
** Don't let the fame (and infamy) get to you. You're not as good as your fans think, and your not as bad as your critics think. And even though people think you're an expert, remember that there are thousands of others who could do what you did, but just haven't done so because they weren't as desparate (or stupid, or whatever) as you.
** Once you get the book, don't be afraid to ask for more extras for promotion. Most of the time the publisher will help you out.
** Always give a copy of your book to your mother - and write something nice to her in it.
** The book you give to your mom is the only one you're allowed to autograph without being asked first. Except for that one, don't autograph any books you give away unless the recipient asks you to; to do otherwise is arrogant.
Those are what I can think of off the top of my head. Like Bob, I think it was worth it, overall.
Thanks for sharing that article, Volker.
Err, thanks for letting ESTHER share, Volker ;)
I've been an author, co-author, and tech editor on a bunch of books. The last one (before this) was in 1996, when I was so exhausted from the effort that I said I'd had enough. Obviously, it's been long enough to have forgotten the pain -- and I've had an unaccountable urge to write something for mere mortals rather than for techies. So once more into the breach --
Fortunately, early in my book writing career, a more experienced author gave me the wise advice, "Live on the advance. Go to Hawaii on the royalties." Only one of all those books (Teach Yourself REXX in 21 Days) has paid out its advance.
As far as dealing with publishers goes: it really does vary by publisher. And having a book agent makes a difference. Like many, I started out with MacMillan -- SAMS and New Riders (which are now, with industry reshuffling, part of Pearson). Then I went to AP Professional. Then to Coriolis. The first were too intrusive, with development editors and tech editors and copy editors (though in truth they taught me a lot about writing effectively). AP Professional tentatively asked me, a month before the book was due, if it'd be ready on time. No tech editing, barely a copy edit. (That scared the poop out of me.) Coriolis, like Goldilocks discovered, was Just Right. Enough queries to help me find errors, not so much that they forgot it was MY book.
The first few books were ego boosts. This one is... money. I've been writing so many 300-page industry analysis reports, in the last year, that I figured I might as well write a book and get a hard cover on it.
Personally, I find autographing among the most personally embarrassing experiences. Who ME? Why would you want ME to sign this? And I never know what to inscribe, so it's usually just my name. I'm not in the lucky position of one of the well known Dummies authors of my acquaintences, who confided to me once that his typical autograph says, "YOU're no dummy!"
Rock, I am really proud to have Esther with us here. And a little plug for her: If you look for a technical author or editor, look no further. :-)
Esther - that is fascinating. I have never had an agent, but if I were to make this at least semi-regular I probably would. I relied on my first co-author and writing mentor, Bill Kreisle, to give me tips for negotiating my subsequent contracts. Incidentally, Esther, Bill and I did a "Teach Yourself..." book as well, for MIS Press - "Teach Yourself...LotusScript for Notes/Domino 4.6".
As for signatures - I am TOTALLY in agreement with you. "Why do you want my autograph? I'm just a geek like you!" But I do oblige when asked. I typically write "Best Wishes" and my sig, but sometimes people ask me to personalize it, so I have written things like, "Well, I KNOW you don't need this book - heck, you could have written it! Make sure someone who needs this reads it, because it is quite apparent that you don't. Thanks for your support!" This usually gets a good laugh, and they seem to really appreciate it.
Volker, if I ever do decide to jump back into the fray, I will definitely keep Esther in mind - I already like her style ;)
I recently read this article http://www.ramblingrose.com/ComputerBooks.htm by Rose Kelleher which I thought was interesting...
