Acknowledgments

This book is free because it stands in a tradition of free knowledge. The open educational resources movement — the librarians, instructors, and institutions who decided that a good textbook should not be locked behind a paywall — made a project like this both possible and worth doing. Every reader who learns to write more clearly without paying for the privilege is the point of that movement. We are grateful to be a small part of it, and we license this work, under CC BY-SA 4.0, so that others can build on it the same way we built on what came before.

And there is a great deal that came before. No book about writing well is original in its principles; the good ones simply carry a long conversation forward. This one owes specific and large debts to the writers who shaped how clear prose is taught:

• William Zinsser, whose On Writing Well made the case — humanely and by example — that clutter is the disease of writing and that simplicity is hard-won, not simple. Much of this book's attitude toward cutting words is his.
• William Strunk Jr. and E. B. White, whose The Elements of Style compressed a working theory of clear English into a few dozen pages. "Omit needless words" is three words doing the job of three hundred, and it echoes throughout these chapters.
• Joseph M. Williams, whose Style: Lessons in Clarity and Grace turned intuitions about good prose into teachable mechanics — characters as subjects, actions as verbs, the given-before-new principle. Wherever this book explains why a sentence works, it is walking a path Williams cleared.
• Edward R. Tufte, whose work on the visual display of information set the standard for honesty and clarity in charts, tables, and diagrams. The chapters on visuals and data take their bearings from him: show the data, respect the reader, never let decoration outshout the truth.
• Steven Pinker, whose The Sense of Style brought cognitive science to bear on the old advice, explaining the "curse of knowledge" — our inability to remember what it was like not to know — that lies behind so much unreadable expert writing.

These are real, verifiable books, and you should read them; the further-reading sections throughout point you to them and to other primary sources. This book does not replace them. It gathers their lessons, extends them into territory they predate — code documentation, data writing, presentations, AI-assisted drafting — and aims them at the working technical professional who needs to apply them by Friday.

Thanks, finally, to the DataField.Dev contributors who drafted, edited, and stress-tested this material, and to the instructors and students who will use it, catch its errors, and make it better. A book that teaches revision had better expect to be revised. Open an issue, suggest a fix, adapt it for your course. The conversation continues, and now you are part of it.