~/talk

Why a One-Line Change Can Break Your Whole Stack

links:none on file
slides:none on file

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

  1. 0:00Intro
  2. 0:59Review is the new bottleneck
  3. 2:03A one-line change that passes every check
  4. 3:35The hidden blast radius
  5. 4:15Building a software graph
  6. 4:56Custom rules and tribal knowledge
  7. 5:47Context before code is written
  8. 6:29Don't let the writer grade its own code
  9. 8:20Turning PR comments into rules
  10. 10:06Q&A: catching the wrong intent
  11. 13:55Wrap-up
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.