liveBook · Manning

Direct address

As explained in Writing for Developers: Blogs that get read

A writing technique that speaks to the reader explicitly, commonly by using second-person forms such as “you.”

Direct address turns technical writing into an explicit conversation with the reader. Use “you” for the reader and “I” or “we” for the author instead of creating distance with impersonal terms such as “people” or “users.” section 5.5.1

Pull the reader into the problem

Ask readers to analyze evidence or consider what they would have done at a particular point. This faux dialogue is especially useful in a Bug Hunt, where prompts encourage readers to form their own conclusions. section 5.5.1

Apply a quick revision check:

  • Replace impersonal references with direct second-person language where it sounds natural. section 5.5.1
  • Invite readers to inspect a problem, weigh evidence, or explain what they would do next. section 5.5.1

How Writing for Developers: Blogs that get read covers it

How deep it goes
Defines conversational framing and demonstrates interactive prompts, without prescribing a broader editing procedure.
Examples
Uses “you,” “I,” “we,” impersonal terms, and prompts asking readers to analyze evidence or consider alternatives.
What it assumes
Assumes attention to the reader’s identity, existing knowledge, and reasons for caring about the subject.
What you can do after
Apply it by rewriting impersonal references and inviting readers to reason through technical problems.
How it connects
Connects with audience analysis and the Bug Hunt pattern through reader participation.
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.