1,742
1,740
1,7371,7371,7361,7361,736495495
435431314314
1883h ago · 6 min read · Summary AI coding tools have accelerated how code is written. The infrastructure for validating that code has not moved at the same speed. The constraint in software delivery has shifted from writing
Join discussion
8h ago · 3 min read · The Build Is Red. Now What? CI pipelines are supposed to catch problems early. And they do — sort of. The pipeline tells you something is wrong. What it almost never tells you is what your change broke and why. Instead, you get a wall of log output. ...
Join discussion1d ago · 2 min read · The Bottleneck Moved — Most Teams Haven't Noticed For years, writing code was the slowest step in the software delivery pipeline. A developer might open one or two pull requests a day, and a teammate could review them without breaking a sweat. That b...
Join discussion2d ago · 3 min read · The Bottleneck Moved For twenty years, writing code was the slowest part of the software delivery pipeline. Requirements, architecture, and review all had enough slack to keep up. AI coding tools changed that almost overnight. LinearB's 2026 Software...
Join discussion2d ago · 7 min read · Code review should be about engineering judgment, not branch protection detective work. But many teams still end up with pull requests that feel almost ready and yet somehow impossible to merge. Nobod
Join discussion
3d ago · 3 min read · The Productivity Paradox Nobody Talks About There's a strange thing happening in engineering teams right now. Developers feel faster. Dashboards show more PRs opened. And yet features aren't shipping any quicker. LinearB's 2026 analysis of 8.1 millio...
Join discussion4d ago · 3 min read · The Numbers Don't Lie The AI Engineering Report 2026 analyzed telemetry from 22,000 developers across more than 4,000 teams. The headline metrics look impressive: epics completed per developer are up 66%, task throughput is up 34%, and PR merge rates...
Join discussion5d ago · 2 min read · The Bottleneck Moved AI coding tools promised faster development. They delivered — sort of. Developers using AI complete 21% more tasks and merge 98% more pull requests. But PR review time has increased 91%. The bottleneck didn't disappear. It reloca...
Join discussionApr 22 · 2 min read · The Problem With Treating All PRs Equally Every engineering team has a review queue. And in most setups, that queue is a flat list sorted by time. A one-line documentation fix sits next to a 600-line database migration, and they get the same visual t...
Join discussion