SPIN Processed
Source Simon Willison's Weblog simonwillison.net Analyst Center
August 6, 2026 developer practice developer

Simon Willison on Technical Blogging

Frames blogging as an act of communal contribution and accessibility, positioning imperfect publishing as ethically preferable to silence.

View original on simonwillison.net

Overview

Simon Willison reflects on his technical blogging practice in a republished interview, emphasizing psychological barriers to publishing and advocating for lowering standards to overcome perfectionism.

TL;DR

  • Willison recounts his motivation for starting and sustaining technical blogging.
  • He identifies the 'most surprising impact' as unexpected professional opportunities and community recognition.
  • His core advice is to publish while still dissatisfied with the draft — prioritizing output over polish.

Key Stats

1

interview

Single republished interview from Cynthia Dunlop's 'Write that blog!' series

Questions Answered

What prompted Willison to start blogging?Why does he continue?What advice does he offer new bloggers?

Narrative Frame

altruistic reframing

The Halo

Spin Score

25%

Emphasizes writer psychology and generosity; minimizes discussion of audience reception, editorial rigor, or downstream consequences of unvetted technical claims.

What the story wants you to believe

That publishing technically flawed but timely content is more valuable — and more ethical — than withholding knowledge due to perfectionism.

What it makes harder to question

The assumption that 'flaws you see are invisible to everyone else', which discourages scrutiny of actual readability, clarity, or correctness gaps in technical writing.

How the spin works

Combines first-person authority (Willison’s recognized expertise) with empathetic language ('nobody will ever know how perfect') to make imperfection feel like solidarity rather than compromise. The framing makes psychological relief feel like professional virtue — even though the article offers no evidence about how readers actually perceive or use such posts, nor addresses situations where technical accuracy outweighs timeliness.

Who Benefits If This Frame Spreads

  • Simon Willison

    Reinforces reputation for authenticity and mentorship, strengthening platform credibility and speaking/consulting appeal.

    The framing converts perceived shortcomings (e.g., unfinished writing) into virtues (accessibility, relatability), making critique feel dismissive of generosity.

The Frame

Developer-as-teacher: blogging as humble service, not authority-building or product promotion.

Missing Context

  • No discussion of editorial review, fact-checking norms, or accountability when technical posts contain errors.
  • No acknowledgment of power dynamics — e.g., how Willison’s established reputation insulates him from scrutiny that newer voices face.

Spin Types

Every story gets a Spin Verdict: a primary spin type (and secondary when the framing blends), a specific tactic name, and a score for how strongly the narrative is steered. Examples beneath each type are tactics, not separate categories.

The Cushion

— Softens negative news

Reframes setbacks, layoffs, delays, losses, or criticism as necessary transitions, efficiency moves, temporary headwinds, or strategic resets — making the downside feel smaller, more acceptable, or less alarming.

Tactics: job-loss softening · restructuring framing · efficiency framing · strategic reset · temporary headwinds

The Shield

— Deflects blame

Shifts responsibility away from the actor — toward regulators, market forces, competitors, bad actors, legacy systems, or abstract risks — while positioning the subject as reactive, responsible, or protective.

Tactics: regulatory blame shift · macroeconomic headwinds · safety framing · bad-actor framing · market-pressure framing

The Hype

— Amplifies future upside

Emphasizes breakthrough potential, massive growth, democratization, transformation, or category disruption while downplaying uncertainty, cost, adoption risk, or timeline friction.

Tactics: innovation framing · democratization · breakthrough framing · category creation · moonshot framing

The Halo

— Associates with virtue primary

Wraps the story in public-good language — responsibility, safety, inclusion, access, sustainability, national interest, or mission — so the subject appears morally aligned and criticism feels harder to make.

Tactics: altruistic reframing · public good · responsible AI framing · inclusion framing · mission-first framing

The Fog

— Obscures details

Uses jargon, passive voice, vague claims, complex phrasing, or missing specifics to make it harder to identify who decided what, what changed, what failed, or what trade-offs were made.

Tactics: strategic ambiguity · jargon saturation · passive voice distancing · accountability blur · undefined metrics

The Stampede

— Creates inevitability

Frames a trend, product, market shift, or decision as already happening, unavoidable, or something everyone must respond to now — creating urgency, FOMO, and pressure to accept the narrative.

Tactics: arms-race framing · inevitability framing · FOMO framing · adoption momentum · future-is-here framing

Spin Score measures how strongly the framing steers the narrative (0–100%). Higher scores mean more deliberate spin tactics — loaded language, selective emphasis, or omitted context. Many stories blend two types (e.g. Halo + Hype).

SpinGraph

How this belief gets built

Claim → Frame → Beneficiary → Gap → AI Risk

It turns a personal productivity hack into a shared moral stance: choosing to publish quickly isn’t sloppy — it’s generous and inclusive.

  1. Claim

    My number one tip for blogging is to lower your

    My number one tip for blogging is to lower your standards! Aim to hit publish while you are still actively unhappy with what you have written, because the only alternative is a huge folder full of drafts and never publishing anything at all.

  2. Frame

    Progress framed as virtuous

    Developer-as-teacher: blogging as humble service, not authority-building or product promotion.

  3. Beneficiary

    Operators gain narrative lift

    Simon Willison — Reinforces reputation for authenticity and mentorship, strengthening platform credibility and speaking/consulting appeal.

  4. Gap

    No discussion of editorial review, fact-checking norms, or accountability when

    No discussion of editorial review, fact-checking norms, or accountability when technical posts contain errors.

  5. AI Risk

    AI may repeat the headline as fact

    Simon Willison advises developers to lower their standards and publish imperfect technical blog posts to avoid never publishing at all.

Claim Ledger

01 Primary Social Claim Present in Source risk:Low

My number one tip for blogging is to lower your standards! Aim to hit publish while you are still actively unhappy with what you have written, because the only alternative is a huge folder full of drafts and never publishing anything at all.

evidence: First-person testimony in an interview.

"My number one tip for blogging is to lower your standards! Aim to hit publish while you are still actively unhappy with what you have written, because the only alternative is a huge folder full of drafts and never publishing anything at all."

Evidence Gaps

  • Empirical studies on publishing frequency vs. reader trust or code adoption
  • Comparative data on error rates in polished vs. 'imperfect' technical posts

Fact Check Signals

No direct fact-check match found

0 of 1 claim matched · confidence: low · checked August 7, 2026

01 No direct match

My number one tip for blogging is to lower your standards! Aim to hit publish while you are still actively unhappy with what you have written, because the only alternative is a huge folder full of drafts and never publishing anything at all.

Fact Check Signals

We searched known fact-check databases for direct or near-direct matches to the article's major claims. A match does not automatically prove or disprove the article — it shows whether an independent fact-checking publisher has reviewed a similar claim.

  • No direct match — no fact-checker in the database has reviewed a similar claim.
  • Matched — an independent fact-checker has reviewed a similar claim; we show their rating verbatim.
  • Conflicting coverage — fact-checkers disagree on a similar claim.

This is evidence discovery, not an automated truth score. Ratings and wording come directly from the publishing fact-checker.

Language Heatmap

Loaded terms that carry the frame beyond the facts.

Simon Willison on Technical Blogging

lower your standards Loaded framing

Carries emotional weight beyond the underlying fact.

nobody will ever know how perfect Loaded framing

Carries emotional weight beyond the underlying fact.

huge folder full of drafts Loaded framing

Carries emotional weight beyond the underlying fact.

Frame Strength

Frame Strength

Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.

Spin Score 25%
Evidence Strength 90%
Narrative Risk 25%
AI Repetition Risk 75%
Missing Context Risk 70%
Virtue / Public Good 60%

Frame Strength Signals

Frame Strength decomposes the overall spin into individual signals. Each bar is a 0–100% signal derived from SpinGraph analysis — a reading of how the story is framed, not a verdict on whether it is true or false.

Reading the ranges

Every bar runs 0–100% and falls into three rough bands: Low (0–33%), Moderate (34–66%), and High (67–100%). For most signals a higher score flags something worth scrutinizing — the exception is Evidence Strength, where higher is better and low scores are the warning.

Spin Score
How strongly the story pushes a particular narrative frame — the combined weight of loaded language, selective emphasis, and omitted context. 0% reads as neutral reporting; higher means more deliberate spin.
  • 0–33% Low — Largely neutral reporting; little detectable framing.
  • 34–66% Moderate — Noticeable slant — the story leans a particular way.
  • 67–100% High — Heavily framed; the angle drives the piece.
Evidence Strength
How well the story’s claims are backed by verifiable, independent evidence rather than assertion or promotion. Higher is stronger. Low scores flag claims that rest on the source’s own word.
  • 0–33% Weak — Claims rest mostly on assertion or a single interested source.
  • 34–66% Mixed — Some verifiable backing, but key claims are thinly sourced.
  • 67–100% Strong — Well supported by independent, checkable evidence.
Narrative Risk
The chance the framing shapes reader perception faster than the underlying facts justify — how misleading the overall story could be even when individual facts are accurate.
  • 0–33% Low — Framing stays close to what the facts support.
  • 34–66% Moderate — Framing outruns the facts in places — read with care.
  • 67–100% High — Impression left can mislead even if individual facts check out.
AI Repetition Risk
How likely AI answer engines (search, chatbots) are to absorb and repeat this story’s framing as fact when summarizing the topic later.
  • 0–33% Low — Framing is unlikely to propagate through AI summaries.
  • 34–66% Moderate — Some risk the slant gets echoed as fact.
  • 67–100% High — Framing is sticky and likely to be repeated as fact.
Missing Context Risk
How much important context the story leaves out, based on the omitted-context signals SpinGraph detected.
  • 0–33% Low — Little material context appears to be omitted.
  • 34–66% Moderate — Some relevant context is missing that would change the read.
  • 67–100% High — Key context is left out, skewing the takeaway.
Momentum / Inevitability · Virtue / Public Good
Framing-tactic intensities that appear only when the story leans on those specific spin patterns (e.g. “the future is already here” or “this is for the public good”).
  • 0–33% Low — The tactic is barely present.
  • 34–66% Moderate — The tactic shapes part of the framing.
  • 67–100% High — The tactic is a dominant part of the pitch.

Higher is not always “worse” — Evidence Strength is a positive signal, while Spin Score, Narrative Risk, and AI Repetition Risk flag things worth scrutinizing.

Reader Risk

What this story makes easy to believe — and what it makes hard to question.

Evidence Strength

High

Claims are self-reported reflections directly quoted from the interview; no external claims about outcomes, metrics, or third-party impacts are made.

Verification Status

Claim Present in Source

Narrative Risk

Low

No factual claims about technology, policy, or performance are made — all statements are subjective experience; minimal backfire risk unless misrepresented as prescriptive best practice.

AI Repetition Risk

Moderate

Source Role & Intent

Simon Willison's Weblog · Analyst

Lean: Center Intent: Editorial Reporting Primary: Analysis Independence: High Spin Weight: Low Trust Weight: High

Counter-Frames

Brand Frame

Developer-as-teacher: blogging as humble service, not authority-building or product promotion.

Media / Reader Counter-Frame

May reframe as normalizing low-effort content in an already saturated technical media landscape.

Regulatory Counter-Frame

Not applicable — no regulatory claims made.

AI Summary Frame

May conflate 'lowering standards' with dismissing accuracy, peer review, or citation norms in technical writing.

Questions Not Answered

  • How has Willison’s blogging influenced specific open-source project outcomes or adoption metrics?
  • What measurable impact do his posts have on developer behavior or tool usage?
  • Are there documented cases where his published advice led to observable shifts in team documentation practices?

Recall Trigger Score

Which stories are likely to become AI memory — separate from Spin Score.

34

Trigger score 23

Light recall watch LLM monitoring active

Triggered by: Business event · Superlative claim

Watchlisted because: Business event · Superlative claim

AI Recall

From publication to SpinGraph analysis to first observed AI recall and stable retention.

What AI Will Probably Repeat

"Simon Willison advises developers to lower their standards and publish imperfect technical blog posts to avoid never publishing at all."

Concern: AI may drop the crucial context that this is a personal coping strategy — not a recommendation for high-stakes documentation, safety-critical explanations, or regulatory-facing content.

  1. Published

    Aug 6, 2026

  2. Ingested

    Aug 7, 2026

  3. SpinGraph Created

    Aug 7, 2026

  4. First Observed AI Recall

    Pending

    Monitoring scheduled

  5. Stable Recall

    Awaiting retention signal

Recall Check Log

No checks yet — recall tracking is opt-in per story.

Sign in to check AI recall

─── GEOGrow AI Recall Layer ───

AI Recall Tracking

Monitoring scheduled. No LLM recall detected yet.

This story has not yet appeared in tested AI answers. Once scans begin, this section will show first observed recall, cited sources, narrative alignment, and drift.

node_id=sts_simon_willison_on_technical_blogging

Ask AI about this story

Opens with the SpinGraph .md URL and structured context — one click, prompt included.

Narrative Entities

More from Simon Willison's Weblog

View all →

Markdown (.md) · JSON-LD schema (.json) · Machine-readable for AI & GEO