Why "Just a Small Change" Is Never Small

The most expensive four words in software are "just a small change." Not because the change is hard. Because "small" is almost never true.

I changed one color once. One. And it broke the look of every screen in the app at the same time.

Here is why, in plain terms. A product is not a stack of separate pages, each minding its own business. It is more like a house where the wiring and the plumbing run behind all the walls. That one color was not sitting on one screen. It was a single setting that dozens of screens quietly shared. When I changed it in one place, it changed everywhere at once, including a lot of places I was not thinking about and did not test, because in my head I had made a "small" change to "one" thing.

That is the whole trap. The things that make software fast to build, shared settings, shared pieces, one source for a decision, are the exact things that make a small change ripple. The efficiency and the danger are the same feature. A change is only "small" in the place you are looking. Whether it is small everywhere else depends on how many rooms share that wall, and you usually cannot see that from where you are standing.

So when a developer, or a careful builder of any kind, hears "can you just quickly change this," they do not flinch because they are lazy or precious. They flinch because they have been burned by the word "just." They know the change might genuinely be small. They also know the only way to find out is to go check every room that shares the wall, and that checking is the actual work, not the typing.

If you build with AI, this bites harder, not softer. The AI will make your "small" change instantly and confidently in the one spot you asked about. It is not going to wander the other twenty rooms to see what you just knocked loose. That walk is on you.

Here is the useful reframe. "Small change" describes the typing. It does not describe the risk. The risk is set by how connected the thing is, not by how few words it took to change. Before you call something small, ask what shares this. If the answer is "a lot," then it is not a small change. It is a small edit with a large blast radius, and those are the ones that ruin your evening.

Respect the word "just." It is usually lying to you.

I write Building in the Open about designing and shipping a real product in public, one honest week at a time.

Curious how solid your own build-with-AI process is? Take the 4-minute check → aneilrazvi.com/maturity.html