Editing Your Novel: a Model of Testing
summary
Claims a concrete parallel: editing a novel maps to testing software with measurable outcomes — a cited 5% error rate (studies 1–14%), first drafts of ~90,000 words/100 hours, and recurring name/continuity bugs (Melody vs Harmony) that spell check misses. Shows tools actually used: ProWritingAid and Microsoft Word read‑aloud, beta readers and professional editors, and fast fixes via Amazon publishing (small edits propagate in ~15 minutes). Demonstrates what gets built (self‑published Melody Harper series, a halfling fantasy and robo‑teddy draft), what the tools catch, and what still slips through.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 5:42Testing and writing connection
- 9:22First draft flaws
- 16:31Find flaws early
- 22:34Back up and rest
- 24:00Polish draft with tools
- 31:30Read aloud to catch errors
- 36:28Change perspective
- 38:35Common mistakes
- 41:05Editors and beta readers
- 47:46Summary
related talks
47mTelling Better Stories with Tests
58mTesting Strategy - New Model, Better Outcomes
26mThe Impact of Testing on a DevOps Pipeline
01h 11mTest Cases are Not Testing: Toward a Performance Culture
56mIf You Won't Test Your Code, Who Will?
33mTESTING IN PRODUCTION
34mesting in modern times: A story about quality and value
33mWhat people get wrong about testing and how can you leverage tests to develop a lot faster!