On the invisible governance of industries, and why the system you serve was never designed to serve you back.
🎬 The Continental Rules: A series on the career lessons hiding inside the world's most elegant action franchise.
🏛️ The High Table — Power you didn't elect ← You are here!
🏨 The Continental — Neutral ground, unspoken rules
🪙 The Gold Coins — Currency that isn't money
⛓️ Excommunicado — The anatomy of professional exile
✏️ Baba Yaga — The reputation that enters before you do
🏔️ The Impossible Task — The job that was supposed to set you free
👑 The Bowery King — The ones who built it from the sewers
✉️ A Note from the Author
I watched the John Wick films the way most people watch them — for the choreography, the suits, and the quiet satisfaction of watching a man avenge a dog with the kind of commitment most professionals can't muster for a quarterly OKR. But somewhere around the third film, between the gunfights and the impeccable interior design, something started nagging at me. Not the violence. The governance.
The High Table. Twelve seats. Unelected. Unaccountable. Setting rules that every assassin in the world must follow, regardless of whether those rules serve anyone other than the people sitting at the table. Punishing disobedience with a speed and totality that makes corporate HR look like a mediation circle. And operating with such complete authority that even John Wick — the most dangerous professional in that entire fictional universe — cannot simply walk away. The system will not allow it.
I have been in the software industry for over fifteen years. I have never killed anyone with a pencil. But I have spent my entire career operating inside a system whose rules were set by organisations I have never worked for, in meetings I was never invited to, by people whose names I will never know. And the more I thought about it, the more the High Table stopped looking like fiction and started looking like a Tuesday.
If Human Code was a field guide to the species living inside the building, this series is about the building's government.
This is the first article in a series called The Continental Rules — seven career lessons pulled from the John Wick universe and dropped into the world of professional survival. Because it turns out that a franchise about assassins has more to teach you about corporate life than any leadership seminar you have ever been forced to attend.
Let's start at the top. The very top.
🏗️ Act I: The Twelve Seats (Or: Who Decided That This Is How We Build Software?)
In the John Wick universe, the High Table is a council of twelve crime lords who govern the global criminal underworld. They set the rules. They enforce obedience. They punish anyone who steps out of line. And they have been in power so long that nobody alive remembers a time before them. Their authority predates the Roman Empire, which is the kind of tenure that makes even the most entrenched VP of Engineering look like an intern.
The professional world has its own High Table. It does not sit in a candlelit room in Rome. It sits in conference halls in San Francisco, boardrooms in Seattle, and keynote stages at re:Invent. Its twelve seats are occupied not by crime families but by something far more powerful: the companies whose decisions define how the rest of us work.
You know them. You have built your career around their gravitational pull. When one of them decides that containers are the future, every mid-sized company on the planet starts migrating to Kubernetes within eighteen months — not because it is the right infrastructure decision for a twelve-person team deploying a single application, but because the Table has spoken. When another announces that a particular framework is deprecated, a million developers feel the ground shift beneath code that was working perfectly well yesterday. When the Table decides that AI should be embedded in every product, the job listing for your next role will contain "experience with LLMs" whether or not the product has any conceivable use for one.
You did not vote for this. You were not consulted. The architectural patterns you use, the tools in your pipeline, the frameworks on your CV, the shape of your interview process — all of it was decided upstream, by organisations whose problems are not your problems, whose scale is not your scale, and whose priorities have nothing to do with the software you are actually building.
The sociologists Paul DiMaggio and Walter Powell gave this phenomenon a name in 1983: institutional isomorphism. Their paper, "The Iron Cage Revisited," argued that organisations within the same field do not become similar because similarity is efficient. They become similar because of three pressures that are almost impossible to resist. Coercive: you must comply or face consequences. Mimetic: everyone else is doing it, so it must be right. Normative: this is what the experts say, and you went to the same conferences they did.
The tech industry runs on all three at once. Coercive: try getting funding without a cloud-native architecture. Mimetic: try explaining to your CTO why you chose a database nobody at re:Invent mentioned. Normative: try hiring a developer who did not spend six months grinding the same interview problems that one particular company popularised, as if algorithm puzzles on a whiteboard were the universal measure of professional competence.
The High Table does not need to send an Adjudicator to your office. The pressure to copy does the enforcement for free.
🔗 Act II: The Oath of Fealty (Or: How You Joined Without Signing Anything)
In the films, every operative in the underworld swears an oath of fealty to the High Table. The words are simple: "I have served. I will be of service." It is not a negotiation. It is a declaration of subordination, made in exchange for access to the system — the Continental hotels, the gold coins, the network, the protection. You swear the oath, and the machine begins to work for you. Refuse it, and you are outside the system entirely. No resources. No network. No career.
The professional oath is never spoken aloud, but it is sworn the moment you accept your first job offer. Not the contract — the contract is paper. The oath is the set of invisible agreements you made without reading the terms and conditions:
You agreed to measure your worth in the currency the Table recognises. Job titles. Company logos on your CV. Technologies the market currently values. You may be the most brilliant developer in your city, but if your stack is not on the Table's approved list, your brilliance is priced at a discount.
You agreed to move when the Table moves. When the industry shifts direction — cloud-native, serverless, AI, whatever comes next — you will shift too. Not because you evaluated the technology and concluded it was superior for your use case. Because the job listings changed. Because the recruiters changed their keywords. Because the conference talks changed. The Table moved, and you moved with it, because standing still in a moving system is the same as falling behind.
You agreed to play by the interview rules. The technical interview process at most companies is a direct descendant of practices established by a handful of firms in the early 2010s. Whiteboard algorithms. System design rounds. Take-home projects. Behavioural questions structured around a framework that one company's HR department invented and everyone else adopted because — and here is the copycat pressure again — if the company with the highest market capitalisation does it this way, it must be correct. You did not design this process. You were not asked whether it measures the skills your actual job requires. But you will study for it. You will practise. You will perform. Because the alternative is not being hired, and not being hired is the professional equivalent of excommunicado.
Max Weber, the German sociologist who described in 1905 what would later be translated as the "iron cage," argued that modern capitalist society traps individuals in systems built on efficiency and rational calculation from which there is no escape. His original German phrase was stahlhartes Gehäuse — a casing as hard as steel. Weber was talking about bureaucracy. He could have been talking about your LinkedIn profile.
The oath is not coerced. That is the elegant part. Nobody forces you to learn Kubernetes. Nobody holds a gun to your head and says "adopt Agile." The system simply makes the alternative so costly — unemployment, irrelevance, the slow erosion of your market value — that compliance feels like choice. And the moment compliance feels like choice, the cage is complete.
John Wick swore the oath because the alternative was life outside the system. You did the same thing. The only difference is that John knew he was swearing it.
⚖️ Act III: The Rules That Serve the Table (Or: Why Best Practices Are Rarely Best for You)
The films make one thing beautifully clear about the High Table: the rules exist to protect the Table, not the people who follow them. "No business on Continental grounds" sounds like a rule that protects everyone equally. In practice, it protects the people who own the Continental. The enforcer who needs to finish a job is constrained. The hotel owner who profits from the enforcer's stay is not. The rule is neutral in language and lopsided in effect.
The professional world is full of Continental rules.
"Best practices" is the most effective phrase in the industry's vocabulary, and it deserves more questioning than it gets. A best practice is a solution that worked for one organisation, at one scale, with one set of constraints, at one point in time — and was then declared universal by the people who benefited from declaring it universal. When a cloud provider publishes a best practices guide, the practice that is "best" is, with remarkable consistency, the one that involves purchasing more of their services. When a consultancy promotes a best practice, the practice that is "best" is the one that requires their continued involvement. The practice is real. The "best" is marketing.
Microservices are a best practice. They are a best practice that emerged from organisations running thousands of services across distributed teams in multiple time zones. The mid-sized fintech with eight developers and a single payment flow does not have that problem. But the Table endorsed it, and the Table's architecture is aspirational. So eight developers now maintain thirty-seven repositories, a service mesh they do not understand, and a deployment pipeline that takes longer to configure than the monolith took to write. The architecture is not solving their problem. It is solving Google's problem. But it is the Table's approved architecture, and straying from it feels like heresy.
Agile is a best practice. Or rather, the Manifesto was a set of principles written by seventeen people in a ski lodge in Utah who were frustrated with heavyweight process. What the Table turned it into — the certifications, the two-day courses, the Scrum Masters, the sprint rituals performed with the precision and self-awareness of a cargo cult — bears the same relationship to the original manifesto that a theme park bears to the wilderness it replaced. The principles were wise. The industry that grew around them is a compliance engine. And the compliance engine does not serve the teams who follow it. It serves the organisations that sell it.
The John Wick films understand this well. Every rule in the underworld exists to maintain the power structure, and the characters who survive are the ones who understand the difference between following a rule because it is just and following a rule because it is enforced. Winston survives not because he obeys every rule, but because he knows which rules the Table actually cares about and which ones are theatre. He is not the most powerful character in the franchise. He is the most politically literate. And in the professional world, political literacy — the ability to tell the difference between a rule that matters and a rule that is performance — is a survival skill that no best practice guide will teach you.
But even Winston, with all his literacy, never tried the one move that would truly test the system: walking away from it.
🪤 Act IV: The Illusion of the Empty Chair (Or: Why You Cannot Leave and Why the Table Knows It)
In John Wick: Chapter 4, John attempts what every burnt-out professional has fantasised about: he tries to fight his way out of the system entirely. Not to retire within the system. Not to negotiate better terms. To leave. To be free. To owe nothing to anyone and have no one owe anything to him.
It does not work. Four films, hundreds of dead operatives, and an international trail of destruction later, the system does not release him. The only exit the Table offers is the one John finds at the end of the fourth film, and if you have seen it, you know it is not the kind of exit anyone puts on their five-year plan.
The professional High Table operates on the same principle: it does not have a door.
You cannot leave the system because the system is the market, and the market is everywhere. You can leave a company. You can leave an industry vertical. You can move countries. But you cannot leave the web of expectations, valuations, and credentials that determines your professional worth. Your LinkedIn profile is not a document you maintain. It is a passport the Table issued. Your CV is not a record of your achievements. It is a record of your compliance — proof that you used the approved tools, followed the approved methods, worked at organisations the Table recognises.
Try stepping outside. Try spending five years at a company the market does not value. Try mastering a technology the Table has deprecated. Try doing excellent work that does not translate into a keyword a recruiter can search for. You will discover what John discovered: the system is not a place you go. It is a set of rules that follow you. Your market value is not determined by what you can do. It is determined by what the Table has decided matters this quarter.
And the worst part — the part Weber understood and the films show — is that the cage does not feel like a cage when you are succeeding inside it. The gold coins flow. The Continental doors open. The network hums. You do not notice the walls because the interior is comfortable. You notice them only when you try to leave, or when the Table decides you are no longer useful, and the resources that felt like entitlements reveal themselves to be privileges that can be revoked with a single policy change, a single reorganisation, a single shift in the market's approved technology stack.
The chair at the High Table is never empty. It only looks empty from the outside. From the inside, someone is always sitting in it. And the moment you entered the industry, you agreed — without being asked — to arrange your career around whatever they decide.
📕 The Concierge's Notes
🏷️ The keyword pivot. Watch the job market after a major company's annual conference. Count the days between the keynote and the first appearance of the new terminology in job listings at companies with no connection to the technology announced. If the gap is less than two weeks, you are watching copycat adoption in real time. Nobody evaluated the technology. They evaluated the keynote.
📋 The best practice that benefits the seller. When someone presents a best practice, ask one question: who benefits most from widespread adoption of this practice? If the answer is the company or consultancy promoting it rather than the teams using it, the practice is not best. It is marketed. This does not mean it is wrong. It means the word "best" is doing commercial work, not technical work.
🔄 The interview cargo cult. If your company's interview process resembles one designed for a company with ten thousand engineers and you have forty, ask who designed it and why. If the answer involves the phrase "industry standard," ask which industry and which standard. If the answer is "this is how [large company] does it," you have found a Table rule being enforced locally without any adaptation.
🪞 The invisible oath. Look at your own CV. Count how many technology choices on it were made because you evaluated them as the best tool for the job versus how many were made because the market currently rewards them. If the ratio surprises you, you have found the oath you swore without noticing. This is not a criticism. It is a diagnostic. Knowing the difference between genuine preference and market compliance is the first step to making deliberate career decisions instead of reflexive ones.
📉 The deprecation shiver. Notice your emotional reaction when a tool or framework you have invested years in gets deprecated by a major player. If the reaction is out of proportion — if it feels less like "I will need to learn something new" and more like "my professional identity is under threat" — that gap tells you how much of your professional identity the Table built for you. Your skills did not change. The Table's rankings changed. And the fact that those feel like the same thing is the cage.
✉️ A Final Note from the Author
I want to be clear about something, because sarcasm has a way of flattening into cynicism, and cynicism is the refuge of people who have stopped trying.
The High Table is not a conspiracy. It is not a cabal of executives meeting in a bunker to decide your fate. It is what happens when a small number of very large organisations have outsized influence over the standards, tools, and expectations that govern an entire industry. The people at those organisations are not villains. Many of them are brilliant engineers solving hard problems at genuinely unprecedented scale. The tools they build are often good. The patterns they discover are often useful. The problem is not the tools or the patterns. The problem is the unquestioning adoption — the herd instinct that turns one company's solution into everyone's obligation.
You cannot fight the High Table. John tried. It did not end well. But you can do something John never managed, because John was too busy reloading: you can understand the system you are operating inside. You can tell the difference between the rules that serve you and the rules that serve the Table. You can adopt a technology because it solves your problem, not because it appeared in a keynote. You can design an interview process that tests the skills your team actually needs, not the skills that a company with a thousand times your headcount decided were important. You can build a career that is informed by the market without being controlled by it.
Weber called the cage "a casing as hard as steel." But steel, given enough time and the right pressure, bends. It does not shatter. It bends. And the bending starts with seeing the cage for what it is — not a natural law, but a human construction. Built by humans. Maintained by humans. And, with enough clarity and enough stubbornness, navigable by humans who understand that following the rules and understanding the rules are two very different skills.
The High Table is real. The oath is real. The iron cage is real. But so is the professional who knows all three are there and chooses, with open eyes, which rules to follow and which to simply acknowledge. That is not rebellion. That is literacy. And in a system that runs on blind compliance, literacy is the most dangerous skill you can develop.
"Institutions will try to preserve the problem to which they are the solution." — Clay Shirky 🪨
