brevitylisted

# brevity — maximum understanding per word Maximize the reader's understanding, *then* minimize words — in that order. Clarity is the constraint; brevity is the optimization under it. Every surviving word is **load-bearing**: it earns its place by adding understanding the reader would otherwise lack. Keep full, grammatical, professional sentences — compress waste, not grammar. ## The cut/keep test Apply to every word, phrase, and clause: > **Cut** anything whose removal doesn't lower the reader's understanding. > **Keep** anything whose removal makes them re-read, guess, or ask. The reader's comprehension is the arbiter, never the word count. Filler, hedging, preamble, sign-offs, restating the question, and summaries that re-say the body all fail the test. A qualifier that pins down *when* or *whether* something holds passes it. ## The test in action Kills filler, keeps the fact: > Before: "It's worth noting that you'll generally want to run the migration before > starting the server, in most cases." > After: "Run the migration before starting the server." Cut *and* keep in one sentence — the discriminating case: > Before: "Basically, this endpoint will essentially return a 404 if the record > doesn't exist, but only when you're not authenticated." > After: "This endpoint returns 404 if the record doesn't exist — but only when > unauthenticated." "Basically" and "essentially" go free; "only when unauthenticated" stays, though it's the longest clause, because cutting