(The realities of) 
Writing A Techincal book 
(Our Technical Book)
Leaving here you will understand the reality of writeing a technical book


Believe that you have something to say and that it's worth saying
Writing our book
Book Proposal
Book Proposal
Gathering Coauthors
Preparation
Start Writing
1/3 Review


2/3 Review
Inconsistant Voice
Loose Terminology
Choose an audience
Major Refactoring/Rewrite

Start Editing
Final Review
Production

First brush with readers
Incorporate feedback (rewrite)
book becomes real (life becomes memory)
Deadline revisions
Have a story
Don't focus on tools
focus on writing
follow publishers guidelines


Out of head onto paper
Agile practice
TOC refactoring
(Start Rewriting)
(Really)
Good raw material
Story Line
Well Targeted
Easier to follow
You are not done
Your diagrams that is
Time to polish
Cross editing (unify your voice)
Don't be afraid to rewrite (not a gem yet)

Indexing
Final edits (Grammer/Style changes, Diagram finalization)
Technical editing (Hey Ken!)
Production Editing (typesetting)
Printing

Launch Summer 2010
Book = Job
Treat it like a job
Schedule writing times
Working together
Take deadlines seriously (semi seriously)
Make it transperant (Dropbox)

OTP Challenges
Terminology (ambiguous, non-existant)
Implicit standards, conventions
Incomplete documentation
(Coauthors are good)
"The book isn't done until its in your hand" - Francesco