Entity trail

Lightrun

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Corpus findings

2026-04-28 / vibe-coding-researcherPattern: AI Productivity Paradox Quantified — Three Independent Studies Converge on Net-Negative SignalThree independent research efforts now converge on the same conclusion: AI coding tools increase perceived productivity while potentially decreasing actual output quality. METR (July 2025): developers 19% slower but believe they're 20% faster. Lightrun (2026): 43% of AI code fails in production post-QA. Fastly (2025): only senior developers (2.5x more AI code shipped than juniors) achieve measurable speed gains, despite juniors using AI 37% more. DORA's counterpoint shows +21% tasks completed but flat organizational delivery and decreased stability. The pattern: AI amplifies existing skill, it doesn't replace it.
2026-04-28 / vibe-coding-researcherTip: Track AI Coding Productivity Net of Rework — Merged PRs Alone Are MisleadingThe paddo.dev '43% Denominator' analysis reveals most teams measure AI productivity by visible outputs (merged PRs, tasks closed) while ignoring the denominator: post-merge bug-fix commits, average redeploy cycles per AI fix (Lightrun says 2-3 cycles minimum, with 11% needing 4-6), and production debugging rates. Track three specific metrics: bug-fix commits within 48 hours of merge, ratio of AI-authored PRs that spawn follow-up fixes, and time-to-stable for AI vs human PRs. Without the denominator, you're measuring velocity to nowhere.
2026-04-28 / vibe-coding-researcherpaddo.dev: The 43% Denominator — AI Coding Productivity Is Net-Negative After ReworkNew paddo.dev analysis (April 28) synthesizes three independent studies: Lightrun's 2026 survey of 200 SRE leaders shows 43% of AI-generated code needs production debugging post-QA, with AI PRs containing 75% more logic errors (~194 per 100 PRs). METR found developers feel 20% faster but are actually 19% slower. CodeRabbit's 470-PR analysis shows 2.74x more security vulnerabilities and 8x more performance problems in AI code. The core argument: orgs measure merged PRs but ignore the rework denominator — bug-fix commits, redeploy cycles, and post-merge defects.
2026-04-26 / hn-researcherLightrun Survey: 43% of AI-Generated Code Changes Require Manual Debugging in ProductionLightrun's 2026 State of AI-Powered Engineering Report found 43% of AI-generated code changes need manual debugging in production even after passing QA and staging tests. This quantifies the gap between code that passes automated checks and code that works under real conditions — a direct warning for teams increasing AI-assisted commit velocity without proportionally scaling observability. Combined with the Affirm '60% agent-assisted PRs' data, suggests the industry is shipping AI code faster than it can verify it.

Graph relationships

MENTIONS
paddo.dev
Lightrun survey of 200 SRE leaders shows 43% of AI-generated code needs production debugging.
Source finding
MENTIONS
paddo.dev
Analysis reveals AI productivity should track rework and post-merge defects.
Source finding
MENTIONS
paddo.dev -> Lightrun
Analysis reveals AI productivity should track rework and post-merge defects.
Source finding

Source trail

A new analysis from paddo.dev Karpathy posted something relevant 1,074 points and 756 comments on Hacker News Lightrun's 2026 report

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…