liveBook · Manning

Reader language

As explained in Writing for Developers: Blogs that get read

Language adapted to a reader's knowledge, context, expectations, and communicative needs.

Adapt your language to the reader’s knowledge, context, expectations, and communicative needs. Adjust formality, tone, explanation level, technical terms, cultural references, inside jokes, comparisons, and analogies. section 5.5.1

Review each draft with the intended reader in mind:

  • Use “I” or “we” for yourself and “you” for the reader; avoid impersonal labels such as “people” or “users” when direct address is clearer. section 5.5.1
  • Match the language to the audience: community users may need friendly, transparent, technical prose, while investors may need crafted, value-oriented, aspirational language. section 5.5.1
  • Invite readers to analyze evidence or consider their choices when a faux dialogue helps them enter the problem. section 5.5.1

How Writing for Developers: Blogs that get read covers it

How deep it goes
Defines several language dimensions and contrasts two audiences, without prescribing a formal revision checklist.
Examples
Contrasts language for teammates, experts, family, community users, and potential investors, and uses Bug Hunt dialogue.
What it assumes
Assumes that writers can identify who they address, what readers know, and why readers care.
What you can do after
Practice revising technical prose so its directness, detail, terminology, and tone fit its intended readers.
How it connects
Connects audience analysis with tone, technical terms, direct address, comparisons, analogies, and reader engagement.

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.