Writing the Next Great Tech Book
summary
Explains how tech book proposals actually win: pick a verb-focused scope and a tight audience, show market signals like GitHub stars or user numbers, and prove differentiation with Amazon competitive research. Describes concrete deliverables: an outline and a sample chapter on spec that publishers use to judge fit. Covers tooling (markdown/CMS/git), the editorial pipeline and production workflow (development editor technical reviewers copyedit proof print), and realistic pay expectations.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:52Street Cred Slide
- 1:22Why write a book?
- 3:45The Big Differences
- 7:57Pre-writing
- 8:38Do some homework
- 10:14Make an outline
- 11:17Find a publisher
- 14:01Create a proposal
- 21:16The Process
- 26:06End Screen
related talks
45mTelling Your Technical Story
13mWhat Not to do When Pitching a Book
21mWhat I learned writing a lousy tech book
44mWriting For Nerds - Blogging For Fun and (Not Much) Profit
40mHow to Write. A Craftsman's Guide
26mDrafting Success
39mBeyond Words: Strategies for Leveling Up Your Tech Writing Career
35mEngage or Die: Four Techniques for Writing Indispensible Docs