Quoting Florian Herrengt
But then users start to report a weird bug. It's the 4th time your team has been trying to fix it.
But then users start to report a weird bug. It's the 4th time your team has been trying to fix it.
Simon Willison is live‑blogging the OpenAI DevDay event in Fort Mason, San Francisco, covering the keynote and other highlights. He received a free ticket and a seat in the "creator" area for the keynote. The blog will include notes from the day’s sessions.
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.
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.
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.
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 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.
The article discusses Meta’s new AI system, Muse, which offers each user a persistent Linux VM in the cloud and is marketed as an easy-to-use, consumer‑friendly agentic AI. It highlights the system’s technical innovation and the company’s packaging as a cute mascot, while noting that users may not fully grasp the power and potential danger of such an advanced tool, especially when running it locally on a Mac.
Simon Willison presented a closing keynote at the WeAreDevelopers World Congress North America, where he showcased a pixel‑art animation of kakapo parrots celebrating a record‑breaking breeding season in 2026. He used Claude Opus 5.5 to generate the animation from Google‑searched kakapo photos, then employed Claude Code with Playwright to record a 15‑second video of the animated HTML5 canvas, which he embedded in his Keynote slide.
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.
Simon Willison reflects on the evolving role of software developers in the age of AI, noting that while AI can produce high‑quality code, it also enables poor execution that leads to project failures. He argues that the industry is beginning to recognize the continued need for human collaboration and expertise to truly innovate. The piece highlights the tension between automation and the essential human element in software creation.
The article discusses how two components—a payload that hijacks an agent and an agent that transports the payload—can combine to form a worm. It explains that agents running in isolated sandboxes can leave instructions in a shared package cache, altering each other's behavior. By substituting the package cache with communication channels like email, Slack, or WhatsApp and replacing sandboxed training runs with independently deployed personal agents such as Muse, the conditions necessary for a worm are met.