3 ms·
After almost a dozen years spent writing almost as many technical books (some second editions), I wouldn't recommend taking forever with a technical book. It wi
by __mharrison__ 3y ago
After almost a dozen years spent writing almost as many technical books (some second editions), I wouldn't recommend taking forever with a technical book. It will be out of date by the time it comes out.
Every author has to figure out why they write. For me it was a business decision, and finally this year I'm making more from books than I was doing software.
- r0s 3y agoMy first book deal went through recently and I'm about to finally get published. Any advice for a first timer? I'd like my technical non-fiction to lead to a novel deal later. What do you think?
- __mharrison__ 3y agoYour publisher will likely send out an email when the book comes out. Don't expect much more from them. My advice, promote the book and use it to build up a mailing list. (I should have been building my list much earlier.) I'm not sure about the intersection between technical books and traditional novelists. The only person I've known who tried it ended up going the self published route for the novel. I am curious myself about writing a book for the general business audience through a traditional publisher. Happy to answer more questions, I have details in my bio for contacting me.
- r0s 3y agoAppreciated, thank you.