What is to be done
Yeah I’ve turned a bit commie recently. Anyways this isn’t about that, but shit happened in Portugal so I guess I could clickbait you into being a bit more aware about what’s happening in a country you probably don’t and won’t care about.
Tens of thousands of people marched through more than 30 cities and towns across Portugal on Saturday in the largest protest yet against soaring housing costs. Participants ranged from teenagers to retirees, and activists want limits on rent increases, stronger legal protection against eviction, and more affordable housing. There was this picture of this woman carrying a big ass carnation which is cool af.
I recently had this interaction with a “do-good”er in Montreal community who’s trying to build a platform for young children to learn about the different professions they could involve themselves in when they grow up. I didn’t know that beekeeper is a job that’s on the verge of extinction because not a lot of people are interested in that profession. 2025 study of beekeepers found that the average age of a beekeeper right now is about 59, which is craaaaaaaaazy.
So I was talking to this guy who is trying to get this thing running and I pitched him the idea of a Byte Club and he said, “I will never start a non-profit because volunteers are unreliable. I pay my people and they do work for me, people won’t work if they don’t have incentive”. This incentive is THE incentive: money.
I disagree. I think in our late capitalist world people have forgotten the idea that humans do things because of their ideals, philosophies, beliefs and a thousand other things other than just moolah. I don’t think he liked the idea of Byte Club at all, to be honest. So what is the idea of a Byte Club.
Tech deficit
I’m gonna dump some stats on you for a sec
- Nearly 9 in 10 nonprofit leaders say technology is vital to their fundraising, but most spend less than 3% of their budgets on it, while for-profit companies spent nearly 6% last year. (Chronicle of Philanthropy, 2025)
- 45% of nonprofits say they aren’t spending enough on technology, citing lack of budget (77%), lack of funder support (47%) and lack of donor support (38%). (NTEN)
- Funders don’t help much: only 11% of nonprofits say foundation grants contribute significantly to their tech budgets. (NTEN 2024 Digital Investment Report)
So there IS an issue here to be addressed. “The idea” is to provide this deficit for free. Gratuitement is scary to most people I’ve realised. Comment fait-on quoi que ce soit gratuitement? We bring in people who want to.
When I was in highschool, I used to be often scour the web (mostly for random reddit rabbitholes but sometimes) for things to do with the skills that I had (or lacked). I think I just want to help someone who wants to build for the sake of building. That’s why the idea was to pair these two groups together.
Highschool students looking for volunteering roles to revamp their resumes. People with passion but without a project to work on. Students with extra time on their hands to see a non-profit solve the problems they’ve been struggling with.
How you do be do be do ba
How’s it work though? We’ll find some of these non profits with this tech deficit. We find what they need exactly and how we can serve them the best we can. Everything goes through a proper legal process with contracts, NDAs and anything else that makes them comfortable with giving us the opportunity to help them. All we ask from them is time every week to look after and mould the project in the way that they would like.
We find passionate people interested in taking on these projects, next. We pair them in teams. If they need it, we teach them the craft of using the tools a real software team would use. In our epoch of clankers, even though the entry threshold into software development has fallen down significantly, the quality and maintenance thresholds of these projects have risen drastically. I’m not making this up, there are serious issues with the code we push nowadays. We need developers to learn different and new skills instead of asking claude to fix our bugs, but this time in all caps.
The drive to do things matters more than one’s inexperience. If you want to be something, you already are that thing. Contradictely, it truly doesn’t matter if you have always wanted to paint, until you’ve not picked up the paintbrush. We only want people to pick up paintbrushes and do something that actually matters.
How do you trust a bunch of kids with your project?
Going back to my Montreal guy for a sec. He said volunteers are unreliable and honestly? He’s kinda right. Caring about something doesn’t stop you from disappearing for three weeks because you have a chem midterm. I’ve been that kid. I’ve also been the guy waiting on that kid.
But I don’t think the answer is “pay them.” When a company hires a junior dev they don’t just trust them with prod on day one either. There’s a senior dev looking at their code, there’s a manager, there’s a whole system built around the fact that new people mess up. Nobody calls that unreliable, they call it onboarding.
So that’s sort of what we’re trying to copy. The projects have to be small. Not “rebuild our whole donor system” small, more like “make a form that goes into the spreadsheet you already use” small. If it only gets 70% done it should still be useful to someone. A lot of this is just saying no to projects that would eat a team alive.
Nobody touches anything scary at the start either. No donor data, no payments. You build a website or some internal tool first, you ship it, and then you get the harder stuff. Kinda like open source where you don’t get maintainer access because you showed up.
Every bit of code gets looked at by someone who’s done this before it ships. This is the part I care about the most, because this is where you find out the function claude wrote for you is gonna break at 3am, and nobody explains why to you when you’re vibe coding alone in your room.
And people will leave. That’s just a fact. So teams are 3 to 5 people, everything’s in a shared repo with docs, the nonprofit hears from us every week, and if someone goes quiet we check in and then we move on. No guilt trip.
The thing I keep coming back to is what happens two years later. A project that never ships is sad but whatever. A project that ships, gets used every day, and then breaks when nobody who built it is around anymore is way worse. So we pick boring tools that don’t need babysitting, we write docs a non-tech person can actually read, and we figure out who fixes stuff before we even start.
Also we’re just upfront with the orgs. You’re getting a team of students who want to be there and who are being supervised. You’re not getting an agency. Most people are fine with that once you actually say it out loud.
How do you make sure sensitive info doesn’t get into the wrong hands?
Mostly, you set it up so the students never handle the real data. Most of the projects you’re describing (a website, a sign-up form, an internal tool) can be built and tested without ever seeing a real donor or client record. NDAs are the backup to a system that doesn’t even use any data.
WILL IT WORK
Let’s see. Honestly it could flop. We might not find enough people who know what they’re doing to review the code, orgs might not trust a bunch of teenagers, kids might ghost anyway. But there are two gaps here: nonprofits that need tech and can’t pay for it, and kids who want to build something real and have nothing to build. I think that’s reason enough to try. Tens of thousands of people just marched across Portugal and nobody paid them to. People show up for stuff they believe in. I’m betting on that.