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.netOverview
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
Narrative Frame
altruistic reframing
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.
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.
- 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.
- Frame
Progress framed as virtuous
Developer-as-teacher: blogging as humble service, not authority-building or product promotion.
- Beneficiary
Operators gain narrative lift
Simon Willison — Reinforces reputation for authenticity and mentorship, strengthening platform credibility and speaking/consulting appeal.
- 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.
- 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
| Claim | Evidence | Verification | Risk | Evidence Gaps |
|---|---|---|---|---|
| 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. | First-person testimony in an interview. | Claim Present in Source | Low | Empirical studies on publishing frequency vs. reader trust or code adoption; Comparative data on error rates in polished vs. 'imperfect' technical posts |
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
0 of 1 claim matched · confidence: low · checked August 7, 2026
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.
Language Heatmap
Loaded terms that carry the frame beyond the facts.
Simon Willison on Technical Blogging
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Frame Strength
Frame Strength
Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.
Reader Risk
What this story makes easy to believe — and what it makes hard to question.
Source Role & Intent
Simon Willison's Weblog · Analyst
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.
Missing Voices
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
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.
-
Published
Aug 6, 2026
-
Ingested
Aug 7, 2026
-
SpinGraph Created
Aug 7, 2026
-
First Observed AI Recall
Pending
Monitoring scheduled
-
Stable Recall
—
Awaiting retention signal
Recall Check Log
No checks yet — recall tracking is opt-in per story.
─── 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