The Humble Doorstop: A Bastion Against Unplanned Change
We spend our days architecting systems to resist change. We configure immutable infrastructure, we lock down deployment pipelines, we enforce rigid access controls. All of it is a grand, digital effort to maintain a desired state. And yet, one of the most reliable guardians of that state in my own daily work is a small, rubber-coated wedge of steel that lives on the floor by the server room door.
The doorstop is an analog device in a digital world, a physical interlock for a virtual process. Its purpose is beautifully, brutally simple: to prevent an unplanned modification to the environment. In this case, the environment is a draughty corridor and the modification is a door swinging shut. Its entire reason for being is to enforce a constant. It is a monument to the idea that sometimes, the most sophisticated solution is a block of friction.
I think about that doorstop every time I write a configuration file or a firewall rule. Its logic is impeccable. It doesn’t require authentication; its authority is its presence. It has no moving parts to fail, no software to patch, no logs to monitor. It operates silently, requiring no battery or network connection. Its status check is a glance. It is the ultimate in boring technology, and its reliability is absolute.
The Philosophy of the Wedge
This small object embodies a core principle of sane operations: the enforcement of intentionality. The door doesn’t stay open by accident; it stays open because someone made a conscious decision to place the stop. The action is deliberate, the outcome is clear. There is no ‘drift’. The door is either meant to be open, with the stop in place, or it is meant to be closed, with the stop put away. The state is binary and unambiguous.
We strive for this clarity in our systems. We version our infrastructure code to know exactly what was intended. We use declarative configurations to move away from ambiguous, incremental changes. The goal is to make the state of the system as obvious and as deliberate as the gap under that propped-open door. The doorstop doesn’t just hold something; it communicates. It signals that this alteration to the normal flow—this open door—is approved, is temporary, is known.
In the end, the doorstop is a lesson in humility. For all our complex orchestration and automated auditing, sometimes the most critical thing is to simply, physically, prevent a thing from happening. It is a reminder that not every problem requires a distributed systems solution. Some just require a wedge, a moment of thought, and the small, satisfying act of ensuring a door won’t slam shut at the worst possible moment. It is the oldest form of uptime there is.
Notes & further reading
A few pages I came back to while writing this: