So You Want to Write a Technical Book: A No-Bullshit Guide

What people are saying about the book:

"It's very good and true to reality. Writing a book and getting it published is a major project, and people often forget about the hard organizing and planning work that goes into that. Your book talks about all those important topics. It really brings back memories :)"

- Vitaliy Osipov, Author of "Buffer Overflow Attacks" and other books on application and network security, @agelastic

"Thanks Justin, I wish I would have had this guide when I first started writing my book. With this information I can finish my book much quicker."

- Alfred Farrington, Current Author, @althetinkerer

"Lord knows I wish I would have read this before starting my book."

- Author who wishes to remain nameless

What Is Inside

Two-time author (we call that prolific in the biz), Justin Seitz, walks you through a simple process on how to write a technical book. 

You will learn pain free ways of creating an outline, finding a publisher, doing the actual writing, and how to support your book after it hits the shelves.

If you are a developer, sys admin, hacker, engineer, or any other flavour of technical person looking to write a book or you are currently writing one, there may just be a few nuggets of wisdom here that you can use.

Enjoy! And don't forget to ping me with any questions or criticisms: @jms_dot_py on Twitter.

Author Bio 

Justin Seitz is the author of Gray Hat Python: Python Programming for Hackers and Reverse Engineers and Black Hat Python: Python Programming for Hackers and Pentesters. By day he is a security researcher and consultant and by night he fields questions from aspiring technical authors. You can usually find him in a hockey arena.