There Are No Lossless Transformations of Natural-Language Text: Lessons from an Engineer's AI Writing Policy
Score
67提出了‘自然语言无损转换’这一简洁有力的概念，对常见 AI 使用误区有启发。
文章本身短小精悍，论证清晰，推荐了具体的可执行政策。
可直接用于团队制定 AI 写作规范，帮助避免责任模糊。
AI 写作政策是持续话题，但内容并非新近突发新闻。
Simon Willison 是知名开发者博主，引用来源可靠。
Base 74 × T2 Source weight ×0.9 = 67
Curation line 70Below curation line
Why selected
Clear and broadly applicable viewpoint, not deeply technical but directly instructive for content workflows.
AI commentary
「What makes this worth reading is it turns a vague intuition into a clear policy: the risk of AI rewriting lies not in style but in meaning loss. Especially valuable for team leads managing content quality—don't let AI become a disclaimer inside your docs.」
Quick overview
Sophie Alpert shares an internal policy on engineers' acceptable use of AI writing. The core idea: there are no lossless transformations of natural-language text—every rewrite and rephrase shifts meaning. When using LLMs to polish docs, engineers must stand behind every sentence and ensure the document truly represents their own thoughts, rather than blaming AI for unclear lines. Short but highly practical.
- Any AI rewrite causes information loss, as the model lacks your full personal intent.
- Engineers must own every idea and sentence; 'AI wrote it' is not an acceptable excuse.
- AI writing tools can assist expression, but the final text must reflect the author's genuine thoughts.
Full text
There are no lossless transformations of natural-language text
Sophie Alpert shares her "internal policy on acceptable use of AI writing by engineers". It's a short read (supporting its own recommendations) and really good.If you chose to have LLMs help massage your writing the following rule seems crucial to me:
You must stand behind every idea and every sentence in your docs. It is your responsibility to make sure that the entire document is representative of your own thoughts before you share it. If a reviewer asks, “What did you mean by this line?”, it’s not acceptable to reply with “Oh sorry, AI wrote that, just ignore it.” You will confuse your readers (and waste their time) if you present them things that are not genuinely representative of your thoughts.
The "no lossless transformations" idea from the post title is expanded on here:
There are no lossless transformations of natural-language text — every rewrite and rephrase changes the meaning of your writing, and if this is done by an entity that doesn’t have the most detailed mental representation of what you personally were trying to communicate, information will be lost.
Tags: writing, ai, generative-ai, llms, ai-misuse
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.