Thursday, 16 August 2007
|
Why write a tech book?
posted at
04:52 PM
|
trackback
|
|
link
You don't write a technical book for the money. Some books are successful enough to generate a respectable royalty. For most books, tho, if you divide the pay by the hours you put into writing a book, it's not usually an impressive number.
So why do it? Well, one reason is so you can steer your friends into the right book aisle at B&N and say "Hey, look at that!" (You can do the same with your mom, but she'll probably never be able to tell her own friends what your book is about.)
That thrill wears off, tho. Andrew Savikas summarizes beautifully a more cogent reason, and a reason to find the right publisher for your book. Writing a book, he says, is ...[...] for a lot of authors just a promotional tool to build demand for speaking and consulting (something tech authors have been doing for a long time). When viewed through that lens, finding the right publisher becomes more important, not less.
Authors have learned that they don't work with a publisher to create and sell a book -- they work with a publisher to build and promote a brand. Publishers who view the relationship in the same way, and provide tools and opportunities for authors to sell themselves as much as their books, will have little trouble attracting top talent.
[categories]
writing
|