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.
But then users start to report a weird bug. It's the 4th time your team has been trying to fix it.
The article discusses a shift in code review practices, moving from a final gate to continuous review that functions like spellcheck during coding. It highlights how the Claude Code team uses the Claude AI to catch routine mistakes before human reviewers intervene, allowing developers to focus on higher-level issues. The piece references insights from Addy Osmani, Morgan Westlee Lunt, and Qing Wang on this evolving approach.
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.
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.