B4 Research August 10, 2026

Engineers report a productivity-experience paradox: 84% report productivity improvement at both time points, yet the share of matched participants reporting worsened developer experience in at least one dimension nearly doubled from 14% to 27% over six months, with flow state and cognitive load eroding while feedback loops improved.

What it means Track developer experience alongside throughput when rolling out AI tooling — the work is shifting to supervisory correction of AI output, and that erosion shows up months after the productivity win.

arXiv preprint · MAY 22

In legacy-code modernization, semantic-trap snippets silently changed behavior in 39.7% of attempts (versus 7.0% on benign controls), and the producing model silently endorsed 31.7% of its own drift cases — sometimes while correctly articulating the exact Python 2/3 semantic distinction that broke its output.

What it means Never use the model that performed a migration as its own behavioral reviewer — verify semantic preservation with executable oracles (characterization tests), especially around numeric semantics.

arXiv preprint · MAY 20

10.7% of passing SWE-agent trajectories are 'Lucky Passes' — regression cycles, blind retries, or missing verification that happen to end green — with per-model Lucky rates ranging 0.5% to 23.2%, enough to move models up to five leaderboard rank positions when scored by process quality.

What it means When comparing agents for production use, inspect trajectories, not just pass rates — a model that passes by chaotic trial-and-error will be more expensive and less predictable on your real work than its score suggests.

arXiv preprint · MAY 13