Blog writing voice guide

Structure

Open with a personal observation or frustration, not a definition. The reader should nod before they learn anything.
Build the “why” through narrative, then deliver the “what” and “how” concisely once the reader already cares.
End short. No summary paragraph restating what was just said. Close with one clean thought.

First person but not self-indulgent. “I” is used to establish credibility and shared experience, not to center yourself.
Confident without being prescriptive. State things directly (“The signal-to-noise ratio goes from terrible to perfect”) rather than hedging (“you might find that…”).
No filler phrases. No “In this post I will…” or “Let’s dive in.” Every sentence earns its space.

Short sentences for impact. Longer ones for explanation. Alternate between them.
No em dashes. Recast asides as their own sentence, or set them off with commas or a colon.
Fragments are fine when they land a point. “That’s it.” “Every line is marked as changed.”

Show before you explain. Examples appear before rules, so the reader already understands the value by the time they see the spec.
Quote primary sources and let them do the heavy lifting. Frame them, don’t paraphrase them.
Lists and code blocks for scannable reference, but only after the narrative has done its job.

Rhetorical questions used as transitions (“But what if there was a better way?”)
Superlatives and hype (“amazing”, “game-changing”)
Explaining things the reader already knows (what Markdown is, what a diff is)
Apologizing for the post’s existence or length

Patterns that read as machine-generated. If a sentence could open any post on any topic, cut it.

Em dashes, especially in contrast constructions
Negation-contrast constructions (“Not a pilot, not a slide deck, but a system”)
“It’s not just X, it’s Y” (“It’s not just a tool, it’s a mindset”)
Alliterative parallelism (“what sticks and what stalls”)
Triads of punchy fragments used for emphasis (“No pilots. No decks. Just systems.”)
Rule-of-three adjective lists (“clear, concise, and compelling”)
Throat-clearing qualifiers (“It’s important to note”, “It’s worth mentioning”)
Formal connectors starting sentences (“Moreover”, “Furthermore”, “Additionally”)
Summary closers (“In conclusion”, “Ultimately”, “At the end of the day”)
Scene-setting openers (“In today’s fast-paced world”, “In the ever-evolving landscape of”)
Audience-widening constructions (“Whether you’re a founder or an engineer”)
LLM vocabulary (“delve”, “leverage”, “robust”, “seamless”, “crucial”, “comprehensive”, “landscape”, “journey”)
Personifying concepts (“AI is transforming the way we work”)
Bolding random phrases mid-sentence for fake emphasis
Colon-headline formulas (“AI Adoption: Why It Matters”)
Uniform rhythm. Every sentence the same length, every paragraph three sentences. Human writing is uneven.

Use semantic line breaks. Start a new line after each sentence. Split long sentences at natural clause boundaries: commas, semicolons, colons, conjunctions. The rendered output stays the same; only the source changes.

Write like you’re explaining something to a peer at a bar, not presenting to a conference audience.