The exponential curve behind open source backlogs

A simple model, a hard truth

A recent deep-dive on Hacker News linking to Arman C. Keser's piece argues that open source backlogs can grow not linearly, but exponentially — and it hurts. It has been reported that the author models issue flow for projects like Jellyfin, showing how small mismatches between incoming requests and the team’s capacity to resolve them compound quickly. The math is straightforward; the sting is real. One missed equilibrium and the queue snowballs.

Why maintainers feel the burn

So why does this feel so familiar? Because many projects live on the knife-edge of supply and demand: users keep filing issues and feature requests, while the handful of people who keep the lights on can only do so much. The piece makes the emotional point clear — maintainers are not machines. Burnout, stalled PRs, and endless triage are the human fallout. It has been reported that the analysis ties this dynamic to common open-source phenomena: increasing visibility, hobbyist contributions that need shepherding, and the gap between first-time contributors and sustained maintainers.

What to do about it

The article doesn’t just ring alarm bells; it sketches mitigation: harder prioritization, clear contribution contracts, and throttling feature intake until capacity improves. These are familiar prescriptions, but their urgency today feels louder given the broader conversation about software supply chains and project sustainability. Can a few process changes turn the tide before the backlog becomes a permanent fixture? Maybe — but only if projects accept that growth isn’t always a good thing.

A cold, useful lesson

The takeaway is simple and sobering: growth without capacity planning is not progress, it’s a debt. For anyone who’s watched an issue tracker balloon overnight, the model reads like a post-mortem and a warning. Read it, nod, and then ask the hard question: how will your project keep the promises it keeps making?

Sources: armanckeser.com, Hacker News