The reality of writing a technical book - manuel bernhardt.
Technical Writing: A Practical Guide for Engineers, Scientists, and Nontechnical Professionals, Second Edition enables readers to write, edit, and publish materials of a technical nature, including books, articles, reports, and electronic media. Written by a renowned engineer and widely published technical author, this guide complements traditional writer’s reference manuals on technical.
Nina Stibbe: Read as much as you can “My number one writing tip is to read a lot,” says Nina, whose first book Love, Nina: Despatches from Family Life was a memoir about her time as a nanny.
Roger E. Sanders has been writing technical articles and books for more than 14 years. He is the author of several books on DB2 9 and the owner of his own database design company. He has had articles published in Certification Magazine and IDUG Solutions Journal.
Again, I say that without judgment. I have been the author afraid to write a book and using a distraction to avoid this fear many times. And I have seen many authors afraid to write a book, for any number of reasons (that usually boils down to the fear it will make them look stupid), so they install a writing assistant but never write a page.
Ever thought about writing a book? I think many of us have, but have no idea where to start or what it would take. In this talk we will write our experiences over the last two years writing the book Erlang and OTP in Action for Manning.
The rest of this post is a brief laundry list of tips for writing your own technical book. Getting a book deal. Make 'em fight for it. One day, I got a cold email from Packt Publishing asking me to write a book on TypeScript. I’d actually been thinking about the idea for a few months, having sent a series of unreturned cold emails to an O.
This is a fact, and you shouldn’t approach writing a technical book with “getting rich” in mind. It probably won’t happen. There are several reasons for this fact: Technical books often apply to a very narrow audience (by their very nature) Technical books are commodities; Technical books are instantly obsolete; Advances, royalties, and e-books; Technical Books Apply to a Very Narrow.