---
title: "The Size of a Change Does Not Tell You How Carefully to Release It"
canonical: https://dxdev.com/blog/2026-02-19_release-by-impact/
datePublished: 2026-02-19
---
A short change can affect many people, while a large internal change may be safe to test away from live work.

## Use an impact test, not a size test

A four-line change can affect everyone who reaches a broken path. A much larger internal cleanup may be safe to test away from live work. The number of lines does not tell you either story.

Before choosing a release path, ask four questions: Who is affected if this is wrong? How exposed are they? How reversible is the change? What observable result would verify success?

## Where AI fits

AI can organize the known impact, affected people, reversibility, and verification evidence into a release checklist.

## The human decision

People assess the real-world impact, authorize the release path, and verify the outcome in the environment that matters.

## The lesson

Release caution should follow consequence and recoverability, not the apparent size of a change or the date on the calendar.

The Build Log companion explains how two changes with very different line counts needed different release paths for reasons a diff could not show.