Everything You Need to Know About Writing Technical Python Books
summary
Panel discussion distills actionable book-writing tactics: make code listings executable and kept in version control, run automated checks so every example actually works; use Visual Studio Code for development and Microsoft Word (publisher templates) for manuscript delivery; expect heavy editorial rewrites and pick a technical editor or child readers to validate explanations; choose a publisher (No Starch, O’Reilly, Wiley) or self-publish, note timelines (roughly a year per book is common) and consider a Creative Commons or traditional contract.
AI-written summary · about
chapters (29)
- 0:00Intro
- 2:25How did you get started
- 5:00When did you start writing
- 8:00Who is your book for
- 9:40What is the fundamental difference
- 10:10What is the biggest challenge
- 11:40What is the main appeal of a book
- 12:55Outline and scope
- 15:00Are you done yet
- 16:30Choosing a technical editor
- 17:45Copyediting
- 23:20Making Connections
- 24:40Reading Reviews
- 25:40Most Fun Parts
- 27:00Technical Logistics
- 28:45Code Blocks
- 30:50Doc Books
- 34:30Git
- 36:00Workflow
- 36:50Personality
- 40:00Cultural References
- 41:40Book Cover
- 43:30Favorite Technical Book
- 44:40Why Read Technical Books
- 45:20My Favorite Book
- 47:50Wise Pragmatic Guide to Ruby
- 49:30Thank You
- 50:40Next App
- 51:40Where to Buy
