Writing a Technical Book

Get Started. It's Free
or sign up with your email address
Writing a Technical Book by Mind Map: Writing a Technical Book

1. Speaker

1.1. Dave Fancher

1.2. @davefancher

1.3. [email protected]

1.4. 2 time Microsoft mvp

1.5. wrote the book: The Book of F#

2. His Journey

2.1. Fell in love with language F#

2.2. Started writing a bunch of blog posts

2.2.1. lots in a couple months

2.3. Started talking about it at conferences

2.4. Experienced the 'dig effect' on his site with one giant spike

2.5. Someone from "No Starch Press" reached out to him about a book technical review

2.5.1. code samples didn't work

2.5.2. mis/bad information

2.5.3. poor organization

2.5.4. author was removed from contract do you want to write your own book?

3. Time Commitment

3.1. Like having a second full time job

3.2. ~11 months, start to finish

3.3. lots of late nights

3.3.1. weekends become writing days

3.3.2. same with lunch hour

4. Where I Wrote

4.1. Cafes

4.2. Pubs

4.3. McDonalds

4.4. Public Library

4.5. WiFi - core resource

5. Who You Work With

5.1. Editors

5.1.1. Developmental Editor Wordsmithing Grammatical corrections Spelling/Typos

5.1.2. Production Editor Oversees the process Coordinating activities Defines Schedule

5.1.3. Copy Editor Formatting Style Consistency

5.2. Reviewers

5.2.1. Technical Reviewer(s) Check text & examples for technical errors Suggest improvements for technical clarity In my case, primary reviewer was a good friend Additional reviewer was recognized expert

5.2.2. Proofreaders enter later in the process generally just listened to them they know their stuff ensure accuracy throughout the work

5.3. Everyone Else

5.3.1. Compositors prepare work for printing little to no direct contact

5.3.2. Illustrators for the cover art, primarily

5.3.3. Marketing enters late in the game develop branding marketing message text on back of book questionaire Cover matter Identify reviewers recognize experts in the subject matter to get to try to review the book

5.3.4. Friends & Family cheerleaders you will get discouraged

6. Questions

6.1. Title?

6.2. Rough schedule / deadlines

6.2.1. agreed on? pushing deadline back? How is that part of the agreement? Fair both ways. no starch knows new author, new technical author, negotiation for changes were really easy mostly a 'no starch' experience

6.3. who you shared chapters with a concern?

6.3.1. publisher worried someone taking the idea or it's just such a big project it's not a concern

6.4. what kind of input would you take from the forward author

6.4.1. they read it... they will have comments, is it done too late for changes, is that part of the plan, is it just too bad, get a new forward author

6.5. pay?

6.5.1. you get a front pay book sales need to cover that before you see any more

6.5.2. then you get percentage based on sales numbers ~$12/book

7. Writers Tools

7.1. Research

7.1.1. msdn

7.1.2. language reference

7.1.3. language spec

7.1.4. blogs

7.1.5. other books

7.2. Software

7.2.1. Word Word Template Starting Point run through InDesign automatically

7.2.2. Visual Studio / IDE

7.2.3. one drive / drop box / drive

7.2.4. one note / wtv note tool

7.2.5. PDFs after compositing

7.2.6. Snipping tool for screen captures

7.3. Defeating Writers Block

7.3.1. ... beer

7.3.2. write drunk edit sober caffeinate for indexing

8. Development Process

8.1. Content Definition

8.1.1. high-level

8.1.2. synopsis

8.1.3. identify major topics

8.1.4. rough outline & refining to draft ToC

8.2. Publishing Agreement

8.2.1. Determine delivery deadline

8.2.2. Draft Table of Contents (ToC)

8.2.3. Royalty terms balance between advance payment and long term royalty payments

8.2.4. Rights assignments

8.3. Content Development

8.3.1. Chapters

8.3.2. Table of contents solidifies Chapter by Chapter basis

8.3.3. Index Important terms & where to find them angular book reference only one thing under 'n'... it's angular Ongoing throughout development creating the index tag important terms and concepts include variations page ranges are helpful multiple variations cross-references

8.4. Front Matter

8.4.1. foreward written by someone else helps establish your credibility as an author should be about the work and/or justify why the work is important Author should read most if not all of the content I agonized for weeks my target audience didn't want one fo the "usual suspects" not data science or finance Forward author traits business acumen industry recognition experience with Functional Programming, F# in particular

8.4.2. preface Organization of the book Describe target audience where to find updates

8.4.3. acknowledgements thanks specific people for their contributions identify how they shaped the book

8.4.4. introduction describes the book Motivation for the book Identify additional resources

9. Printing, Distribution & Marketing

9.1. No starch works with O'Reilly

9.2. Print & Electronic Media

9.3. Channels

9.4. Press release

9.5. Publisher catalog content

10. Final Thoughts

10.1. Writing a book is a long, time consuming process

10.2. Often stressful

10.3. Many moving parts and different stages

10.4. seeing the final product is gratifying

10.5. Would I do it Again?

10.5.1. yes

10.5.2. my wife said I had to wait a year

10.5.3. Time to formulate the next one