liveBook · Manning

Technical communication

As explained in Writing for Developers: Blogs that get read

Writing that explains technical information, processes, systems, or decisions to a defined audience.

Technical communication makes engineering information clearer and more convincing for defined readers. It includes blog posts, commit summaries, code review comments, documentation, proposals, reports, RFCs, presentations, and videos. section 1.0

Start with the reader’s problem, then improve precision by cutting unnecessary words and revising deliberately. Match the approach to the post’s purpose rather than treating every technical piece alike. section 1.4

Use these practical checks:

  • Identify the intended audience and the result the communication should achieve. section 1.4
  • Choose a fitting pattern, such as a bug hunt, system build, lessons learned, rewrite, or trend discussion. section 1.0
  • Prioritize revision time, using generative AI tools when useful, and adapt successful writing into other formats. section 1.4

How Writing for Developers: Blogs that get read covers it

How deep it goes
Explains audience awareness, precision, revision, post patterns, and reuse across formats, without detailing sentence-level grammar.
Examples
Uses bug hunts, system-building accounts, lessons learned, rewrites, trend discussions, and engineering communication formats as examples.
What you can do after
Apply reader-focused patterns and prioritized revision to produce clearer, more convincing engineering communications.
How it connects
Connects audience, technical writing, revision, engineering blogs, documentation, and communication patterns.

Also explained in

Compare how 2 books explain technical communication →

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.