The Humble Doorstop: On Holding Open the Gates of Change

On the floor of our server room, tucked beside a rack humming with the future, sits a small, rubbery wedge. It is a doorstop. Its entire purpose is to be placed, to be compressed, to hold a heavy fire door open against its own desire to swing shut. It is, in its own quiet way, one of the most critical and overlooked pieces of operational infrastructure we have.

We don't think about it until we need it. The doorstop’s value is purely situational. On a cool, quiet day, it is a tripping hazard. But on the day a new rack arrives, when we are heaving boxes and threading cables through the doorway, it is indispensable. It facilitates the flow of change. It holds the portal open so that the new, the bulky, the necessary can be brought inside without the constant fight against a spring-loaded hinge. It makes the act of transformation just that little bit easier.

This is its first lesson in reliability: a good system has tools for both stasis and flux. Our backups, our immutable logs, our version-controlled configurations—these are the heavy doors, the vital barriers that keep chaos contained. They are designed to close, to seal, to protect. But we must also have our doorstops. These are the scripts that gracefully drain traffic from a node before maintenance, the feature flags that allow us to deploy but not release, the checklists that ensure a change window is used safely and effectively. They are the small, simple things that allow us to deliberately and temporarily hold our safeguards ajar.

The Art of the Temporary Prop

Yet, the doorstop carries a inherent warning. Its use is meant to be temporary. No one leaves a fire door propped open overnight. Its entire function is predicated on a trust that the person who placed it will be the one to remove it. This is a profound act of operational discipline. We must be mindful of our temporary props.

How many of our systems are held together by the digital equivalent of a forgotten doorstop? A manual override script that became part of the daily routine. A port left open for a one-time data transfer and never closed. An exception in a firewall rule that was never documented. These are the wedges we leave in place, forgetting the door they are holding open was never meant to stay that way. They become silent single points of failure, little compromises that accumulate into a brittle whole.

The humble doorstop, therefore, teaches a dual philosophy. First, to actively employ tools that make necessary change safer and less burdensome. And second, to maintain the vigilance to remove them when their work is done. It is a call for mindful operation—to not just set a process in motion, but to see it through to its complete conclusion, including the cleanup. It reminds us that reliability isn't just about building strong doors, but also about knowing how and when to hold them open, and, most importantly, knowing when to let them swing shut again.

Notes & further reading

A few pages I came back to while writing this: