Confessions of a Self-Published Technical Writer
Now, one thing you should know about me is that I self-publish.
There are huge drawbacks to that, and a few key
benefits, and for me, I think the benefits tend to outweigh the
drawbacks.
The Drawbacks of Self-Publishing
The drawbacks? Well, my distribution channel is pretty small,
and I don't sell a whole whack of books. That makes my per-unit
cost pretty high, and as a result, my books cost a bit more than
other technical books on the market. I always try to sell them directly
through amazon.com as an associate seller with a big discount, but the list price I've gotta charge on Amazon to cover
costs (they take 55%) is pretty high. That really sucks.
The other drawback is that I don't have a whole list of editors
and proofreaders to help me edit the final copy. My friends help
me out, that's for sure, and I always edit and reproof my books
three or four times before they go to press, but the fact is, there
are always typos and other little errors that make it into print.
I always find the typos that make it into the prose quite
embarrassing, so if you catch any, please shoot me an email either through the JavaRanch Big Moose Saloon, or at:
typos ahyt cameronmckenzie dahwt com -- you can figure that out, right?
(I have to write my email that way, or the spambots will start inundating me with junk)
Benefits of Self-Publishing
You see, the flip-side of self-publishing
is the fact that I can quickly make changes to my master manuscript,
so if I find a typo or grammatical error, I can fix it and have the
correct content into circulation within a month - you'll simply never
see that type of responsiveness with the big publishers.
Furthermore, I can add or update the content in my books
rather quickly, too. If there's something you'd like to see added
or changed, again, I can make that happen. My ultimate goal is
to have some really great technical books on the market. If you
can help me make that happen, I'd really appreciate it, and so
would everyone else that reads my books in the future.
Now as I said, I've never released a book that was completely free of
typographical errors or grammatical mistakes, although I do try.
Of course, errors in the prose is one thing, but errors in the actual
code in this book is totally another matter. My guarantee to you
is that every line of code in this book is error free, and will
compile as it is written, and I'm willing to put my money where
my mouth is on that point.
The $100 Error Free Code Challenge
I really have no tolerance for
programming books that contain errors in their code. I mean, how can
someone learn if what they are being taught is wrong? There are a lot
of reasons why technical books get riddled with code errors, but I
don't find any of those excuses acceptable.
A Promise to You
My promise to you is that if you find a
syntax error in my Java code, anywhere in the book, from the preamble
onward, and you are the first person to inform me of it, I will write
you a check for one hundred American dollars.
And on top of that, I'll add your name in a special thank
you section of the next printing of the book, and say all sorts of
great things about you. That's how confident I am that there are no
code errors in this book.
Your Input is Extremely Important to Me
And to be honest, if there is something in here that's wrong,
and you find it, I'll be more than happy to pay. That's my commitment
to quality, and to you, the reader. If you can help me improve the
quality of this book, I will more than appreciate your help!
Send any errata to: jpaerrata aht
cameronmckenzie dawht calm
|