Title Image

Don Xml's Grok This

The home of Don Demsak
Welcome to Don Xml's Grok This Sign in | Help
in Search

This Blog

Syndication

Site Sponsors

DonXml's All Things Techie

Why Shouldn’t Tech Authors Self-Publish? Part 2

Back in May, 2004 I wrote the blog post, Why Shouldn’t Authors Self-Publish? and like most decent posts, it garnered some attention, and then slowly faded into oblivion, only to be found by people searching about self-publishing.  Over the holiday weekend someone added it to the social bookmarking site (actually, I never heard of this particular social bookmarking site before, and found it thru my referrals), and it has really taken a life of its own.  It isn’t anywhere near the traffic from being slashdotted, but still very noticeable when looking at my traffic stats.

The post takes you thru self-publishing a factious 600 page tech book, printed using print on demand and sold thru Amazon, and compares the potential income compared to what a publishing company would pay you (I used APress in this example, since their rates are available on their site).

If you haven’t checked out the original post recently, you may want to take a look again, since there are a bunch of new comments, even Tim O’Rielly chimed in on a comment.  Here are a couple of my favorite comments:

  • I know of a very good reason for authors to not publish their own work themselves: they don't get help with typesetting, proofreading, layout, peer review, and so on. This article is an example of this problem, as it is riddled with bad writing and blatant errors.
  • I've made more on my Amazon link to the book (via Amazon Associates) than I have made on the actual sales ($0) of the book.
  • There's one critical dimension that I think is overlooked, though. Buying from reputable publishing firms - Addison Wesley, for instance - provides for a level of trust between the seller and buyer.
  • This isn't a point in favor of publishers, BTW. Most editors that work for publishers are free-lance and would just as happily take your money as a publisher's. You can probably get tech reviewing done by local user group buddies or co-workers. The point is: If you're going to charge the same as the big publishers, readers are going to expect the same quality -- better, really, if they realize that you're getting more of they money
  • The primary objection to POD is, and has always been, simple stigma. POD is still equated with vanity publishing in the minds of agents, editors, and the general public. Traditional publishing, by contrast, is considered the end product of survival of the fittest: only the best books get through.

The costs I seemed to have missed in my original post were the costs of proofreaders, tech reviewers, typesetting, and indexing.  Each one of these items can usually be done by the same folks that the publishers use, since they are usually freelancers.  Only the author can determine if their particular book requires these services (and for most tech authors, they probably do need them).

Technorati tags

Published Wednesday, December 28, 2005 7:24 AM by donxml
Filed under: , ,

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

Sahil Malik said:

I know this is an f**ing old blogpost, but the comment is new. Publishing with a well established name, or self-publishing - both mean very low $ anyway. So I might as well, stick with a better name, get project management, decent reviewers, pdf experts, english experts, and basically - all the *** that I'd rather not do. The little bit extra money you will make, will very easily be eaten up by all this extra hassle. The bigger Q is, in a blogolicious world, why publish anyway?
February 8, 2007 1:37 PM

Leave a Comment

(required) 
(optional)
(required) 
Submit

About donxml

I’m an independent consultant, specializing in .Net solutions architecture, based out of New Jersey who also doubles as an evangelist for XML, Domain Driven Design, enterprise architecture and .Net. I do not work for Microsoft, the W3C or any other big company that you may know of (at least not yet). I’ve been an indie for over ten years, and although I’ve been tempted a couple times to take a job with companies like Microsoft, I’ve haven’t found something better than my current situation. I work mostly with the large pharmaceuticals that are based here in New Jersey, and usually find myself on long term contracts. Definitely not the prototypical indie consultant, but it lets me dedicate time to my non-income generating activities like the developer community stuff, plus financing open source projects like XPathmania and MVP-XML. If you would like to talk to me about doing some contract work, just contact me via the contact page. My rates vary widely, depending on lots of different variables, but mostly distance from Jersey, and type of work. Plus, I’ve been known to donate some of my code for various projects.
Powered by Community Server, by Telligent Systems