Live data from Hacker News

So you want to write a technical book

terathon.com

11–20 of 29 posts

Re: So you want to write a technical book

#11

After talking to a handful of successful technical authors, they have all said - don't write a book for the money.

I'd agree with this, having been a contributing author to a technical book. It was a very interesting process and I learned a lot, but it was not something with a good return on investment, in terms of straight money.

What I've heard from speaking to other technical authors is that the value comes from the opportunities it can generate. Writing a good book in a technical field can help establish you as an expert in the field, which can generate things like consultancy opportunities.

Re: So you want to write a technical book

#12
post #9

After talking to a handful of successful technical authors, they have all said - don't write a book for the money.

I'm personally playing with the idea of starting a blog, not a book, in the mid future. I have tons of unpolished article drafts laying around. On one side I'm painfully aware of the work required to write useful texts and the monetary incentive is almost non-existent. But what motivates me is to finally take a leap to try and be competent at writing in English, which is not my first language. As of now I'm terrible…

I can recommend starting a blog. The big thing, at least for me, is it that incentivises you to finish side-projects and complete thought pieces (at least finish/complete them enough to be able to write about them). Prior to starting my blog I'd years and years of unfinished and undocumented, but potentially quite interesting and/or innovative, side-projects.

Just to add - for technical folks a blog can be free and relatively easy to setup and self host with something like Hugo or Jekyll on GitLab or GitHub pages.

Re: So you want to write a technical book

#13
I also wrote about this topic at: https://andregarzia.com/2021/04/writing-a-technical-book.htm..., it might me interesting for people who enjoyed this post to also read mine.

The author has very good points but their assumption of a 10K advance is not what I have seen (or been paid) in the traditional industry. Most publishers I’ve worked with or approached were paying between 1K and 2K in advance depending on which terms you accept. You usually get some more money if you allow the book to be distributed to libraries or be placed in some all-you-can-eat services.

Regardless of the publishing route you chose — traditional or self-publishing — it is very hard to make money with a technical book. Most people who are financially successful are those with an established platform. The traditional publisher will do very little to push your book. As an example, I made much more money from my self-published books than my recent traditional published book even though they sold less because I keep all the money instead of getting a small royalty.

Publishing a book is not all about making money, each of us have their own reason to write and money is more of a side-effect than the primary cause. I hope posts like these inspire more people to publish.

Oh, I’ve also shipped a prototype ebook generator at https://little.webby.press that runs purely on the client-side, no accounts, no tracking, no state. I think people here might enjoy it.

Re: So you want to write a technical book

#14

So when I started at college, I took a freshman lit class. So first week, the professor assigns a book for us to read and report on. So I read the book, which was "Tinker Tailor Soldier Spy" by Carré and turn in my report on it. So then instructor reads and grades our book reports and returns them to us. So I'm expecting all her markup to be related to my review of the story content. So I was surprised when I saw tha…

"So you want to do X" is a standard phrase which is used to introduce advice on how to do something, or why not to do it. See the poem "so you want to be a writer" by Charles Bukowski.

Re: So you want to write a technical book

#15

I'm an author of a book also published through Amazon Direct Publishing. I've documented how my book is put together with source code, so if you want to produce something suitable for self-publishing, have a look at: https://github.com/faisalmemon/ios-crash-dump-analysis-book I make very little money on the book itself because I have a free web-based version hosted on GitHub. However, I don't know how many sales I've…

Do you happen to know where does the "So you want to" prefix originates from?

Did you reply to the wrong comment?

This is a poem by Charles Bukowski, I don't know if it's the original use: https://poets.org/poem/so-you-want-be-writer

Re: So you want to write a technical book

#17

After talking to a handful of successful technical authors, they have all said - don't write a book for the money.

I'd agree with this, having been a contributing author to a technical book. It was a very interesting process and I learned a lot, but it was not something with a good return on investment, in terms of straight money. What I've heard from speaking to other technical authors is that the value comes from the opportunities it can generate. Writing a good book in a technical field can help establish you as an expert in t…

> the value comes from the opportunities it can generate

Yep, exactly what I've been told too.

I think the two reasons to write a book would be if you're super enthusiastic about a topic and are dying to tell the world about it, and/or you want to establish yourself and use the book as a lead generator.

Re: So you want to write a technical book

#18

Going via traditional publishing is a fools game. The author says you can get $10,000, but for most my books, publishers would only pay $2000. And even that amount is paid over 1-2 years. And he's right about publishers trying sleazy things. Another thing they may ask for is "All future rights in any medium". So people who signed this clause in 90's/early 2000s lost right of their ebook/audiobooks, which are the most…

I agree with all of this. I wrote a book for Packt many years ago (2005-ish?), and I was kind of underwhelmed about the whole experience. The editors were not native speakers of English, and introduced grammatical errors into the book. They published the wrong version of chapters I submitted. (Things would be revised after feedback from editors, I would revise later chapters for continuity with future chapters, etc.) Their editorial oversight basically made me look like an idiot. I could have done better on my own. (I got 3 stars on Amazon, and basically deserved that rating.)

They also changed the terms of payment at some point. I used to get quarterly royalties via Paypal, but they wanted to switch to European bank transfer or something. That is impossible for people based in the US, and they just didn't seem to understand that. It sounds like something I could have sued them over, but the book was definitely past its prime at that point, so I just said "remove my name from the book and don't contact me" and that has worked out pretty well so far. (I think someone else did a second edition. Good for them!)

It was nice to be forced to write an entire book. I signed a contract, got an advance, and delivered it. Today's me would just tell users "read the source code if you have questions", but a book length tutorial was probably good for the project in general.

If you have the mental energy to write an entire book without anyone pushing you to complete it, I think you'll enjoy the enhanced control that you get by self-publishing. Collecting money for PDFs is a solved problem, and honestly, PDFs are a lot more useful than printed books anyway. It is always "neat" to show people a printed book that you wrote, but I'm not really sure that's worth the downsides. I buy programming books, but I haven't gotten a printed copy in years. They just live on my computer, where I'm actually doing the programming.

Re: So you want to write a technical book

#19
I have a friend who co-wrote a book on TCP in the early days and it still sells because it hasn't really changed much in the interim.

On the other hand, how many times do you see something like Java 2.0 or C#2 books which are out-of-date very soon after the author has slaved over the whole process!

The trick is obviously writing about something that won't change too much like Design Patterns and avoiding very specific things unless you are motivated by love!

Re: So you want to write a technical book

#20
Good post.

I think that for most it's best to start with self publishing which is what I did for Deployment from Scratch[0]. I cannot imagine I would have just half the revenue or something like 15%/2.

Technical publishing won't make you rich but you can have an equivalent of a minimum salary at least.

[0] https://deploymentfromscratch.com/

Post reply on HN