liveBook · Manning

Writing process

As explained in Writing for Developers: Blogs that get read

The writing process is the sequence of activities involved in planning, composing, revising, and editing written text.

Treat writing as forward motion rather than perfect wording. A working draft gets finished by resisting premature editing, starting wherever progress is easiest, and returning to difficult sections later. section 4.4.2

A practical drafting pass

Choose a specific target, such as drafting several paragraphs in 20 minutes. Set a timer, disable distracting corrections, mark uncertain wording for later, and keep moving. If the introduction stalls, skip it and draft a test result, concept, or other accessible section instead. section 4.4.2

Use these checks to keep the process bounded:

  • Define a realistic stopping point instead of endlessly tweaking beyond diminishing returns. section 1.3.3
  • Reserve consistent long-term time for large projects and accept that deadlines may require a final decision to let the work go. section 17.2.2

How Writing for Developers: Blogs that get read covers it

How deep it goes
Explains timed drafting, deferred editing, out-of-order composition, and completion limits without developing a full revision method.
Examples
Uses timed paragraph goals, Pomodoro timers, disabled spell checking, highlights, comments, skipped introductions, and book deadlines.
What you can do after
Apply it via timed drafting, deferred edits, flexible section order, and explicit stopping points.
How it connects
Connects drafting with editing, introductions, deadlines, time planning, and diminishing returns.

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.