Earlier quoted context omitted.
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?
Lightning Source, now part of Ingram. Wouldn't recommend them for working with you to get your book on shelves, and this was before POD really took off so I'm sure there's better alternatives these days. The print quality was top notch though.
The economics of writing technical books
91–97 of 97 posts
Re: The economics of writing technical books
#92On 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…
This whole idea of greed is good and the profit motive being the prime mover is a very recent and arguably detrimental mindset for the long term development of civilization.
Re: The economics of writing technical books
#93On 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…
Nah, people should pay, at least a minimum amount for others's work. Look at open source, it's a mess, exactly because of the nonexisting payment layer. And what they used open source code? To bootstrap llms, for free.
Re: The economics of writing technical books
#94Re: The economics of writing technical books
#95Earlier quoted context omitted.
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…
I'm surprised they can even reach $800/mo. But there are multiple other avenues for revenue. One can sell merchandise, such as the ever-popular band t-shirt. And there are still many who will want to buy an official cassette rather than just download a song. There are also paid gigs - a live performance is not replaceable with a download. One can livestream a performance, and get paid for the ad placements.
Livestreaming and live performances and merch creation are all vastly different skillsets than making music in your bedroom, and some musicians are only really good at that part.
Re: The economics of writing technical books
#96I 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…
To fuess some numbers for this, Cubase 6 was ~2011, so sales would start in 2013, 11 years is 132 months, at $400/month that's $52,800 total over the years, and that was for about a year of work. So it paid something, but probably not as much as a 1 year full time job would have.
Re: The economics of writing technical books
#97Earlier quoted context omitted.
This has been in my "to buy" for a while. I am decent with ffmpeg but I could always learn more.
The ebook (.epub or pdf) is for free on the GitHub: https://github.com/jdriselvato/FFmpeg-For-Beginners-Ebook/tr...