Simon Willison on Technical Blogging: Lower Your Standards and Publish
Score
67虽是作者本人回顾访谈，但核心建议对技术写作有直接启发，且包含个人实践案例，信息增量中等偏上。
内容来自资深博主的一手经验，表达清晰，观点集中，具备较强的说服力和可读性。
“降低标准”是可立即执行的具体建议，对想开始或坚持写作的开发者有直接帮助。
内容为访谈回顾，无强烈时效性，但写作建议具有长期参考价值。
Simon Willison 是知名技术博主，信源为本人博客，可信度高。
Base 74 × T2 Source weight ×0.9 = 67
Curation line 70Below curation line
Why selected
First-hand experience from an experienced technical blogger, offering direct and actionable advice that is highly relevant to content creators.
AI commentary
「The real value here is not blogging tips but breaking the mental barrier that 'you must have something perfect to publish.' For those stuck polishing drafts, Simon's 'lower your standards' is the most direct call to action. Especially relevant for developers early in their careers who want to build technical influence.」
Quick overview
Simon Willison shares highlights from his interview with Cynthia Dunlop, with the core advice to 'lower your standards' and publish while still unhappy with the draft — otherwise you end up with a folder full of unpublished drafts. He discusses why he continues blogging, the most surprising impact, his proudest and hardest posts, and practical tips for beginners. The view challenges perfectionism and emphasizes the value of public sharing.
- Core advice: lower your standards and hit publish while still unhappy with the draft
- Flaws you see in your writing are invisible to everyone else; done beats perfect
- Interview covers why he continues blogging, surprising impacts, proudest and hardest posts
- Offers actionable advice for beginners and recommends several blogs he enjoys
Full text
Simon Willison on Technical Blogging
I was interviewed by Cynthia Dunlop for her "Write that blog!" series back in January, but I just realized I never linked to the interview from my own blog!It includes my answers to the following questions:
- Why did you start blogging – and why do you continue?
- What has been the most surprising impact of blogging for you?
- What blog post are you most proud of and why?
- What post was the most difficult to write and how did you tackle it?
- Any lessons learned that you want to share with the community?
- Your advice for people just getting started with blogging?
- A few blogs that you particularly enjoy?
I'll repeat my most important piece of advice here:
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.
Nobody will ever know how perfect the thing you intended to write would have been. The flaws you see in your writing are invisible to everyone else.
Tags: blogging, interviews
Related items
84
FeaturedHow to Evaluate LLMs Before Production: Lessons from GitHub
GitHub 实战分享：如何在生产前评估 LLM
This practical guide stands out because it comes from a real security scenario, not theoretical reasoning. Teams integrating LLMs into production, especially those working on security scanning and data-sensitive engineering, should definitely read it. I recommend designing evaluation sets around your own business data rather than blindly adopting public benchmarks.
84
FeaturedRuff v0.16.0 Released: Default Rules Jump from 59 to 413, CI Pipelines Need Attention
Ruff v0.16.0 发布：默认规则从59条激增至413条，CI工作流需关注
For Python developers, this is an unmissable update signal. The significant increase in Ruff's default rules means we can no longer ignore potential issues in our code, and AI fix tools can lower the upgrade cost. Notably, Astral (OpenAI) is deeply integrating AI coding capabilities with static analysis tools, which may become the norm in future engineering practices.
81
FeaturedOpenRouter Team AI Spend Controls Setup Tutorial
OpenRouter 团队 AI 支出控制设置教程
As AI API spending balloons, OpenRouter's official governance tutorial signals that platforms are taking enterprise cost management seriously. Rather than waiting for bill shock, teams should configure these guardrails early. This is especially valuable for platform engineers and finance owners overseeing AI usage.
81
FeaturedFireside Chat with Anthropic's Claude Code Team: How AI Coding Agents Reshape Software Development
Anthropic Claude Code 团队炉边谈话：AI 编码代理如何重塑软件开发
The value of this fireside chat lies not in repeating Claude Code's features, but in revealing how Anthropic internally redefines engineering processes—shifting from 'execution-heavy' to 'taste-heavy'. For anyone in an AI product team, Cat's point that 'product taste outweighs execution' is worth pondering. Thariq's subversion of the 'never rewrite' rule also reminds us that traditional software engineering principles are being rewritten by AI capabilities.
80
FeaturedGPU Management: Why Idle GPUs Are the New Grounded Aircraft
GPU管理：闲置GPU为何成为新的停飞飞机
This blog is worth reading because it elevates GPU resource management to an economic perspective, using the grounded aircraft analogy to visualize waste. Teams using Kubernetes for GPU clusters can immediately try the recommended tools. However, users in China should note the compatibility of some tools outside AWS/GCP environments.
80
FeaturedAn Opinionated Guide to Which AI to Use to Do Stuff
一份主观指南：如何选择AI来做事情
This blog post is Simon Willison's refined take on Ethan Mollick's guide, ideal for developers and power users struggling to choose between ChatGPT and Claude and their various agent modes. It cuts through the confusion of product naming and unintuitive platform differences, offering clarity that saves hours of trial and error.
80
FeaturedPyPI Implements 14-Day Upload Window to Prevent Supply Chain Poisoning
PyPI 实施14天上传期限以防止供应链投毒
This is a critical message for the Python ecosystem. If you maintain any PyPI project, check your release workflow immediately — the 14-day window means you can no longer patch or overwrite files on old releases; you must publish a new version. For security teams, this is a best practice in supply chain security worth emulating by other package managers.
80
FeaturedLobsters Community Successfully Migrates to SQLite: A Win for Single-Server Architecture
Lobsters 社区成功迁移至 SQLite：单服务器架构的胜利
This migration case is particularly noteworthy because it challenges the conventional wisdom that small sites must adopt distributed databases. Lobsters proves that in 2026, a single server with SQLite can handle an active community. For startup teams struggling with overcomplicated tech stacks, this is an excellent reference for cost reduction and efficiency improvement.