Drafting Success
summary
Claims that writing a book mirrors building software and maps its emotions onto the Gartner hype cycle, showing concrete phases: peak of inflated expectations, a trough with steps named procrastinate, question credentials, existential crisis, then slope of enlightenment to a plateau of productivity. Advises making a table of contents then abandoning it, expects the first draft to suck, cites Wiley and Amazon for the book, and urges community and vulnerability among roughly 900 attendees.
AI-written summary · about
chapters (16)
- 0:00Introduction and background
- 1:06Writing a book as a marathon
- 3:59Creative work and self-doubt
- 5:47The emotional hype cycle
- 7:11Imposter syndrome and struggle
- 9:03Procrastination and self-questioning
- 11:06Existential crisis and isolation
- 13:33Slope of enlightenment
- 14:57First challenge is the hardest
- 16:02Catching fire and flow
- 17:49Growth is painful and awkward
- 19:18Procrastination as part of process
- 20:22First draft will always suck
- 21:06Pursuit of perfection and growth
- 22:33We need each other
- 24:20Community and vulnerability
related talks
08m"Why you should write a book even if you don’t intend to publish?"
27mWriting the Next Great Tech Book
37mFailing Well: A Practical Guide to Growth for Technical Writers
36mOvercoming the Plight of Lone Writers
24mCreating Passionate Users
34mMoonshot mindset: A tech writer's guide to thinking big and breaking free from the GDZ
22mChoosing Failure
44mWriting For Nerds - Blogging For Fun and (Not Much) Profit