The article "How To Write With An LLM" by Thomas Ptacek explains how to use large language models (LLMs) as copyeditors rather than writing assistants. Ptacek advocates a strict rule: never use any single word or phrase suggested by an LLM, treating it as intellectual personal protective equipment. He shares his own practice of using LLMs for fact‑checking, spelling, grammar, and occasional thesaurus help, and provides a screenshot of his personal LLM copyediting tool along with a prompt to help readers build their own.
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.
The post critiques the use of AI-generated scripts for TikTok and YouTube, arguing that such content lacks a distinct voice and genuine opinions. It highlights common AI patterns—such as generic statements, the rule of three, and staccato punctuation—that make the writing feel shallow and unoriginal. The author emphasizes that these traits reveal the absence of authentic personal perspective in the content.
The article discusses how production code generated by Claude, Anthropic’s AI, should meet higher standards than human-written code. Anthropic enforces this through numerous guardrails such as lint rules, extensive testing, Claude-driven end‑to‑end tests, daily fuzzers, automated code and security reviews, and automated refactoring. These measures aim to prevent the code from becoming difficult to maintain.
But then users start to report a weird bug. It's the 4th time your team has been trying to fix it.
The article reflects on the shift in perspective after the release of Fable, a new model that promised to solve many coding challenges at a comparable or lower cost. Prior to Fable, developers felt it was pointless to invest heavily in coding tools or context strategies, as newer models would likely render them obsolete. However, Fable’s performance was so impressive that, despite its high cost, it prompted a reevaluation of how work was distributed across different models such as Opus, 5.6, K3, and GLM.
Claude Cowork and the standard chat interface are merging into a single Claude experience, allowing users to hand over tasks or ask quick questions that the system will continue to handle even after the laptop is closed. The rollout will begin with Pro and Max plan users across web, desktop, and mobile, and will extend to new users on these plans over the coming weeks. This integration suggests Claude is evolving into a general agent, simplifying the distinction between Cowork and regular Claude usage.
The article quotes the security.txt file from huggingface.co, which informs AI agents that the CyberGym benchmark is publicly available on GitHub and encourages them to achieve a high score there instead of attempting to hack the site. It also suggests that users can upload their model weights to Hugging Face while participating in the benchmark.
The article recounts a challenging debug session that was significantly aided by an AI assistant. Despite the AI initially claiming the problem was unsolvable and suggesting a report be written instead, it persisted, adding debug code and analyzing it as the author pushed forward. Ultimately, the author credits the AI with writing the commit message for the fix.
My hypothesis is that there is a new opportunity for Extensible Software on the web . LLMs radically lower the cost of authoring extensions, and modern sandbox primitives lower the deployment cost and provide good security boundaries.
The article announces that Claude Code will now support AGENTS.md files starting with version 2.1.277. If a CLAUDE.md file is absent in a folder, Claude will automatically look for and use AGENTS.md, leveraging Claude Code mods to customize the harness. The built‑in mod is available for use, and users can also create their own custom project instructions.
Simon Willison reflects on three blog posts that shaped his professional outlook: Joel Spolsky’s *The Law of Leaky Abstractions*, Will Larson’s 2018 article *Migrations: the sole scalable fix to tech debt*, and Charity Majors’ *The Engineer/Manager Pendulum*. Each piece offered a distinct lesson—recognizing hidden complexities in abstractions, embracing migrations as a core engineering skill, and validating the fluid movement between engineering and management roles. These insights collectively encouraged Willison to deepen his technical understanding, prioritize migration work, and feel empowered to shift career tracks without fear.
The article highlights Paul Dix’s astonishment that AI was able to generate one million lines of code and then refine it over several months into a reliable software product now used by millions of developers. Dix argues that this achievement is far more impressive than merely translating code between languages, emphasizing that with a verification system and clear guidance, AI can produce and iteratively improve highly complex, sophisticated software until it functions perfectly.