The Obedient Clerk and the Unwritten Law
There is a quiet rhythm to keeping systems alive. It’s a rhythm of checks and confirmations, a liturgy of the expected. We write runbooks, we document procedures, we design our automations to be predictable and sane. The ideal operator, in this frame, is one who follows the script. They are the obedient clerk of the system, processing the tickets and executing the playbooks with meticulous care. It’s a comforting ideal. But it overlooks a deeper, more vital duty, one for which the story of Harold Bride, the junior wireless operator on the R.M.S. Titanic, provides a stark and poignant lesson.
Bride’s job was, in the parlance of our world, a classic operations role. He was responsible for the health and function of a critical communications service: the Marconi wireless. His duties involved routine maintenance, logging outgoing and incoming traffic, and ensuring the machine’s delicate spark-gap transmitter was in working order. The night of April 14th, 1912, began with this mundane cadence. The script was being followed. But then, the context changed entirely. The ship struck the iceberg, and the rulebook was rendered instantly obsolete.
What happened next was not mere obedience. It was judgment. As the senior operator, Jack Phillips, frantically sent the new distress signal, CQD, and later SOS, Bride’s role evolved. He became the keeper of state. He knew the power was failing, he understood the desperate queue of messages needed to be prioritized, and he made a critical decision. When a crewman attempted to shut down the wireless to conserve electricity for the failing lights, Bride physically intervened, arguing that the ship’s only hope was the continuous operation of his ‘service’. He understood that the procedure, in this unprecedented failure mode, was to keep sending the signal until the very last moment.
This is the unwritten law of operations that supersedes all written ones: the operator’s duty is to the service’s intent, not merely to its documented steps. Bride and Phillips didn’t just follow a runbook for ‘ship hitting iceberg’; there wasn’t one. They assessed the catastrophic failure, understood the ultimate goal—summoning help—and adapted their tools and actions relentlessly to serve that goal. They prioritized distress calls over passenger telegrams. They fought for resource allocation (power) against other failing subsystems. They worked until the water was physically lapping at their feet, a brutal, literal form of uptime.
In our world, we are seldom faced with such dire physical consequences. But the principle holds. The obedient clerk, when the alert fires at 3 AM for a novel failure, cannot simply shrug and say the runbook doesn’t cover this. They must channel the spirit of the wireless operators: understand the service’s true purpose, diagnose the actual break in the state machine, and act to preserve the intent. The logs, the backups, the restarts—they are all tools for this higher function. They are the Marconi set. But the operator must be more than a technician; they must be a sentinel capable of judgment when the lights are going out. The most reliable technology is not the one that never fails, but the one operated by someone who knows what to do when it inevitably does.
Notes & further reading
A few pages I came back to while writing this: