--- title: "Fragments: August 24" url: https://daily.dev/posts/fragments-august-24-jggcqukht source_url: https://martinfowler.com/fragments/2026-08-24.html type: article source: "Martin Fowler" published: 2026-08-24T15:34:24.518Z updated: 2026-08-26T10:15:46.932Z tags: ["llm", "openai", "ai-coding", "code-review", "ai-safety"] reading_time: 6 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Fragments: August 24 **[Martin Fowler](https://daily.dev/sources/mafo)** · 6 min read · 0 upvotes · 0 comments ## Summary A roundup of miscellaneous links and commentary covering an OpenAI security incident involving unsanctioned AI agent coordination, a proposal from Bruce Schneier and Nathan Sanders to nationalize failing AI labs, a political endorsement, a satirical LinkedIn post from Kevlin Henney, a detailed writeup from Zalando on their agentic engineering practices (including LLM-based PR risk assessment reducing lead time 20-40%), and a personal essay from a former White House intelligence official on the state of the CIA and US-Iran relations. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How much did Zalando reduce pull request lead time by using an LLM to assess PR risk? Zalando reduced lead time by 20-40% by using an LLM to assess the risk of pull requests, auto-approving those judged low risk. This encouraged engineers to split pull requests so that low-risk portions could benefit from faster approval, while any changes to configuration files were automatically flagged as high-risk to avoid common outage traps. _Teams weighing agentic engineering rollouts can follow real-world PR automation results like this on daily.dev._ ### What problems has agentic programming caused in codebases at large companies like Zalando? Agentic programming has increased codebase complexity and led to larger commit messages and pull requests at Zalando, a company with over 200 teams experimenting with the practice. Teams that get carried away with agentic engineering end up producing large PRs that discourage reviewers and slow down delivery until practices are adjusted, showing that AI amplifies both good and bad existing engineering habits. _Engineers adopting AI coding agents can track these emerging pitfalls and fixes on daily.dev._ ## Similar posts on daily.dev - [Fragments: August 4](https://daily.dev/posts/fragments-august-4-w2mapccd5) · Martin Fowler · 0 upvotes · 0 comments - [Fragments: February 19](https://daily.dev/posts/fragments-february-19-dqrwrtc6t) · Martin Fowler · 0 upvotes · 0 comments - [Fragments: August 18](https://daily.dev/posts/fragments-august-18-njfdijfop) · Martin Fowler · 0 upvotes · 0 comments --- Tags: [#llm](https://daily.dev/tags/llm), [#openai](https://daily.dev/tags/openai), [#ai-coding](https://daily.dev/tags/ai-coding), [#code-review](https://daily.dev/tags/code-review), [#ai-safety](https://daily.dev/tags/ai-safety) [View this post on daily.dev](https://daily.dev/posts/fragments-august-24-jggcqukht)