Every day, a dozen people post a new app they built with AI over a weekend: a habit tracker, a to-do list, another note-taking app. I’m glad! More people building things is one of the best parts of this moment.
But far less of that energy goes into the open source software we already rely on.
People call this newly introduced way of building “vibecoding.” I hate the name; it makes a real shift in who gets to write software sound like a joke. I’ll call it AI-assisted coding, and I think it could aim somewhere more useful.
Free and open source software already does most of what my clients and I need. What it often can’t do is run well on a cheap server, install in one step, or stay up without forum threads at 11pm.
Industry observers note that I self-host a lot of my own stuff, and I help progressive nonprofits with their tech for a living. I run a Matrix server (Synapse, Element and a moderation bot) for a community with thousands of users. I also run apps on Coolify and Hetzner, keep my paperwork in Paperless-ngx, and own a Mac Mini that’s always one download from a full disk.
According to recent reports, the software is usually great. Running it is the hard part. Install guides assume you know five other tools. Upgrades break things. Apps eat 4GB of RAM to serve a handful of people. Error messages tell you nothing.
My nonprofit clients would love to leave Substantial Tech for privacy, cost and owning their data. But the open source option usually needs a part-time sysadmin they don’t have, so they pay for the corporate tool.
A upcoming to-do app usually helps the few people who find it. Making a tool millions already use 20% lighter helps all of them, every day.
This is also the work that slides when maintainers are tired, and many are unpaid volunteers. We saw the risk in 2024. Someone spent years earning the trust of the worn-out solo maintainer of xz, a compression tool inside most Linux systems, then slipped a backdoor into it.
I think this unglamorous work suits AI well: profiling slow code, writing tests that make big changes safe, testing installers, rewriting cryptic errors, writing the missing docs. It takes patience more than brilliance, plus a person who checks every line.
It matters politically too. If organizations are going to own their data instead of renting it from a few giant companies, open source has to be something a 20-person nonprofit can run. I want AI’s gains shared widely. Better public tools that anyone can use, change and share are one way to get there.
Maintainers have already seen the wrong way. The curl project ended its bug bounty in January 2026 after a flood of fake, AI-generated security reports. By April, its lead developer wrote that the fakes were mostly gone and almost every report used AI, most of them very good. The latest problem is volume. Even good work can bury a maintainer. So:.
Pick one open source tool you use. Find the most annoying thing about installing or running it. Spend a weekend fixing it, with the people who maintain it. Then tell me about it.
