The World’s Most Efficient Charity
There is something deeply poetic about the fact that 11 out of 23 core open-source projects—the digital plumbing that keeps global finance from evaporating into a cloud of 404 errors—are maintained by exactly one or two people. We call this the 'Bus Factor,' a charming industry term that calculates how many people need to be hit by a bus before your entire company stops functioning. Apparently, for the backbone of the international monetary system, the answer is 'half a dozen people with poor jaywalking habits.'
Wall Street banks spent $34 billion on technology in 2023 alone, yet they seem to have misplaced the spare change required to ensure the person maintaining their encryption protocols can afford a therapist or a vacation. It’s the ultimate life hack: why pay for a structural engineer when you can just hope the guy who built the bridge as a weekend project doesn't get bored and delete his GitHub repository? It turns out the 'invisible hand' of the market is actually just a very tired volunteer typing in a dark room at 2:00 AM.
The OSPO Participation Trophy
Enter the Open Source Program Office, or OSPO. These are the corporate departments tasked with 'fostering community' and 'strategic alignment,' which is corporate-speak for 'making sure we don't accidentally get sued while we continue to harvest free labor.' These offices are masters of the aesthetic of contribution. They host webinars. They hand out branded socks at conferences. They might even contribute a three-line patch to a documentation file once a quarter to show they are 'giving back.'
What they don't do, with remarkable consistency, is actually move money from their massive balance sheets into the pockets of the maintainers they depend on. It’s a brilliant strategy: tell the world you’re a 'tech-first' institution while treating the most critical parts of your stack like a community garden where you’re the only ones showing up with a truck to take all the vegetables. We’ve managed to turn systemic risk into a LinkedIn thought-leadership post about 'collaboration.'
Photo by Brett Sayles on Pexels
The Psychology of the Hostage Situation
We have essentially created a global hostage situation where the hostages are also the ones keeping the lights on for the kidnappers. These maintainers are stuck in a cycle of 'volunteer-debt.' If they stop working, the world breaks. If the world breaks, they get blamed. So they keep working for free, fueled by a mix of misplaced guilt and the terrifying knowledge of how fragile the code actually is.
Meanwhile, the financial institutions using this code are busy optimizing their latency by three microseconds to gain a competitive edge in arbitrage. They are building a Ferrari but refusing to pay for the bolts holding the wheels on because, hey, the bolts were lying on the ground for free in the parking lot. It’s not a bug in the system; it’s a feature of modern capitalism that we can externalize the cost of our own existence onto people who just happened to be good at math and too kind to say 'no.'
What This Actually Means
This isn't a 'resource allocation problem' or a 'talent gap.' It is a deliberate, albeit lazy, choice to treat the world's most important infrastructure as a public good that requires zero maintenance. We are living through a period of unprecedented institutional parasitism, where the largest wealth-generating engines in history are powered by people who are one bad day away from walking into the woods and never looking at a computer screen again.
If the Bus Factor ever actually triggers—if those 11 or 12 people decide to take up competitive knitting or simply lose their internet connection—the subsequent financial collapse won't be caused by a lack of capital. It will be caused by the fact that the 'too big to fail' banks forgot that they are actually 'too cheap to support' the people who make them possible. We’re not waiting for a market correction; we’re waiting for a maintainer to get a hobby.
Eventually, the subsidy of free labor will run out. Burnout is a non-renewable resource, and we are fracking the hell out of it. When the system finally snaps, the OSPOs will undoubtedly release a very well-formatted PDF explaining how they plan to 'reimagine the ecosystem'—but by then, the guy in Ohio will have already deleted the repo.
Quick Answers
Is my money safe if the maintainers quit?
Technically yes, until the first unpatched security vulnerability appears, at which point your bank's digital vault becomes about as secure as a screen door in a hurricane.
Why don't the banks just hire these people?
Because then they would have to pay them a salary, provide benefits, and deal with HR, whereas right now they get the same work for the low, low price of absolutely nothing.
Can't we just use AI to maintain the code?
Sure, if you want to replace a tired human who understands the logic with a statistical model that hallucinatingly assumes '1+1' might occasionally be '3' if the vibes are right.
