Skip to lesson
Exit
CI/CD, release engineering & the toolchain1 / 3

2 min lesson

Why 'smaller and more often' is the whole game

Consider this situation. "A skeptical platform lead says 'AI just means more code we have to review. That's more risk, not less.' Reframe in one move." Start with the decision, then the evidence.

Step 1 of 3

Why 'smaller and more often' is the whole gamethe batch-size argument

Large batches are where risk hides, and the figure shows how.

Cursor's structural contribution is that it makes the expensive part of a small PR cheap: the tests and the changelog. Engineers stop amortizing that cost by batching, and the blast radiusHow much breaks if a change goes wrong; the scope of potential damage. Press Enter for the full definition. of any one change stays tiny.

Batch size sets the blast radius

Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.

diagram: batch-size-blast-radius

A small PR stays reviewable, git bisect pinpoints the regression and the blast radius is tiny. A 2,000-line PR defeats review, makes bisect useless and couples unrelated changes, so one rollback reverts five features. Small diffs are what keep AI velocity safe.