The Code Review That Cost $2 Million, CodeGood

kept by eddie jan 05

Code review catches mostly style issues, not production bugs, costing a typical 80-engineer firm $3.6M annually while preventing few real incidents.

Claude Security is now in public beta
Claude Security public beta lets Enterprise customers scan code for vulnerabilities and generate targeted patches using Opus 4.7, with integrations across partner platforms.
also on CrowdStrike, #software-engineering, #ai
Reality's Moat — David Beyer
Operational knowledge earned by surviving surprises in coupled, shifting systems ('scar tissue') is the only durable competitive advantage when AI makes building any software essentially free.
also on CrowdStrike, #software-engineering, #ai
You should use AI for reviewing code especially when the diff is huge – Simian Words
Human reviewers should focus on offering out-of-distribution knowledge (context, design decisions) rather than line-by-line checks, which AI can handle.
also on #code-review, #software-engineering, #productivity, #ai, #developer-tools
Using AI to write better code more slowly
Using multiple LLMs for rigorous code review and bug finding can produce higher-quality code than the common fast-output approach, though it slows development velocity.
also on #code-review, #software-engineering, #productivity, #developer-tools
GitHub's plan for Agents — Kyle Daigle, GitHub
GitHub COO Kyle Daigle discusses how AI agents caused platform activity to surge 1400% in 2026, straining infrastructure and forcing GitHub to rethink open-source social contracts and reliability.
also on GitHub Copilot, Microsoft, #software-engineering, #developer-tools