Live data from Hacker News

The Economics of Writing a Technical Book

medium.com

51–60 of 151 posts

Re: The Economics of Writing a Technical Book

#51

My experience is that the self-publishing business is a _business_ that generates money from publishing and marketing books. If you decide to self-publish and self-market, all you are doing is skipping the publishing step of recruiting an author, and substituting the step of writing one or more books yourself. The key insight here is that it is a business, and the actual writing of the book is incidental to the succe…

It could also be that you write off the cost of the book-writing as an expense in an experience-establishment communications effort. Like building up your professional resume. In effect you are giving time and maybe a little money to be able to say "I'm an author who has published N books on this subject." That's part of the equation, if not the whole equation, for many people.

Quite a few people make this argument, thank you for mentioning it.

My feeling is that this is a holdover from a time when there was a substantial barrier-to-entry for authorship. Back when publishers were the gatekeepers, anybody could write a book, but relatively few were published.

People could vanity-press anything, but nobody would hear about them, because just as publishing was concentrated, so was marketing.

---

But today, anybody can publish a book, and likewise anybody can market a book, super-cheaply. "I wrote X" is worth geometrically less today than it was a decade ago.

If you write a book for other reasons, by all means bask in the reputation. But I find it extremely unlikely that if you are doing it strictly for economic reasons, that writing a book and then marketing it is going to be superior to the many other ways you might have of building your professional resume.

Maybe you should answer a lot of questions on Stack Overflow. Or--like me--become a blowhard on Hacker News.

Re: The Economics of Writing a Technical Book

#52

My experience is that the self-publishing business is a _business_ that generates money from publishing and marketing books. If you decide to self-publish and self-market, all you are doing is skipping the publishing step of recruiting an author, and substituting the step of writing one or more books yourself. The key insight here is that it is a business, and the actual writing of the book is incidental to the succe…

Do you publish on Amazon? If not, you are leaving a lot of money (relative to leanpub sales) on the table.

First, Leanpub allows you to simultaneously publish on Amazon or anything else if you wish. So... If that's what you want to do, you can.

I choose not to publish on Amazon because I have philosophical reasons for not wanting to do business with them. As it is my lifestyle hobby, I needn't worry about leaving money on the table. But if this was my business, that might be important.

Re: The Economics of Writing a Technical Book

#53

This sponsoring is cool. I wonder if they would work with self-published books. Writing a book is a huge effort (I'm the author of a couple Python books, one of which is on the current Python Humble Bundle). From speaking with (many) other Python authors, most would do better financially self-publishing. There are few titles that sell very well from publishers (they do 2nd, and 3rd versions), but these would probably…

Re: sponsoring and self-publishing.

Probably not. The marketing programs people who are mostly the ones paying for these things are mostly looking for predictable content from the publishers who do this sort of thing regularly.

Re: The Economics of Writing a Technical Book

#54

My experience is that the self-publishing business is a _business_ that generates money from publishing and marketing books. If you decide to self-publish and self-market, all you are doing is skipping the publishing step of recruiting an author, and substituting the step of writing one or more books yourself. The key insight here is that it is a business, and the actual writing of the book is incidental to the succe…

Another nice thing I really like about LeanPub is the discount code system.

You can create special discount URLs where you can specify the discounted price, and optionally the period of validity and the max. number of uses.

I've used that in the past for promoting the book, but also for giving the book to colleagues for free (and being able to track whether they actually cared enough to add it to their library :D).

With a traditional publisher, you can typically get some coupon codes for the ebook, but it's a slow process, with little control over the actual amount, no direct access to tracking data etc.

Re: The Economics of Writing a Technical Book

#55

I authored and co-authored some books. I wrote a book on Akka for Packt that has made maybe 5k. Packt is out of India and they have some different standards around topics and contents, but the experience wasn't much different from O'Reilly overall. And there was a mini book for O'Reilly that netted a couple k, mostly because of later sponsorship. Writing a book is a really tough experience. I found it taxing. It's in…

> You become an expert on a topic by writing well on it because you're forced to fill in all the gaps as you go, and then people give you the credit because you have a book.

For me, teaching had a similar effect (and, to a lesser extent, blogging).

I worked in IT at a .edu for ~8 years and was approached to teach a few courses as an adjunct professor, which I did for ~3 years. I think I learnt much, much more while I was teaching than my students ever learned from me.

Re: The Economics of Writing a Technical Book

#56
post #4

Another payout of writing a technical book is that it pretty much solidifies you as an expert in the topic and can be a springboard leading to great job opportunities and things like paid offers to speak or teach. If I ever write a technical book, it won't be for the immediate monetary payout, it will be to solidify expert status in a topic.

I commented above - I published a technical book about 8 years ago, that's been pretty well received (lots of 5-star reviews on Amazon, still selling 8 years later). But boosting my career? Solidifying my expertise in a topic? An MCSE would have done more in that direction than having published a book. Mostly people are just confused when they find out.

I would say just the opposite. I think a certification is a slight negative signal, it seems like there are too many "paper tigers" who memorize enough to take the test and don't know how to implement anything.

I took the 6 tests back in 2010 to get the MCSD for a Software architect (?) but even then I didn't think it was all that valuable. I don't think I ever used it on my resume. But it was more to force me to learn .Net after spending 12 years mostly doing C and C++.

Currently, I'm working on various AWS certs for the same reason - to force me to learn and a company needs a certain number of AWS certified employees to be an Amazon Partner.

I would have a lot more respect for someone who wrote a book.

But does it really make sense to right a book on technology instead of creating a video for PluralSight, Udemy, etc?

Re: The Economics of Writing a Technical Book

#58
post #3

Really useful, thank you! I had saved this post of John Resig's from 10 years ago (!), which also gives some numbers: https://johnresig.com/blog/programming-book-profits/ (I'm not sure if my expectation is reasonable, but I would have thought that a book the most popular JS framework author would have sold more / made more in profit.) I know you said you weren't planning to write another book, but I wonder if in retr…

author here From what I hear from other O'Reilly authors my experience was more negative than most. We got very little support from our editors because of various situations (job change, maternity leave, etc.) If I tried to self-publish my first book it would have never happened. I feel like there's too much to figure out I'd spend a year yak shaving and never produce a book. O'Reilly helped me focus on writing and m…

Deadlines are also both a blessing and a curse. On the one hand, they’re not very flexible if you get busy or there are reasons to slip a bit to sync up with external events. Or just to take a bit more time.

On the other hand, deadlines impose a certain discipline and also force you to wrap things up by a certain date and not draw things out.

Re: The Economics of Writing a Technical Book

#59
Author here of a technical book published with Packt several years ago. I had the first mover advantage as the only book of significance covering a Java library that was (and is) very widely used.

Total page count was ~350-400. It took me approximately 600-800 hours of research, authoring, editing, and final to complete the book. I had a full-time job and so spent about 6-9 months of nights and weekends.

I actually haven't added up the total of royalties but it was probably somewhere over $15-20k on sales of several thousand copies.

I wasn't in a position at the time to capitalize on the consulting / speaking gigs that folks have mentioned, and had I thought more about it I would have put myself in that position.

It definitely has been worth the experience as folks mentioned both in terms of resume-building (a book is a great thing to bring to interviews) as well as general reputation.

Also, if you are truly building a quality technical book, the level of research and knowledge required to do a good job was (for me) at least 5x the depth of my day-to-day work. As goes the old adage, you think you know something well until you try to teach it -- this was definitely true of my research efforts.

Summary - not worth it financially, but it definitely changed my career overall for the better.

If anyone wants to know more details, please reply here or PM me and I'm happy to answer as best I can.

Re: The Economics of Writing a Technical Book

#60

We've published several books, and the author for our latest Vue book earned $20k on the opening weekend. The economics change completely if you self-publish or publish with a smaller firm that has marketing abilities (and better royalty rates). Self publishing is awesome because you keep all the money, but it takes years to build an audience. Honestly, writing the manuscript is the easy part. Building an audience, m…

I'm ready to share this now: our book on Angular 2 did $400k a revenue, per year, the first two years. BUT the reason this was possible was we had a huge audience that trusted us.

Helpful insights.

What are the major factors you credit with getting the large audience?

How large is "large"?

Post reply on HN