Why a One-Line Change Can Break Your Whole Stack
summary
A one-line data model change in Bitwarden passes tests and linters but silently breaks web, mobile, CLI and MCP clients across repos, showing how small edits have a large, hidden blast radius. A generated software graph maps repo-to-component links and exposes affected clients. Review agents run independent checks — not the same agent that wrote the code — and CI can check PRs against the original ticket. Post-merge comments become turn PR comments into custom rules applied pre-PR.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:59Review is the new bottleneck
- 2:03A one-line change that passes every check
- 3:35The hidden blast radius
- 4:15Building a software graph
- 4:56Custom rules and tribal knowledge
- 5:47Context before code is written
- 6:29Don't let the writer grade its own code
- 8:20Turning PR comments into rules
- 10:06Q&A: catching the wrong intent
- 13:55Wrap-up
