Digging through a cold fire pit at 3 AM is a specific kind of penance, but Leo V.K. says it’s the only way to find the embers that actually survived the rain. Leo, a wilderness survival instructor with a penchant for explaining complex software architecture through the lens of forest management, often reminds me that the most dangerous thing in the woods isn’t a bear-it’s the assumption that someone else is coming to get you. We’ve treated the digital landscape like an infinite, self-replenishing forest, but we’ve forgotten that every tree in the stack was planted and protected by a human being. I’ve spent the last 23 minutes obsessively cleaning my phone screen with a microfiber cloth, trying to get rid of a smudge that turned out to be a dead pixel, a tiny 1×1 grave for a light that just couldn’t keep up. It’s a fitting metaphor for the current state of open source. We want a perfect, clean surface, but we ignore the underlying fatigue of the individual components that keep the display running.

The Foundation of Our Civilization

The dependency that currently powers roughly 43 percent of the modern web is often a single library, maintained by one person who hasn’t seen a meaningful donation in 13 months. This isn’t a hypothetical scenario. It is the architectural foundation of our entire civilization. We have built a global economy on the backs of a few thousand tired developers who are essentially running a benevolent oligarchy, not by choice, but by default. They didn’t ask to be kings; they just wrote a piece of code that solved a problem, and now the world expects them to maintain it forever for the grand price of zero dollars. It’s a hostage situation where the hostage has the keys but nowhere to go because they feel a crushing sense of duty to 803 total strangers who have opened issues on GitHub demanding features for free.

Freedom Requires Infrastructure

Open source was supposed to be a democracy-the great ‘free as in freedom’ equalizer. But freedom, as Leo V.K. would tell you while sharpening a hatchet, requires infrastructure. You can’t be free to wander the mountains if the trails aren’t maintained, and you can’t have a sustainable software ecosystem if the labor is externalized onto individuals who are burning out at a rate of 53 percent every three years. What we have created instead is an extraction economy. Large enterprises, generating 43 million dollars in revenue off the back of a single parsing library, contribute exactly $3 to the maintainer’s collective. If they contribute anything at all, it’s usually more work: a security audit that they expect the maintainer to fix for free over the weekend so their corporate legal team can check a box.

[The tragedy of the digital commons is that we’ve mistaken availability for abundance.]

Exploitation by Abstraction

I remember talking to a developer who had 103 stars on his latest project and 3 recurring sponsors. He was working 13-hour days at a fintech firm and then spending another 3 hours every night answering questions from people who hadn’t even read the documentation. He told me he was considering a security engineering job at Facebook just to have the luxury of only being responsible for what he was paid for. This is the ‘exploitation by abstraction.’ We use a package manager to pull in 203 dependencies, and because those dependencies are abstracted away, we forget they are human. We treat them like air or water-fundamental resources that should just be there. But air and water don’t have feelings, and they don’t get ‘burnout’ from being used too much. Humans do.

This creates a bizarre power structure where a tiny handful of people control the security and stability of the entire internet. This is the benevolent oligarchy. They are ‘benevolent’ because they continue to give, and they are an ‘oligarchy’ because power is concentrated in the few who have the privilege and the stamina to stay in the game. But what happens when that stamina runs out? When the maintainer of a critical encryption library decides that 13 years of uncompensated labor is enough and deletes the repository? We’ve seen it happen. The world breaks for 43 minutes, companies lose millions, and the collective response is usually to yell at the maintainer for being ‘unprofessional.’

The Rot of the Digital Commons

Leo V.K. once told me that if you take more from the forest than you give back, the forest doesn’t just stop giving; it becomes a different kind of forest. It becomes a thicket of thorns and rot. We are seeing the ‘rot’ in the form of supply chain attacks, where exhausted maintainers hand over their credentials to anyone who offers to help, only to find out that the ‘help’ was a bad actor looking to inject malware into the pipeline. It’s hard to vet a volunteer when you’ve been working alone for 3 years and your inbox is a 103-degree fever of demands. We have externalized the cost of security onto the people least equipped to pay for it.

The incentive misalignment is staggering. In a traditional market, if demand for a product goes up, the producer makes more money. In open source, if demand for your project goes up, you just get more work and more stress. There is no natural mechanism for sustainability. This is why we need to move toward a model where project delivery isn’t just about the code, but about the team and the long-term relationship. It’s about building something that can actually survive the ‘winter’ that Leo V.K. is always warning us about. This is the philosophy behind Hilvy, where the focus is on sustainable, high-quality execution that doesn’t rely on the heroic, suicidal efforts of a single person. They understand that a project is only as strong as the system that supports it.

The Debt of Consumption

We need to stop pretending that ‘free’ has no cost. Every time we npm install a package, we are incurring a debt. Usually, it’s a debt of maintenance, security, and attention. If we don’t pay that debt by contributing back-whether through money, code, or documentation-we are just participating in a massive, distributed Ponzi scheme where the ‘payout’ is a functional internet, and the ‘investors’ are the mental health of developers. It’s a fragile system, held together by the thin thread of individual altruism. And altruism is a finite resource. It’s not a solar panel; it’s a candle. Eventually, it burns down to the wick.

[We are building skyscrapers on a foundation made of volunteer-grade balsa wood.]

The Discomfort of Consumption

I’ve made mistakes in this realm too. I once complained on a forum about a bug in a 13-year-old library, acting like a customer who had paid for a premium service. I forgot that I hadn’t paid a cent. I forgot that the person on the other end was likely reading my comment on their phone during a 3-minute break between real tasks. I was part of the problem-the entitled user who views the internet as a vending machine rather than a community garden. It took a particularly blunt response from a maintainer to realize that my ‘feedback’ was actually just a burden I was dropping on someone else’s plate. I had to apologize, which was uncomfortable, but necessary. We have to be willing to sit with the discomfort of our own consumption.

The solution isn’t just ‘more money,’ although $5003 is certainly better than $3. The solution is a fundamental shift in how we think about the commons. We need governance structures that prevent the oligarchy from becoming a dictatorship of the exhausted. This means creating organizations that act as buffers between the individual and the crowd. It means funding teams, not just repositories. It means acknowledging that software is a living thing that needs constant nourishment. Leo V.K. doesn’t just teach people how to survive; he teaches them how to inhabit the wilderness without destroying it. We need to learn how to inhabit the digital world without destroying the people who built it.

The Collapse into Digital Feudalism

If we continue on this path, the benevolent oligarchy will collapse into a state of digital feudalism. Companies will fork everything and hide it behind proprietary walls to avoid the risk of the ‘abandoned dependency,’ and the dream of a shared, open internet will die. We are already seeing the signs: 23 major projects moving to more restrictive licenses in the last year alone. They aren’t doing it because they hate open source; they’re doing it because they want to survive. They’re tired of the rain, and they’re tired of people stealing their fire without bringing any wood to the pile.

I’m looking at my phone screen again. The dead pixel is still there. It’s a reminder that even the most advanced technology has points of failure that cannot be wiped away with a cloth. Our software ecosystem has thousands of these dead pixels-points where the light has gone out because the human behind the code simply couldn’t keep shining. We can ignore them and keep scrolling, or we can start thinking about how to repair the screen. It starts with realizing that the ‘benevolent’ part of the oligarchy is a gift, not a right. And like any gift, if you abuse it, you eventually lose it. Are we ready to live in a world where the code isn’t free, but the people are finally sustainable? That’s the 103-million-dollar question, and right now, we are failing to answer it. Maybe we should start by asking how we can be better guests in the forest that someone else worked 13 hours a day to plant for us.