Simon Willison reflects on the emotional impact of AI tools that can produce code quickly, noting that many developers experience an initial sense of disheartenment. He argues that recognizing the shift from coding to higher‑level problem solving allows experienced engineers to leverage new tools and add greater value. Willison emphasizes that software engineering has always faced rapid change, so adapting to AI is part of the profession’s ongoing evolution.
But then users start to report a weird bug. It's the 4th time your team has been trying to fix it.
Laurie Voss argues that while the cost of writing code has fallen dramatically, the costs of reviewing, fixing, and operating software are rising and will continue to do so. She emphasizes that the true expense lies in understanding user needs, precisely defining requirements, and ensuring a pleasant user experience—costs that are unique to each software product and do not scale with reuse. As software demand grows without an upper limit, these user‑centric costs will dominate the overall development effort.
Simon Willison discusses the pitfalls of attempting to replace a legacy system with a new one when technical debt is overwhelming. He explains that while the old system continues to evolve, developers lack incentive to improve it, and the new team, initially fast, eventually struggles to understand and deliver the required functionality. The result is often two partially functional systems in production, with the new one abandoned and the old one still running, increasing risk and complexity.
The article discusses Bryan Cantrill’s response to a tweet by former Anthropic employee Jacob Coxon, who claimed that AI could kill humanity by the end of the decade. Cantrill shares a personal anecdote about how his own youthful mistakes caused undue panic among non‑technical peers and warns against repeating that pattern. He emphasizes that domain experts must be cautious when making alarmist claims, especially about complex topics like critical infrastructure, bioweapons, and extinction, and that the burden of accurate information lies with those making such statements.
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.