On Writing Well
William Zinsser's classic guide to writing clear nonfiction, first published in 1976 and still updated through its 30th anniversary edition. Its core lessons (cut clutter, write simply, know your reader, rewrite) apply directly to design docs, incident reports, pull request descriptions and the messages that persuade a team. Applying even a third of it makes you noticeably better at a part of the job nobody trains engineers for.
30th anniversary edition
Harper Perennial · Sept 2026
4.24/5 (31,693 ratings)
Goodreads · Sept 2026
Book
Career Growth
William Zinsser
All
around $20
What the book teaches
The book is in four parts: principles, methods, forms and attitudes. The principles are the part most useful to engineers:
- Simplicity: say what you mean in the fewest clear words.
- Clutter: strip every word that does no work. Zinsser's famous line is that clutter is the disease of American writing.
- Style: be yourself on the page; do not imitate a formal voice.
- The audience: write for a reader, but also for yourself, so the writing stays honest.
- Words and usage: prefer short, concrete words to jargon.
- Unity: pick one tense, one voice and one point per piece.
- The lead and the ending: get the reader in quickly; stop when you are done.
- Rewriting: the real work of writing happens in revision.
The later parts cover forms such as interviews, travel writing, science and technology writing, business writing, sports and memoir. The chapter on writing about science and technology is directly relevant.
Why engineers should read it
Much of a senior engineer's influence depends on writing: design proposals, architecture decisions, incident reports, pull request descriptions, status updates and messages to non-engineers. Clear writing gets decisions made faster. Unclear writing creates meetings.
Reception
On Goodreads it has an average of 4.24 out of 5 from about 31,700 ratings as of September 2026. Readers consistently praise its clarity and warmth. A common criticism is that its examples lean towards journalism and magazine writing rather than technical or business documents, so you have to translate the lessons yourself.
How to use it
- Read the principles part first, about a third of the book, in a few sittings.
- Take one recent document you wrote, such as a README or design doc, and cut it by a third following the clutter chapter.
- Read the science and technology chapter before your next technical explanation for a wider audience.
- Pair it with Google's technical writing courses for engineering-specific practice.
Which edition
The current widely available edition is the 30th anniversary edition, published by Harper Perennial in paperback and as an ebook. Older editions are fine to read too, since the principles chapters have changed little.
Common questions
Is it outdated? The examples are older and American, but the principles have not changed.
Is it only for native English speakers? No. Its preference for short, plain words makes it especially useful for people writing in a second language.
How long does it take? The principles section takes a few hours. The rest can be read over time.
Best for: engineers and students who want to write clearer documents, proposals and messages.
Ready to start?
Opens on William Zinsser in a new tab.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
Follow along
New writing, resources and project ideas land here first.