Menu

Coding Got Faster. Verification Became the Bottleneck
📰

Coding Got Faster. Verification Became the Bottleneck

DEV Community: github·Thomson D Nguy·12 days ago
#4pppG3r9
#devtogithub#technology#devto#dev#github
Reading 0:00
15s threshold

Technical Note

What happens when writing code is no longer the binding constraint?

We had about 25 engineering agents in the fleet and used Claude Code with three Claude Ultra accounts. Agents wrote most of the pull requests in our main repository, working alongside people. An agent could open a draft and GitHub would start running 30,000 tests. The next push could run all 30,000 again. Then the merge could kick off another full run. We were billed for 60 to 75 runner-minutes each time the full suite ran on GitHub-hosted runners.

The three Claude accounts cost us $600 a month. Our October tracker put GitHub Actions at about $1,600. We were spending more than two and a half times as much on GitHub Actions as on the subscriptions we used to write the code. 1

An agent could push a revision and start on another task. The PR stayed put until the tests came back green. In one October read, median wait in the merge queue was 12 to 14 minutes. 2 That's the time on the clock for the PR.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.