Live data from Hacker News

The Economics of Writing a Technical Book

medium.com

41–50 of 151 posts

Re: The Economics of Writing a Technical Book

#41
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…

Thanks, I do see that there's value in having a "turn-key" proven process like O'Reilly's. Yak-shaving might be the stage I'm in now :)

Did you have any technical diagrams in the book? If I were to write a book, I would want some, but I'm not sure if I should invest the time to make them myself. I imagine that most publishers can help with that.

Re: The Economics of Writing a Technical Book

#42

Earlier quoted context omitted.

author here Do you have examples on how you would correctly capitalize on this expertise? I put some things that have happened since writing the book in the outcomes section but so far they have all been free speaking engagements.

Basically $1000+/day consulting rates. You still have to do the legwork of getting the gigs, but justifying those kinds of rates are much easier when you literally wrote the book on the subject of your contract. Having written it for a well known, respected, even iconic, publisher does a lot of the work here too, self publishing would have a lesser effect.

$1000/day is $125/hour, which is a standard hourly rate for software developers. I would expect authorhood/extreme-subject-matter-expert to yield at least a 2x premium.

Re: The Economics of Writing a Technical Book

#43
post #35

Earlier quoted context omitted.

That's the main reason I would write a book: to tell people that I wrote a book. You can literally say, "I wrote the book on that."

Hi, you've been shadowbanned, which is a shame because your last three or four comments have been perfectly reasonable (I vouched for them so they'd show up). I'd contact a moderator or something if I were you.

Not anymore shadowbanned

Re: The Economics of Writing a Technical Book

#44

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…

Can you give us a quick overview of what's unique about Ramit Sethi's email marketing?

I also found this blog post for anyone else whose interest was piqued: https://growthlab.com/guides/ultimate-guide-to-email-copywri...

Re: The Economics of Writing a Technical Book

#45

Earlier quoted context omitted.

Basically $1000+/day consulting rates. You still have to do the legwork of getting the gigs, but justifying those kinds of rates are much easier when you literally wrote the book on the subject of your contract. Having written it for a well known, respected, even iconic, publisher does a lot of the work here too, self publishing would have a lesser effect.

$1000/day is $125/hour, which is a standard hourly rate for software developers. I would expect authorhood/extreme-subject-matter-expert to yield at least a 2x premium.

> a standard hourly rate for software developers

Maybe in SF or NYC, but even then I don't think $125/hr or $260K/year at 40 hours/week is "standard" even there.

Re: The Economics of Writing a Technical Book

#46
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 success of the business. I repeat, incidental. The main drivers of the publishing business is marketing to acquire more customers, and finding ways to build additional revenue streams to generate value from each customer.

If you don't care to know what LTVs and conversion rates are, you will not be happy running a publishing business regardless of who wrote the book(s) you are publishing.

The other road forward is to have a publishing hobby. Some hobbies make token amounts of money. I know two brothers who buy collectible corvettes, fix them up, drive them for exactly one Summer, and then sell them.

The money they make seems like a nice side-business, until you listen to them tote up the hours and expenses and tax implications. They would make way more money selling almost anything else part-time. And that is my personal experience with my own writing hobby.

The money sounds nice until you actually look at it as a business, and then you start asking why I am on Hacker News writing this comment when I should be curating my email list. The "problem," of course, is that writing is my hobby, not curating email lists.

So I believe you need to decide whether you have a business or a hobby. If it's a business, then you have to put 80% of your work into the activities that produce 80% of the revenue. And that is not writing, in my experience or observation.

Whereas with a hobby, you put 80% of your work into the activities that produce 80% of the happy juice in your brain. If writing does that for you, you can write and make a little something on the side that will pay for some discretionary lifestyle purchases. In my own case, that's things like a 1950s-era Rietveld Crate Chair.

Blatant Endorsement:

FYI, I publish with LeanPub http://leanpub.com, because it generates the maximum revenue for the small scale of my writing hobby, and its "lean" approach helps me maximize my contact with my readers as part of the writing process. Since writing is my hobby, that's a win for me.

They also help people with a writing business in some amazing ways, like their tools for creating courses, which helps generate more revenue from existing content, and the ways they help you build a mailing list so you can develop other revenue streams from your existing readers. If you want to build a business, they help you build your business.

Re: The Economics of Writing a Technical Book

#47

Earlier quoted context omitted.

$1000/day is $125/hour, which is a standard hourly rate for software developers. I would expect authorhood/extreme-subject-matter-expert to yield at least a 2x premium.

> a standard hourly rate for software developers Maybe in SF or NYC, but even then I don't think $125/hr or $260K/year at 40 hours/week is "standard" even there.

This yearly rate calculation assumes you spend 100% of your working hours on-contract, which is definitely not the case.

Re: The Economics of Writing a Technical Book

#48

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.

Re: The Economics of Writing a Technical Book

#49

Earlier quoted context omitted.

$1000/day is $125/hour, which is a standard hourly rate for software developers. I would expect authorhood/extreme-subject-matter-expert to yield at least a 2x premium.

> a standard hourly rate for software developers Maybe in SF or NYC, but even then I don't think $125/hr or $260K/year at 40 hours/week is "standard" even there.

$125 an hour isn't crazy. I billed that doing some consulting for a company in Memphis maybe five years ago, and that was a no negotiation involved arrangement. I'd worked there before, so they knew me. I threw a number out there and they pretty much went, "alright, sounds reasonable enough".

Re: The Economics of Writing a Technical Book

#50

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.
Post reply on HN