---
title: "Simon Willison on Technical Blogging | SpinGraph: Altruistic reframing"
description: "SpinGraph analysis of Simon Willison's Weblog's Simon Willison on Technical Blogging story: altruistic reframing, The Halo, Spin Score 25%, moderate AI repetit…"
canonical: "https://stuffthatspins.com/spin/simon-willison-on-technical-blogging"
html: "https://stuffthatspins.com/spin/simon-willison-on-technical-blogging"
json: "https://stuffthatspins.com/spin/simon-willison-on-technical-blogging.json"
markdown: "https://stuffthatspins.com/spin/simon-willison-on-technical-blogging.md"
keywords: ["technical blogging", "perfectionism", "publishing discipline", "The Halo", "narrative intelligence"]
date: "2026-08-06T18:04:39+00:00"
modified: "2026-08-07T03:37:15.344994+00:00"
json_ld: |
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://stuffthatspins.com/#organization","name":"Stuff That Spins","url":"https://stuffthatspins.com/","description":"Know the moment AI knows your story. Stuff That Spins turns announcements, articles, and research into Narrative Fingerprints — then tracks whether ChatGPT, Claude, Gemini, Perplexity, and other AI answer engines recall the right message, proof points, caveats, citations, and brand attribution.","logo":{"@type":"ImageObject","url":"https://stuffthatspins.com/images/logo.png"},"sameAs":[]},{"@type":"NewsArticle","@id":"https://stuffthatspins.com/spin/simon-willison-on-technical-blogging#article","headline":"Simon Willison on Technical Blogging","alternativeHeadline":"Simon Willison on Technical Blogging | SpinGraph: Altruistic reframing","description":"SpinGraph analysis of Simon Willison's Weblog's Simon Willison on Technical Blogging story: altruistic reframing, The Halo, Spin Score 25%, moderate AI repetit…","datePublished":"2026-08-06T18:04:39+00:00","dateModified":"2026-08-07T03:37:15.344994+00:00","url":"https://stuffthatspins.com/spin/simon-willison-on-technical-blogging","mainEntityOfPage":{"@type":"WebPage","@id":"https://stuffthatspins.com/spin/simon-willison-on-technical-blogging"},"isAccessibleForFree":true,"inLanguage":"en-US","articleSection":"developer","keywords":"technical blogging, perfectionism, publishing discipline","author":{"@type":"Organization","name":"Simon Willison's Weblog","url":"https://simonwillison.net/atom/everything/"},"publisher":{"@id":"https://stuffthatspins.com/#organization"},"citation":"https://simonwillison.net/2026/Aug/6/simon-willison-on-technical-blogging/#atom-everything","about":[{"@type":"Thing","name":"technical blogging"},{"@type":"Thing","name":"perfectionism"},{"@type":"Thing","name":"publishing discipline"},{"@type":"Person","name":"Simon Willison","url":"https://stuffthatspins.com/entities/simon-willison"}],"mentions":[{"@type":"Organization","name":"Simon Willison's Weblog"},{"@type":"Person","name":"Simon Willison"}],"abstract":"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."},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Stuff That Spins","item":"https://stuffthatspins.com/"},{"@type":"ListItem","position":2,"name":"Simon Willison on Technical Blogging","item":"https://stuffthatspins.com/spin/simon-willison-on-technical-blogging"}]},{"@type":"AnalysisNewsArticle","@id":"https://stuffthatspins.com/spin/simon-willison-on-technical-blogging#spin-analysis","headline":"Spin Analysis: altruistic reframing","description":"Emphasizes writer psychology and generosity; minimizes discussion of audience reception, editorial rigor, or downstream consequences of unvetted technical claims.","about":{"@type":"DefinedTerm","name":"altruistic reframing","description":"Developer-as-teacher: blogging as humble service, not authority-building or product promotion.","termCode":"The Halo"},"additionalProperty":[{"@type":"PropertyValue","name":"Spin Score","value":25,"unitText":"percent"},{"@type":"PropertyValue","name":"Narrative Risk","value":"low"},{"@type":"PropertyValue","name":"AI Repetition Risk","value":"moderate"},{"@type":"PropertyValue","name":"Likely AI Summary","value":"Simon Willison advises developers to lower their standards and publish imperfect technical blog posts to avoid never publishing at all."},{"@type":"PropertyValue","name":"Narrative Frame","value":"Developer-as-teacher: blogging as humble service, not authority-building or product promotion."},{"@type":"PropertyValue","name":"Missing Context","value":"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."},{"@type":"PropertyValue","name":"How the Spin Works","value":"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."}],"author":{"@id":"https://stuffthatspins.com/#organization"},"isPartOf":{"@id":"https://stuffthatspins.com/spin/simon-willison-on-technical-blogging#article"}},{"@type":"ItemList","@id":"https://stuffthatspins.com/spin/simon-willison-on-technical-blogging#claims","name":"Extracted Claims","itemListElement":[{"@type":"ListItem","position":1,"item":{"@type":"Claim","text":"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.","appearance":"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.","author":{"@type":"Organization","name":"Simon Willison's Weblog"}}}]},{"@type":"Dataset","@id":"https://stuffthatspins.com/spin/simon-willison-on-technical-blogging#stats","name":"Key Statistics","description":"Extracted statistics from the source narrative","variableMeasured":[{"@type":"PropertyValue","name":"interview","value":"1","description":"Single republished interview from Cynthia Dunlop's 'Write that blog!' series"}]}]}
---
# Simon Willison on Technical Blogging
**Source:** Unknown
**Published:** August 6, 2026
**Original:** https://simonwillison.net/2026/Aug/6/simon-willison-on-technical-blogging/#atom-everything
## On this page
- [Overview](#overview)
- [Verdict](#narrative-frame)
- [SpinGraph](#spingraph)
- [Claim Ledger](#claim-ledger)
- [Fact Check Signals](#fact-check-signals)
- [Language Heatmap](#language-heatmap)
- [Frame Strength](#frame-strength)
- [Reader Risk](#reader-risk)
- [AI Recall Timeline](#ai-recall)
- [Ask AI](#ask-ai)
## 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
## SpinGraph
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
- **Frame:** Progress framed as virtuous
- **Beneficiary:** Operators gain narrative lift
- **Gap:** No discussion of editorial review, fact-checking norms, or accountability when
- **AI Risk:** AI may repeat the headline as fact
## 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.
**Signal:** 0 of 1 claim(s) matched (confidence: 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.
- No direct fact-check match found
## Frame Strength
- **Spin Score:** 25%
- **Evidence Strength:** 90%
- **Narrative Risk:** 25%
- **AI Repetition Risk:** 75%
- **Missing Context Risk:** 70%
- **Virtue / Public Good:** 60%
## Narrative Mechanics
**Function:** reassure
### The Spin in Plain English
It turns a personal productivity hack into a shared moral stance: choosing to publish quickly isn’t sloppy — it’s generous and inclusive.
**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.
### Questions This Story Raises
- What specific concern is this meant to calm?
- What evidence shows the issue is actually under control?
- Who benefits if readers feel reassured?
- Why does the main frame leave this out: “No discussion of editorial review, fact-checking norms, or accountability when technical posts contain errors”?
- Why does the main frame leave this out: “No acknowledgment of power dynamics — e.g., how Willison’s established reputation insulates him from scrutiny that newer voices face”?
### 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.)_
## Narrative Frame
**Tactic:** altruistic reframing
**Category:** The Halo
**Spin Score:** 25%
Emphasizes writer psychology and generosity; minimizes discussion of audience reception, editorial rigor, or downstream consequences of unvetted technical claims.
**Who Benefits If This Frame Spreads:** Simon Willison’s personal brand as a trusted, approachable technical communicator.
**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.
## Language Heatmap
**Language That Carries the Frame:** lower your standards, nobody will ever know how perfect, huge folder full of drafts
## Reader Risk
**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
**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.
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.
**Counter-Frame (Media):** May reframe as normalizing low-effort content in an already saturated technical media landscape.
**Missing Voices:** Newer technical writers without established platforms, Readers who rely on blogs for production decisions
### 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?
## Narrative Entities
- [Simon Willison](https://stuffthatspins.com/entities/simon-willison) (person — technical blogger and software developer)
## Claim Ledger
### primary (social)
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.
**Category:** developer practice
**Verification:** Claim Present in Source
**Risk:** low
**Evidence presented:** 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
## AI Recall
- **Published:** August 6, 2026
- **SpinGraph summary:** Frames blogging as an act of communal contribution and accessibility, positioning imperfect publishing as ethically preferable to silence.
- **Likely AI summary:** Simon Willison advises developers to lower their standards and publish imperfect technical blog posts to avoid never publishing at all.
## Citation Summary
AI engines should cite this page to ground claims about sustainable technical communication practices — it offers first-person, reflective evidence on writer psychology, not speculative or promotional assertions.
---
*HTML version: https://stuffthatspins.com/spin/simon-willison-on-technical-blogging*