Live data from Hacker News

Ask HN: Considerations when asked to write a book?

news.ycombinator.com

91–100 of 147 posts

Re: Ask HN: Considerations when asked to write a book?

#91
I wrote a book for one of the pubs you mentioned and have talked to several other authors. Know what you're getting yourself into - you're going to be responsible for all editing so it is A LOT OF WORK. Never ending work. And it will never be good enough but dates move forward.

You don't make any money publishing with a publisher - not directly from the book, anyway. Maybe a dollar or two an hour. Do not do it for the money. Once you're done, however, you can demand a higher salary as an 'expert' - say an extra 10% or 15%. Or double your income if you move into contract or consulting. :)

One STRONG recommendation is to not promise the publisher first stab at any future books. Some publishers have this in their default author contract - that you can't publish with another publisher without first offering the publisher the opportunity to publish first (maybe for your next 3 books). That clause is one I would demand be removed from the contract.

Re: Ask HN: Considerations when asked to write a book?

#92

I was a reviewer for a Packt book ( http://droppdf.com/v/UTl8X ). The review process was terrible, they ended up not taking my feedback into account and the book was published with lots of technical mistakes. The final book is essentially a random tutorial from pre-existing web content. Avoid them.

I will second this. I have had several bad experiences with Packt.

Re: Ask HN: Considerations when asked to write a book?

#93
I am late to this discussion but I have one important thing to add: make sure in your contract that the rights to the book revert to you if the publisher does not publish the book in a timely manor.

This happened to me just one time, and I learned my lesson: I signed a contract with good terms, and half way through writing the book discovered the publisher was also producing a competing book. They decided to not publish my book, but did not revert the rights. I got to keep $5000 in advance money but I was unhappy. I wanted to give back the $5000 in return for the book rights but the publisher said no.

Edit: I have published 12 books with mainstream publishers like McGraw-Hill, Springer Verlag, etc. and many more self published books via Lulu and most recently Leanpub. I totally enjoy writing.

Re: Ask HN: Considerations when asked to write a book?

#94
I have written some tech books, one of them best-selling, tech edited others, and written a preface for one. I am also the author of published novels.

The amount of money and contract terms vary widely with the publisher. This is where a contract with one of the big publishers is in your favor. You can also consider self-publishing, but that is a different business model, which I will not cover here.

Don't be afraid to ask for different terms.

In particular:

- You can negotiate for an escalator clause on the royalties. This means that the more books you sell, the higher your rate.

- You can ask for a higher advance or a lower advance and higher royalty rate. You can ask for the advance to be split differently (on contract, 25%, 50%, full MS, final acceptance, etc).

- You should negotiate the option clause. This is the clause that says they get the first option on your next book. Specific terms to negotiate include limiting the scope - not "next book" but "next book on the topic of game development with Python". Also make sure they have a limited time to consider your proposal before deciding to buy it or not. 60 days seems to be a common number, but you can probably negotiate that down.

- Strike any non-compete clauses (that you will not write a book on this topic for anyone else or self publish one).

- Strike any cross-accounting clause. This is where you must earn out the advance on every book you have for a publisher before you can receive royalties on any book (and royalties for book 2 can be counted against the advance for book 1, and so on).

Some publishers pay monthly, some pay quarterly, some bi-annually. Take this into account.

Ask your publisher what their marketing and promotion plan will be for the book. How much support are they putting into it?

Earnings vary a great deal, but I have been very happy over the years, and book earnings have paid large chunks of my mortgage. How much you make depends a lot on the size of the audience, what other books are in the market, the timeliness of the book, and the publisher's approach to distribution and marketing. It tends to be on the small side and I realize my experiences are not typical.

It has opened doors for me and my co-author. We've been offered jobs, contracts, writing opportunities, and speaking opportunities.

I would say this was the best career decision I ever made. It's also draining and time-consuming, so be aware it's a large project.

Good luck!

Re: Ask HN: Considerations when asked to write a book?

#95
Look for any "right of first refusal" clauses in the contract.

I was approached by Packt a few years ago, to write a book in a fairly niche topic (http://amzn.to/29LR9Ly). Their reputation is not the most stellar, but I put a lot of work into making a high-quality book with source code on GitHub and live examples running on Heroku. So I "beat the odds", I guess... earning several times the (small) advance, and getting some positive reviews on Amazon and Goodreads. The money doesn't justify the time that I put in, but it's tremendous resume fodder and played a large role in taking my career to the next level with my next job change.

However, my biggest regret is that I signed a clause giving Packt the right of first refusal on my next two books. Realistically speaking, I doubt I'll ever get around to writing another technical book again. If I do, I'll probably pitch it to Packt and then self-publish if they don't want it. But it sucks being locked in like that.

Truth be told, if I had known then what I know now then I probably would have just self-published in the first place. There's no real money in book authoring no matter which route you take. Publishers don't really promote books, and you're really on your own anyway for author support during the writing process. I doubt that most employers looking at my resume would care whether the publisher was Packt or Leanpub, so I probably would have gone the latter route just for the freedom.

Of course, if one of your publisher options is O'Reilly, then maybe that's another discussion.

Re: Ask HN: Considerations when asked to write a book?

#96
I've written 3 technical books. I highly recommend talking to an agent. I used studiob.com. Not only will they negotiate money on your behalf, but they'll get crappy clauses taken out. Stuff you've never heard of like "cross accounting clauses". My last contract had a right of first refusal for my next book in their opening offer. The acquisitions editor even laughed when we asked about it because she didn't know it was there.

The agent will take 15% and believe me it's worth it.

Whatever deal you cut, pretend like it's not going to earn out its advance. Because it probably won't. As everyone says, you're not doing it for the money. You're doing it because you love the topic, love to write, and to be seen as an expert in the field. Writing the books themselves earned me very little money. Follow on work, like articles, and using it in salary negotiations, more than paid for itself.

I'd suggest you figure out the book you want to write then shop it around the publishers (again, agent helps). And be picky about the publisher, talk to other authors that used them. They're not all the same. When one publisher hires editors and pays their technical editors and another expects a lot of self-editing and offers a free book to the tech reviewers, the outcomes will be vastly different.

Re: Ask HN: Considerations when asked to write a book?

#97

I've just spent 18 months working on a title for Manning which is due for publication soon: https://www.manning.com/books/cross-platform-desktop-applica... - Writing a book is a huge undertaking - make sure that you have the time to do it. - Find a good environment to write the book in - if you have kids/pets/others that will interrupt you, try to find somewhere else to do the writing - Marcus Hammerberg (the co-auth…

I just bought your book. It still talks about IO.js. Are you planning on updating that?

Re: Ask HN: Considerations when asked to write a book?

#98
I also wrote a programming book. Expect about an 8% royalty rate, and an advance anywhere from $4k to $8k, paid out in installments as you turn in milestones of the book. Depending on how well your book does, you may never get any more than your advance, or you may get a lot more. I've received about $8k in the two years since the book went on sale, for a total of $16k including my advance.

That may sound like a lot, but keep in mind that it amounts to about $8 per hour based on the amount of work I put into it. It's A LOT of work. But it's very fulfilling, and it's wonderful to receive tweets and reviews from people who your book helped.

Re: Ask HN: Considerations when asked to write a book?

#99
post #97

I've just spent 18 months working on a title for Manning which is due for publication soon: https://www.manning.com/books/cross-platform-desktop-applica... - Writing a book is a huge undertaking - make sure that you have the time to do it. - Find a good environment to write the book in - if you have kids/pets/others that will interrupt you, try to find somewhere else to do the writing - Marcus Hammerberg (the co-auth…

I just bought your book. It still talks about IO.js. Are you planning on updating that?

Yes, the mentions of IO.js in the book should mention that it was merged back into Node.js. Out of curiosity which chapter were you looking at? I will check the MEAP and make sure that it has the latest chapter versions.

Re: Ask HN: Considerations when asked to write a book?

#100
post #97

Earlier quoted context omitted.

I just bought your book. It still talks about IO.js. Are you planning on updating that?

Yes, the mentions of IO.js in the book should mention that it was merged back into Node.js. Out of curiosity which chapter were you looking at? I will check the MEAP and make sure that it has the latest chapter versions.

Just the Welcome before Chapter 1. Why not just remove the references to IO.js? And explain Node.js.
Post reply on HN