liveBook · Manning

Revision

As explained in Writing for Developers: Blogs that get read

The process of reviewing, modifying, and improving a draft's content, structure, clarity, or correctness.

Revision improves a technical draft by making its purpose, explanations, evidence, and reader experience clearer. Prioritize changes that help readers over grammar nitpicks, and stop before diminishing returns consume the time needed to publish. section 1.4 section 5.1

Use this compact revision loop:

  • Return to the targeting criteria and original goal. section 5.3.4 section 7.2
  • Read the draft aloud and flag sentences that feel unnatural or cannot be spoken comfortably in one breath. section 5.3.4
  • Prioritize critical sentences, such as the introduction and the paragraph presenting major findings. section 5.3.4
  • Timebox improvements, then check grammar reports and read aloud again. section 5.3.4
  • If doubts remain, seek another opinion and verify current names, vulnerabilities, and claims before publishing. section 7.2

When drafting and revision belong in different phases

While drafting, resist premature editing: set a short goal, disable distracting checks, mark troublesome wording, and move on. Start with an easier section instead of forcing the introduction. Revise after the draft exists, when you can judge the whole direction. section 4.4.2

How Writing for Developers: Blogs that get read covers it

How deep it goes
Provides a staged revision procedure with read-aloud tests and prioritization, while de-emphasizing exhaustive grammar polishing and endless refactoring.
Examples
Uses timed drafting, out-of-order writing, read-aloud tests, grammar tools, AI prompts, second opinions, and internet checks.
What it assumes
Assumes a draft, target reader, and original goal; teaches readers to defer editing during drafting and revise systematically afterward.
What you can do after
Apply it via targeting criteria, read-aloud tests, timeboxes, grammar checkers, AI prompts, feedback, and final fact checks.
How it connects
Connects drafting, editing, technical writing, reader perspective, feedback, grammar checking, and generative AI.

Also explained in

Compare how 2 books explain revision →

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.