liveBook · Manning

Chatting with a human

As explained in Writing for Developers: Blogs that get read

A writing technique in which a person explains an idea aloud to another person to obtain feedback while developing it.

Narrate your idea aloud to a real person while developing a draft. Unlike rubber duck dictation, this approach produces actual feedback: listeners reveal whether they are intrigued, surprised, amused, or bored, while a trusted colleague can question assertions, request clarification, and identify omissions. section 4.4.1

Use the conversation to improve the draft:

  • Notice audience reactions and collect likely questions or objections. section 4.4.1
  • Expect the transcription to be choppy; rebuild a high-level outline and move fragments into logical order. section 4.4.1
  • Choose another drafting method if speaking feels unnatural or uncomfortable. section 4.4.1

How Writing for Developers: Blogs that get read covers it

How deep it goes
Explains the feedback benefits and gives a reorganization tactic, but stops short of a detailed conversation script.
Examples
Uses a trusted colleague as a listener who reacts, questions assertions, requests clarification, and identifies omissions.
What it assumes
Assumes access to a willing listener and acknowledges that speaking may not suit every writer.
What you can do after
Practice it by narrating an idea, collecting reactions, and reorganizing the resulting transcription into a logical outline.
How it connects
Connects verbal drafting with rubber duck debugging, audience feedback, objections, and outlining.
Cover of Writing for Developers: Blogs that get read
liveBookmanning.com
Read Writing for Developers: Blogs that get read on liveBook Get the book at manning.com

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Writing for Developers: Blogs that get read. The section links point to the parts of the book it draws on.