Another one: If you are fine writing blog posts, but have trouble writing for a book because you think suddenly things need to be perfect (and run into writer'

Another one: If you are fine writing blog posts, but have trouble writing for a book because you think suddenly things need to be perfect (and run into writer's blog)... Then start with blog posts. Ask your publishers if you can publish them. If not, write them as if you'd publish them on your blog. Then take the blog posts, and turn them into chapters of your book. A blog post tends to be a bit more self-contained than a book chapter, but even for a book chapter, people appreciate it if they can read it separately. Other things: * don't expect to get rich. Writing usually pays way less than programming. * no many how many passes you have made, you'll always find spelling and grammar errors (even after a professional copy editor went over it). Try to get them fixed, but also accept it as a fact of life that things won't end. * Making good illustrations takes quite some time. * Expect illustrations to be printed black and white, with grays being butchered, unless you have negotiated otherwise your publisher. * The publisher has a project manager for you. Keep them updated. They'll be more lenient with delays if you tell them early. Communicate as much as you'd do with a project manager at your job, even if they don't ask you every week or month (because they don't want to be pushy). * Keep a list of contributors, where you add names and email addresses as soon as somebody helped you. After half a year, you would forget at least a few contributors. List people by name in a "Thank you" section. Everybody likes to read their own name in a book :-) * Keep a list of people + email addresses who expressed interest in your project. The publisher likely will send out ebook copies to people, in the hope that they will review your book on amazon. Be prepared for that.