Live data from Hacker News

The economics of writing technical books

architectelevator.com

71–80 of 97 posts

Re: The economics of writing technical books

#71

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:…

I stopped tracking how many books I'd sold once my POD publisher was sending me monthly order reports that numbered in the ten. Not tens. Just ten.

I guess that means printing on demand was the way to go here. Out of interest, are you willing to share the name of the publisher? And how was the print quality?

Re: The economics of writing technical books

#72

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:…

I think this is a valuable post for those people here that love Z-library and think they should have access to these sorts of books for free.

Not paying for a book when you have the full ability to do so is just greed.

But there are also those who come from places where monthly wage is like $200, so they wouldn't be able to afford a $30 book even if they wanted to

Re: The economics of writing technical books

#73

The prospects for making money selling as an artist (author, painter, athlete, musician, actor) are so poor why do they care so much about copyright law? The route to riches for, say, a musician is to become famous and charge for the coliseum seats to hear him play. To become famous doesn't it make more sense to give the music away? Being famous means you get high consulting rates, get paid for personal appearances,…

I am anti-copyright, but I think you're considering this through the lens of a computer scientist/rocket engineer instead of someone who's had to work a worthless desk job or wait tables or paint houses.

As someone who recently (and probably unsustainably) got out of the cycle of worthless jobs and knows a handful of musicians, here's my perspective:

Indie (and indie label) musicians can actually do fairly well with recorded music. No, they won't be rich. Middle class is at most the target, usually under. Live in a third-tier city and have few expenses. You don't need to sell very much for a baseline livable state.

$10000 a month isn't an achievable target for most working artists. $800, on the other hand, is, even without touring. Sell a handful of Bandcamp copies, sell a few physical copies (cassettes are best for this in the current moment, being cheap to produce and having a fairly loyal audience), have your back catalog do well enough on streaming.

$800 is enough to live on, if you're living with roommates. In many ways, living with $800/month and no unfulfilling 40hr job is much better than living with $1800 and an unfulfilling 40hr job. Even if you don't want to live with roommates, it cuts the amount of work for an employer you have to do by a great deal. Working low-skill work is soul-crushing.

For authors, from what I understand, this baseline is even more achievable. If you have no hopes of getting rich, the current copyright system is fine.

Re: The economics of writing technical books

#74

I think this is a fairly accurate article, although I think it overlooks the indirect benefits of writing a book. My book, Effective Haskell ( https://pragprog.com/titles/rshaskell/effective-haskell/ ), is a pretty well reviewed book on a fairly niche technology. It's been in print for about a year, and was in beta for around 6 months before that. I'd estimate I spent around 4,500 hours over 5 years writing my book a…

As a person, you, having written a book on FP, would you consider this book an okay starting point for a programmer, me, with very little FP knowledge ?

Kudos for spending so many years on this, that's very inspiring.

Re: The economics of writing technical books

#75
post #21

Earlier quoted context omitted.

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 t…

I don't think many would disagree that most businesses fail. Which aligns with the author you disagreed with. So what exactly was your source of disagreement? Make it profitable anyway instead of picking a more proven market/audience?

Not all investments are created equal. the bigger Startups convince rich people to give them millions to work on their idea. Publishers completely invert this; you show them a product and you get a piece of the pie in exchange for them distributing. One's a much safer bet even if everything falls apart. And in the corner, entertainment is pretty much the biggest gamble. Always was, probably always will be.

Re: The economics of writing technical books

#76
post #9

On that note, you can just do it for the good of the world. A lot of us have high-paying day jobs that can support us and good writing can be done on the side. Benefits include not needing to hit some page count (so you can be concise), and bug reports from the community. I don't look down at people who make money from books at all. I admire all writers and editors. (Some publishers can go f themselves, though. :) Bu…

>A lot of us have high-paying day jobs that can support us and good writing can be done on the side.

Meanwhile, me as a laid off gamedev counting pennies from the bits of freelance I can grab...

I guess that explains why so much gamedev literature is behind closed doors ($500 vault access for GDC. Or just oral knowledge inside industry) or non-existant. We can barely get good documentation, let alone technical literature. I'm guessing the energy expended from potentially 70+ hour crunch weeks doesn't leave much left for passion writing either.

Re: The economics of writing technical books

#77

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…

That is cool! I turned to ffmpeg to reduce the size of some family videos because despite the command line it was possible whereas the Windows flavour of the year editor just can't do it.

This made me think that hey why not use it for all video editing needs! Although harder to use than a UI the commands will be the same in 2050 as they are now! Plus it is scriptable.

Re: The economics of writing technical books

#79

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:…

I think this is a valuable post for those people here that love Z-library and think they should have access to these sorts of books for free.

Z-Library is a library, not a bookstore. If you want to own a book - buy it.

You could get a book from your local library (in some places, even digitally) - the author ends up getting peanuts for it anyway.

Re: The economics of writing technical books

#80

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.

A DAW is short for digital audio workstation.
Post reply on HN