---
title: 'In the News: September 1, 2026'
description: 'Dave Farley argues coding agents accelerated code generation while specification and verification remain the bottlenecks to durable software.'
canonical_url: 'https://darkfactory.dev/news/2026-09-01-extra-4'
markdown_url: 'https://darkfactory.dev/news/2026-09-01-extra-4.md'
collection: news
date_published: '2026-09-01T16:20:00-04:00'
date_modified: '2026-09-01T16:20:00-04:00'
---

# In the News: September 1, 2026


Dave Farley argues that coding agents have accelerated code generation without moving the bottleneck in software work: specification, verification, and release.

## 1. Coding agents sped up code generation while specification and verification remain the bottleneck

**[Vibe Coding Is Not The Best We Can Do](https://tessl.io/blog/vibe-coding-is-not-the-best-we-can-do)** · Dave Farley, Continuous Delivery author and speaker · Tessl blog, August 24, 2026

Farley, writing up his AI Native DevCon London talk, argues that coding agents have sped up generating code without improving the practices that make the result durable: specification, verification, and incremental delivery. "So the bottleneck is not code generation. We have sped up the coding bit, which was often not the hardest part. The bottleneck is specification, verification, and release," he writes. His proposed fix is to write acceptance criteria as executable, version-controlled specifications, kept mostly out of the model's view, and to treat tests as a form of measurement rather than proof that the work is correct.

**Why it matters:** Teams already running agents day to day can write executable specifications that test the agent's output and keep continuous delivery's incremental habits intact around it.