So you want to write a technical book
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.<p>And he&#x27;s right about publishers trying sleazy things. Another thing they may ask for is &quot;All future rights in any medium&quot;. So people who signed this clause in 90&#x27;s&#x2F;early 2000s lost  right of their ebook&#x2F;audiobooks, which are the most profitable.<p>I would not go with a traditional publisher unless you can afford to hire a lawyer who specialises in copyright law (and not an English lit graduate, which is what most agents are).<p>Self publishing-- from my experience:<p>* Typesetting has never been a problem, but then I write general programming books, and Leanpub handles the conversion really well.<p>* I never found copyediting&#x2F;proofreading very useful for programming books (though I do use them for my fiction). Readers care more about technical accuracy-- ie, does the code work, does the text and code match. are instructions clear etc. A good set of 1st readers is very useful here.<p>The best way to make money is to sell digital copies via leanpub&#x2F;gumroad, as these sellers pay 80-90% royalty. Amazon will only pay you 30% if you price your book over $9.99, which let&#x27;s be honest, most technical books will be.<p>Nathan Barry popularised the formula of selling the book for $39+, and extras for higher pricing, and that works the best.