↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Writer as Coder: The Iterative Way to Write a Book

Babauta argues that nonfiction books should be written more like iterative software than like a finished product produced in isolation. He describes using alpha testers, reader feedback, revisions, wider testing, Kickstarter support, and post-print updates to improve the book through repeated cycles.

Reading notes
#

  • The traditional book model leaves the work untested until launch.
  • Iterative programming uses a minimum viable product, testers, and feedback to improve a product over time.
  • Babauta applied that model to Zen Habits: Mastering the Art of Change.
  • He wrote chapters for ten alpha testers who read early versions and tried the ideas in practice.
  • The testers journaled about the chapters, and he used those journals as feedback.
  • He rewrote responses to their questions and sometimes turned those responses into new chapters.
  • He then tested the ideas with larger groups through Zen Habits and Sea Change.
  • He gathered feedback through Twitter, emails, polls, and forums.
  • He later rewrote the book from scratch using feedback from readers, testers, and his editor Juli.
  • He plans to keep revising the book after print and to prepare a second edition online later in 2015.
  • He says the method makes him more motivated, lowers the burden of writing a large book, and catches problems before print.
  • He also says the process lets him create in solitude while working with a community.