liveBook · Manning

Technical communication

Technical communication is the creation and exchange of clear, accurate information about technical subjects for a defined audience.

How 2 Manning books explain it

Lead Developer Career Guide

The practice of producing clear, structured documentation about technical subjects, systems, or procedures.

How it is used
Helps developers find answers to specific product or feature questions rather than follow a start-to-finish lesson.
How deep it goes
Provides a beginner checklist for planning, formatting, and proofreading documentation; it does not develop a full documentation workflow.
Examples
Uses a question about centering an HTML div to illustrate a direct, narrowly scoped answer.
What you can do after
Practice/perform focused technical writing by defining the goal, following a style guide, and proofreading before publication.

Read how Lead Developer Career Guide explains technical communication →

Writing for Developers: Blogs that get read

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

How it is used
Improves engineering blogs and related communications so readers can understand and act on technical information.
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.

Read how Writing for Developers: Blogs that get read explains technical communication →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.