Simon Willison

Quoting Terk Terkowitz

Read the original on Simon Willison →

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.

Machine-generated by The Flow from the publisher's headline and feed description — not written or checked by a human. The full article lives at Simon Willison.

Simon Willison
Sep 12

Quoting Paul Ford

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
Aug 26

Quoting Paul Dix

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
Oct 22

Quoting Armin Ronacher

Simon Willison reflects on the long history of flawed software development, noting that the proliferation of bad code over the past three decades is now being penalized by the universe. He cites Armin Ronacher’s perspective that the rise of AI, while entertaining, has amplified the consequences of these past mistakes. The piece underscores the growing importance of addressing security and reliability in the age of generative AI.

Simon Willison
Sep 14

Quoting Laurie Voss

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
Sep 11

Quoting Boris Cherny

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.