The Cut of the Keel: On Resistance in a Frictionless World
I read another article this morning about the virtues of frictionless deployment. One-click rollbacks, autonomous scaling, systems that self-heal with the silent grace of a sleeping cat. The language is all of ease, of effortlessness, of removing the human from the loop. And I understand the appeal, deeply. Who hasn’t longed for a little less friction at two in the morning when the alerts won't stop howling? But lately, I’ve been thinking about the value of resistance. Not the grinding, obstructive kind born of technical debt, but a deliberate, designed resistance. The kind that a keel provides to a ship.
A hull without a keel is at the mercy of every current and breeze. It spins, directionless, achieving a kind of perfect, pointless mobility. The keel, that deep fin cutting into the dark water, creates drag. It resists. And in doing so, it allows the ship to point forward, to translate the force of the wind into purposeful velocity instead of chaotic spin. It is the resistance that defines its direction.
Our systems are no different. We chase the frictionless ideal, but in doing so, we risk building hulls without keels. A deployment process that is *too* easy can encourage a carelessness, a subtle shift from considered change to casual experimentation in production. The absence of a deliberate pause, a manual checkpoint, a required second set of eyes—these are forms of resistance we’ve sanded away. We mistake the smoothness of the process for the quality of the outcome.
I am not advocating for a return to bureaucratic gatekeeping or four-hour deployment ceremonies. The resistance I’m meditating on is more subtle. It is the resistance of a thoughtful logging format that requires you to consider what you’ll need to know in six months, not just what’s convenient to spit out now. It is the resistance of a backup restoration drill, a deliberate, slightly inconvenient quarterly ritual that forces you to confront the reality of your recovery plan, rather than just trusting the green checkmark next to the backup job. It is the quiet friction of a well-defined, manual approval step for elevating permissions, a moment of conscious intent before touching the core of the system.
This kind of resistance is not an enemy of efficiency; it is its architect. It trades a micro-delay for macro-stability. It is the acknowledgement that our future selves, tired and under pressure, will thank our present selves for building in a little thoughtful drag. The keel doesn’t stop the ship; it guides it. It turns chaotic energy into a straight line. In our pursuit of systems that never sleep, we must be careful not to build ones that can no longer think. We must cherish the cut of the keel, the beautiful, necessary resistance that keeps us on course.
Notes & further reading
A few pages I came back to while writing this: