Live data from Hacker News

The economics of writing technical books

architectelevator.com

61–70 of 97 posts

Re: The economics of writing technical books

#61
post #21

Earlier quoted context omitted.

I disagree. This is the case for anything entrepreneurial. Vast majority of ventures fail. Reward/Risk ratio (in finance we call it Sharpe ratio) generally equalises across the spectrum. That is there is no free lunch. You can choose an activity that has better odds of making money. But you will make leas money on average.

I think you underestimate the cost of writing a well-researched book. Pre-publication, the process consumes lots of time and energy and money while generating zero revenue, output, or other benefit. Very different from most business ventures. Source: I have written a book, and have also started my own business and have worked for many startups. (VC-backed startups pay their employees.)

Isn't this the case with any new business venture? There is going to be a period of spending (looking it as "investment" is therapeutic) and negative cash flow. In many cases this can be years. Publishing, professional sports and entertainment, start-ups - all seem to have similar distribution of reward.

Being a paid employee of a start-up is different. That would be similar to receiving an advance from a publisher to write a book.

Re: The economics of writing technical books

#62
I've written 9 technical books, including 4 for a major publisher (Apress), and 5 independently (https://wjgilmore.com/). One of these books (Beginning PHP and MySQL) has incredibly reached its 20th year in print[1], and has been translated into a bunch of languages. Many years ago I also wound up editing ~70 or so books for Apress plus a few for Wiley. In summary I know this business pretty well, and still follow it closely despite not having participated in it for several years.

My advice is this: if you want to write a book, then write it. But if you do have this sick, twisted desire to spend countless hours writing and editing your work, telling yourself you are an idiot, not good enough, and a horrible writer, then at least do so with the thinking people are going to read it and as a result you will make money. Set yourself up for the possibility of success. How can you do this?

* Package the book in different ways (print, print + videos, print + videos + consultation). This has been extraordinarily successful for me personally.

* Use the amazing Leanpub.com to do the book production (turn your Markdown into PDF, epub, etc). Not an affiliate or whatever, just mentioning it because you will save untold hours of pain.

* If you want to work with a publisher (and in 2024 I don't suggest you do), then choose very, very wisely. There are two who I would even consider working with today, and even in those cases I would absolutely not cede the usual rights.

Hope this helps, Jason

[1] As of this fifth edition my name is no longer on the book due to a disagreement with the publisher.

Re: The economics of writing technical books

#63

I've written 9 technical books, including 4 for a major publisher (Apress), and 5 independently ( https://wjgilmore.com/ ). One of these books (Beginning PHP and MySQL) has incredibly reached its 20th year in print[1], and has been translated into a bunch of languages. Many years ago I also wound up editing ~70 or so books for Apress plus a few for Wiley. In summary I know this business pretty well, and still follow…

I would also recommend writers to keep their digital books up to date and current. The book should not be considered finished the day it is released.

Jeff Geerling gave his devops books away (free) on multiple occasions. I chose to pay for them as he kept working on and improving them well after release.

If more writers took this approach, the quality would increase.

Re: The economics of writing technical books

#64
There’s a hack if you work in Developer Relations for a tech company.

1. You write the book as part of your job during the workday. 2. Your company buys the published book to distribute at events and conferences for free. 3. The book seems successful and you get paid. 4. The book gives you credibility in industry events and may even help you get a special visa if you need one.

Full disclosure: I have never written a technical book, but you should if you work in Developer Relations.

Re: The economics of writing technical books

#65

In 2020 I wrote a book on FFmpeg after going through the entire FFmpeg documentation. I wanted to learn FFmpeg inside and out by actually using it to convert audio/video based on what the documentation offered. In the end I open sourced the results as an extension to the official docs[0] and then released in on Kindle as well[1]. In the last 4 years I've sold 743 books which is just shy of $2000. Still I love the fac…

This has been in my "to buy" for a while. I am decent with ffmpeg but I could always learn more.

Re: The economics of writing technical books

#66

I've written 9 technical books, including 4 for a major publisher (Apress), and 5 independently ( https://wjgilmore.com/ ). One of these books (Beginning PHP and MySQL) has incredibly reached its 20th year in print[1], and has been translated into a bunch of languages. Many years ago I also wound up editing ~70 or so books for Apress plus a few for Wiley. In summary I know this business pretty well, and still follow…

> [1] As of this fifth edition my name is no longer on the book due to a disagreement with the publisher.

oh man, I'm sure you can't share, but now I really want to know.

Re: The economics of writing technical books

#67

I've had four technical books published and I've finished writing my fifth which I'm in the midst of negotiation with publishers about distributing. I've seen many similar articles to this one before, but I want to complement the author by saying that this one rings the most true and is the most comprehensive of all of them. However, I want to emphasize a paragraph from his article, that I think needs more emphasis:…

> as the market gets flooded with LLM-generated garbage

That's already happening, and getting published. Recently read an awful tech book that was obviously generated by an LLM, it was so bad that I reached out to the publisher, who assured me that this was just the author's style, and that they promised no LLMs were involved. All lies, of course.

Apparently publishing awful books can somehow generate revenue.

Re: The economics of writing technical books

#68

I have written a textbook on using Cubase (a DAW), but including all the background that I think you need to be well-rounded (music theory, audio concepts, mixing, effects, instruments, etc). It took me 2 years to write, one of which was all my spare time, so probably about 9 months to a year's full-time work. Then I found out no-one bought it! Only pure chance led to it being promoted by someone in the industry, may…

I had to look-up what Cubase was (it's music software) to figure out the niche.
Post reply on HN