Why half our work funds coding education, not shareholders
200+ students taught, 15+ communities reached, 50+ graduates employed. Here's what actually goes into those numbers, and why we treat this as core work, not CSR.
Commercial work funds the other half of what we do: building computer skills in communities that don't have access to technology education. That line sounds like a mission statement, and it is one — but it's also a literal description of how the business is structured. This isn't a CSI budget line we top up when the year goes well. It's built into how we plan capacity from the start.
Three pillars, not one programme
Skills development. We run coding workshops in underserved communities that teach practical, employable skills — not theory for its own sake. That means weekend coding bootcamps, mentorship pairing with working developers, portfolio-building projects students can actually show an employer, and job readiness coaching that goes beyond the code itself.
Community building. Tech communities don't appear because a workshop happened once. We help start and sustain local developer meetups and study groups — monthly meetups, study group facilitation, conference scholarships for people who couldn't otherwise attend, and online spaces that keep the connection going between events.
Industry access. Learning to code and getting hired are two different problems, and the gap between them is where a lot of good intentions go to die. We work on the second half directly: internship placements, junior role referrals, freelance project matching, and CV and portfolio reviews that come from people who've actually sat on the hiring side of that table.
What the numbers represent
200+ students taught, across 15+ communities, with 50+ graduates now employed, through 12 partner organisations. Numbers only tell part of the story — behind each one is a specific person who went from no access to technology education to holding a role that didn't exist for them before. We don't publish these to look impressive; we publish them because they're the only honest way to check whether the mission is actually working, not just running.
Why this isn't charity bolted onto a software company
Skills gaps compound. A student without access to a laptop, reliable transport, or someone senior willing to explain a stack trace doesn't lack potential — they lack the specific, addressable things that turn potential into employability. Those are solvable problems, and they're problems a software company is unusually well positioned to solve, because we already employ the people who can teach the skill and hire the graduate.
We're always looking for partners who want in on this side of the work — schools and educational institutions in underserved areas, non-profits working on digital inclusion, companies with CSI or BBBEE-aligned budgets looking for a programme that produces employed graduates rather than a certificate of participation, and developers willing to mentor. Start a conversation if that's you.