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.
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.
Simon Willison reflects on his experience with coding agents, noting that while they enable impressive feats, they also complicate software engineering. He emphasizes that fully harnessing their capabilities demands exceptional discipline and deep knowledge. The article highlights the dual nature of coding agents as both powerful tools and challenging additions to development workflows.
Simon Willison reflects on how programming used to be a rewarding career, describing it as a job where developers solved complex logic puzzles for high pay and had full control over strategy and timelines. He notes that coding agents and large language models (LLMs) now handle many of these puzzles, offering a "gift that keeps on giving" for those who enjoy building systems without caring deeply about the underlying problems. However, for programmers who found joy in directly solving problems, this shift represents a significant loss.
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 how engineers should view the lack of benefit from current AI tools as a finding rather than a failure. It encourages documenting these observations, sharing them with peers and managers, and actively seeking solutions. By explaining where AI falls short, engineers demonstrate the judgment expected of them.
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.
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 discusses how AI is enabling large-scale decompilation of games, allowing developers to create mashups and preserve old titles by porting them to modern platforms like WebAssembly. It highlights both the exciting possibilities for game preservation and the frightening implications for intellectual property, as anyone could decompile and repurpose software without permission. The piece underscores the dual nature of this technology—boosting accessibility and preservation while threatening the security of proprietary software.
The article discusses the essential skill of effectively instructing coding agents and verifying their changes. It highlights that while line‑by‑line code review is one method, it is not the most efficient way to validate software changes. The focus is on confidently guiding agents and confirming correct implementation without exhaustive inspection.
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 article reports that rumors of bugs in open‑source projects now trigger rapid security exploits, with automated agents probing for vulnerabilities within minutes of a patch being discussed. Anil Madhavapeddy demonstrates how modern coding agents can exploit even minimal hints, and rclone maintainer Nick Craig‑Wood notes a dramatic spike in security disclosures and delayed CVE assignments. The post highlights the need for new processes to protect open‑source communities from swift exploitation.