Writing & Delivery: The Craft of EditingStructure first · Kill your darlings · Consistency · The author relationship
BigCat's Writing
Good writing is rarely written—it's rewritten. And rewriting has its own discipline: skeleton before sentences, the nerve to cut your favorite line, making the whole thing sound like one person, and—when you edit others or yourself—the fine line between helping and overstepping. Today, the invisible craft.
Principle 01
Skeleton First, Sentences Last: The Order of Editing
Macro-Editing before Micro-Editing
Editing · Order
The Principle
Editing has an order. Look at structure first (should this section exist, is the sequence right, does the argument hold), then the sentences (word choice, rhythm, punctuation). Reverse it and you'll spend two hours polishing a paragraph you're about to delete whole.
"Rewriting is the essence of writing well: it's where the game is won or lost. ... Few people realize how badly they write."
— William Zinsser, On Writing Well
Pass 1StructureShould it exist · Sequence · Does the argument hold
↓
Pass 2ParagraphsOne idea each · Transitions
↓
Pass 3SentencesRhythm · Active voice · Cut clutter
↓
LastWords & PunctuationTerm consistency · Typos
Edit top-down—touch an upper layer and a lower one may vanish entirely
Why It Works
Editing comes in two kinds: macro-editing handles the whole—cutting, reordering, shoring up the argument; micro-editing polishes line by line. Doing micro first is the most common waste: you carve a passage into a jewel, then realize it shouldn't be there at all. Set the bones first, then add flesh, and what gets cut won't hurt.
Edit in Action
A budget-request email, every sentence buffed: "After a thorough and careful evaluation, weighing considerations upstream and down..." Three paragraphs of runway, then the ask in the last line: "Please approve $300K."Structural edit moves "Please approve $300K for X; three reasons follow" to sentence one, background squeezed to two lines. If that lovely runway sentence sat in a deleted paragraph, lovely or not, it was carved for nothing.
A report polished sentence-by-sentence, but the conclusion sits in paragraph 6.Move the conclusion to the top first; then decide which of the 5 lead-in paragraphs survive. Polish only the survivors.
When to Use + Common Mistakes
✓ Any long piece you revise: design docs, memos, PRDs, talks, blog posts
✗ Fixing typos and word choice first—precision-tuning text that might still be deleted whole
✗ Refusing to touch structure because you "can't bear to lose" a just-polished sentence
Key References
Susan Bell, The Artful Edit (macro / micro passes) · William Zinsser, On Writing Well · Sol Stein, Stein on Writing
This Week's Exercise + Question
Take an old piece of yours and do one thing: write its core claim in a single sentence. Then ask of each paragraph, "Does this serve that sentence?" Delete every one that doesn't—this pass only cuts, never polishes. Question: can you make the cuts? If not, is it that you love the prose, or that you never settled what the core actually is?
Principle 02
Kill Your Darlings
Murder Your Darlings
Editing · Cutting
The Principle
The line you're proudest of, the most ornate, the one you least want to lose—that's usually the one to cut. Because you're keeping it for yourself (to show off, out of attachment), not for the reader.
"Whenever you feel an impulse to perpetrate a piece of exceptionally fine writing, obey it—whole-heartedly—and delete it before sending your manuscript to press. Murder your darlings."
— Arthur Quiller-Couch, On the Art of Writing (1916)
Stephen King turned this line into every writer's most familiar mantra in On Writing.
Why It Works
A darling makes the reader notice "what a writer," not "what a point"—it shines the light on you and away from the message. Sunk cost makes you cling: you spent the most effort on this line, so you most want to keep it. Lu Xun set the harshest yardstick: "After finishing, read it through at least twice, and ruthlessly delete every dispensable word, sentence, and paragraph—without the slightest regret." Note "without regret"—the more it hurts to cut, the more it's worth checking whether it's a darling.
Edit in Action
"In an age where information surges like a tide and algorithms devour attention like beasts, each of us is a small boat on a digital ocean..." (then, finally, the topic: caching strategy)"Caching can make an endpoint 10× faster—and make data wrong, silently. Here are the trade-offs among three strategies." The "small boat on a digital ocean" was the author's proudest line. Precisely why it goes.
Like a phoenix rising from the ashes of legacy code, our new system breathes life into a once-dying stack...Our new system cut p99 latency from 800ms to 120ms. Here's how.
When to Use + Common Mistakes
✓ Ornate openings, pet metaphors, quotable lines—before keeping, ask "is this for the reader or for me?"
✗ Misreading "kill darlings" as "strip all color," writing a dry spec sheet—a good sentence that serves the reader is not a darling
✗ Cutting before you've seen the whole, leaving it in fragments
Key References
Arthur Quiller-Couch, On the Art of Writing · Stephen King, On Writing · Lu Xun, Reply to Beidou Magazine
This Week's Exercise + Question
Dig out a passage you secretly think "reads beautifully," cut it out to the side, and read what remains—did the meaning weaken? Usually not. Question: where's the line between a darling and a genuinely good sentence? One test: cut a good sentence and the meaning collapses; cut a darling and only you feel the loss.
Principle 03
Sounding Like One Person: Consistency
Consistency — One Voice, One Vocabulary
Editing · Consistency
The Principle
One concept, one word throughout; one kind of thing, one format throughout. Inconsistency makes the reader quietly wonder "are these two different things?"—a hidden cognitive tax levied beneath the prose.
"A foolish consistency is the hobgoblin of little minds."
— Ralph Waldo Emerson, Self-Reliance (1841)
Emerson is attacking rigidity of thought. But at the surface of the prose, mechanical consistency (terms, format, voice) is exactly what spares the reader. Be consistent on the surface; be free in the thinking.
Why It Works
Every time a term shifts, the reader must stop to decide "is this a new concept or the old one renamed?" That tiny pause, multiplied across the piece, is real reading friction. Consistency isn't pedantry; it frees the reader's effort from "decoding" for "understanding." The mark of a pro is a style sheet—even a ten-line one.
Edit in Action
One doc mixing "user / customer / end-user / the user side" for the same group; "log in / login / sign in" alternating; numbers as "5" then "five."Standardize: people → "user," the action → "sign in," numbers → digits in body text. Add a ten-line term table up front, align before co-writing.
Mixing "log in" / "login" / "sign in"; "e-mail" / "email"; "Q3" / "third quarter" in one doc.Pick one each ("sign in" v., "email", "Q3") and write a one-line style sheet. The Chicago Manual exists for exactly this.
When to Use + Common Mistakes
✓ Technical docs, API docs, product copy, long collaborative documents
✗ Co-writing without a style sheet—everyone's own labels, reader left assembling a jigsaw
✗ Over-consistency: "fixing" even the varied spellings inside a quotation, breaking fidelity—exactly Emerson's "foolish consistency"
Key References
The Chicago Manual of Style (the authority on consistency) · Strunk & White, The Elements of Style · Ralph Waldo Emerson, Self-Reliance
This Week's Exercise + Question
Pick a team document, list every place where the same thing is named differently, build a term table, and unify the whole piece. Question: which consistencies belong to tools and a style guide (spelling, format), and which can only be done by a human (voice, level of detail)? Why is the latter so hard to automate?
Principle 04
Help Without Overstepping: The Author Relationship
The Editor as Servant, Not Author
Editing · Restraint
The Principle
The editor's highest art is making the work what the author wanted to write, not what you would have written. Edit with questions, not commands; fix the reader's snags, not the author's voice.
"An editor does not add to a book. At best he serves as a handmaiden to an author. ... An editor at most releases energy. He creates nothing."
— Maxwell Perkins, in A. Scott Berg, Max Perkins: Editor of Genius
Perkins was the legendary editor behind Hemingway and Fitzgerald.
Why It Works
Two failures, opposite directions: under-editing—a rubber stamp, all praise no cut; over-editing—turning the author into yourself. The famous case is Gordon Lish, who slashed and rewrote Raymond Carver until it nearly became a different writer. Perkins's "handmaiden" is the yardstick at the other end: your job is to amplify the author's voice, not replace it. The test is simple—after editing, is this still the author's piece?
Edit in Action
(Commanding, ego-bruising) This paragraph is a mess. Rewrite it. This metaphor is bad.(Question-based, from the reader's seat) I lost the thread here—are you saying X? If so, would leading with the conclusion help? I didn't get this metaphor right away—are you stressing speed or scale?
"This is confusing. Rewrite it.""I lost the thread here—is the core claim that X? If so, leading with it might help."
This is query editing: leave the judgment with the author. Self-editing is the same—wear both hats, but at different times: be the author while writing, the reader while revising. Never both at once.
When to Use + Common Mistakes
✓ Code review, editing a report for a report, revising a PRD, peer review, self-revision
✗ Treating editing as a chance to "prove I'm smarter"
✗ Editing the author's style into your taste (over-editing), or only liking without cutting (under-editing)
Key References
A. Scott Berg, Max Perkins: Editor of Genius · Betsy Lerner, The Forest for the Trees · Ye Shengtao (the editor who reads as the reader)
This Week's Exercise + Question
Take a piece by someone else (or your own draft from a week ago) and write three edit notes, all phrased as questions ("Could you...", "Would it help to..."), with no "change this" or "rewrite." Question: Perkins's "handmaiden" versus Lish reshaping Carver—who's right? Who gets to decide where an editor's overreach begins?
Going Deeper
Don't "kill your darlings" and "sentences should have rhythm and color" contradict each other?
No, because the test is "whom does it serve." A good sentence and a darling may be equally lovely; the difference is function. Cut a good sentence and the meaning collapses, the emotion breaks, the rhythm limps; cut a darling and only the author feels the loss, the reader none. Color isn't a sin—color kept to show off is. A practical check: lift the line out and read what remains; if it flows, even reads cleaner, it was a darling. So this rule doesn't oppose fine prose—it opposes dressing the author's vanity up as the reader's need.
Self-editing is hardest because you're both author and editor. What lets you cut yourself?
The key is manufacturing "distance" so the critical you isn't the writing you. Three mechanisms: time—set it aside a night or a week, and once the heat fades the darlings reveal themselves; change the medium—print it, switch fonts, read it aloud (the ear is more honest than the eye; clunky sentences expose themselves on a read); switch roles—declare "right now I'm the reader, not the author," even picture a specific, picky reader across the table. All of it separates the creating self from the judging self in time or space, so they can't be present at once to cover for each other.
AI can already do copyediting (grammar, consistency, typos). What editing work is left for humans?
AI takes over precisely the micro layer and mechanical consistency—rule-bound work—which is good; it frees humans from proofreading. What's left is the three things AI still does poorly: structural judgment, deciding "should this section exist at all," which needs the whole intent and the reader's situation; preserving voice—AI tends to sand everything into the same smooth "correct," erasing the author's individuality, and spotting and keeping a unique voice is human work; and the author relationship—asking, empathizing, restraint, which is interpersonal. In short: AI is the copyeditor; the human is the developmental editor and the one who knows the "handmaiden" line.
Mechanical consistency goes to tools, but "voice consistency" resists automation. What even is consistent voice?
Voice isn't single-word choice; it's a whole posture: preferred sentence length, distance to the reader (do you say "you"?), the ratio of serious to playful, first person or not, the nerve to keep dashes and short sentences. It's consistent because a stable "person speaking" sits behind it. It resists automation because it emerges from countless micro-decisions with no enumerable rules; changing one word won't break it, but converting all the spoken cadences to formal prose will. The way to guard voice isn't a rule table—it's repeatedly asking "is this the same person speaking?" and deliberately keeping the author's signature little habits while you revise.
How does the craft of editing shift across the page, the talk, and video?
Structural editing is universal and most important in all three. The differences are in the micro layer and how you test. Text works on the eye and can be re-read, so consistency, terms, and punctuation reward full polish. A talk works on the ear and can't be replayed, so editing serves hearing—cut subordinate clauses, split long sentences, swap jargon for plain words, use repetition as a memory hook; the test is to stand up and read it aloud. Video/audio adds a layer where "the cut is the edit"—you delete not just words but time and pauses, pace is set by duration, and the darling here is "the great shot/bit you can't bear to cut." The more linear and un-rewindable the medium, the higher the payoff of ruthless cutting.