the shed // interactive briefing

1 Million PRs, 5 Months: The Real DevOps Bottleneck Isn’t Review (Plus RubyKaigi’s 2026 Ruby Survey)

New data this week complicates the “AI broke code review” story: teams were already shipping in batches of 2–50 before AI showed up, which means deployment validation, not review, was always the ceiling. Meanwhile RubyKaigi’s fresh 2026 attendee survey shows Ruby 4.0 caught up to 3.4 in adoption within six months — and Claude Code, not GitHub Copilot, is now the default coding assistant in the Ruby world. Step through both below.

the-shed — briefing-02.sh

Where Does a 2026 AI-Generated PR Actually Get Stuck?

GitHub Copilot generated over 1 million pull requests in five months. If “human review” were the bottleneck, throughput should have collapsed. It didn’t — because the real constraint moved downstream. Click through the lifecycle of one PR to see where it actually waits.

Reported distribution of how teams actually ship changes in 2026 — batching, not per-PR review, sets the pace. Click a bar.

1 change
8%
2–10 changes
41%
11–50 changes
37%
50+ changes
14%
Click any row — over 90% of teams ship in batches of 2–50, meaning validation/release infrastructure (not individual review) sets the real pace of delivery.

State of Ruby, per RubyKaigi’s 2026 Attendee Survey

~400 Japan-centric RubyKaigi attendees, surveyed April 2026. Pick a category on the left.

Ruby 4.0 shipped December 25, 2025. Six months later it’s already running neck-and-neck with 3.4 in production — a faster major-version migration curve than Ruby’s last few jumps, and a sign the community isn’t stuck on legacy branches the way “Ruby is dying” takes assume.