The Mango, the Grant, and the Code: Why I'm Building for the Africa That Isn't Online

I watched a video last week that stopped me mid-scroll.

A man from Malawi—he calls himself Blaw-Da online—was sitting outside his home, speaking quietly to a phone camera. He hadn't eaten dinner the night before. At sunrise, he picked mangoes from a tree to gain strength for the day ahead.

He wasn't asking for help. He was explaining why life pushes people like him to South Africa, and why so many never go back.

He talked about grants. In South Africa, we have SASSA—flawed, yes, but functional. In Malawi, he explained, grants are handled manually. Government officials visit villages with notebooks, collect names, and later cash those grants for themselves. There is no system. There is no trace. There is only trust, and trust, when you're hungry, is a luxury you cannot afford.

He talked about bread being a privilege. About sugar becoming unaffordable not because of luxury, but because income simply stops. About children walking to school without uniforms, let alone lunch, and how in his community, no one judges—because everyone understands.

I have thought about this video every day since.

The Honest Reckoning

I need to be honest about something.

If you look at my work today, you'll see someone who builds practical solutions for businesses. You'll see a pragmatist focused on escaping legacy systems—technical debt, slow databases, outdated architectures. My view was shaped by South Africa's context: we have systems, but they're aging, brittle, and in need of modernization. My mission was to help companies replace technical debt with clean, scalable code.

That was true. It still is, partly.

But my view was also narrow. I hadn't looked properly at what "legacy systems" means elsewhere on our continent.

Before this video, I also found myself nodding along to voices I'm not proud of. Voices that say we should close our borders, protect what's ours, support movements like Operation Dudula. I told myself it wasn't xenophobia—it was consideration. We aren't so different, I thought. If we do nothing, we'll end up like them.

That last sentence haunts me now. Because it's true, but not in the way I meant it.

We aren't so different. That's exactly the point.

If SASSA collapsed tomorrow. If Home Affairs' servers burned down. If South Africa's systems became notebooks and broken trust—we would be them. The only difference between us and Blaw-Da's community is infrastructure. Working, accountable, digital infrastructure.

Which means the solution isn't walls. It's systems.

The Problem I Couldn't Name: Manual Debt

I've spent my career helping businesses escape technical debt. But technical debt assumes there was once a working technical system. It assumes servers, databases, code—things that got messy over time and need cleaning up.

That's South Africa's problem.

Blaw-Da's problem is different. His community never got the servers. They never had the databases. Their systems are still notebooks, word of mouth, and trust placed in officials who exploit it.

Let's call this manual debt.

Manual debt is what happens when a grant meant for a hungry child is cashed by an official because there's no audit trail. It's what happens when a farmer sells below market price because information travels by word of mouth. It's what happens when a child grows up without an ID because the office is three hours away and the paper files were "lost."

Technical debt slows companies. Manual debt starves people. It steals dignity. It pushes families across borders.

Blaw-Da's story made me realize: my skills aren't just for helping South African businesses scale. They're for helping entire communities across Africa access the digital infrastructure that should have been built decades ago.

The Pivot

So here is my new mission, stated plainly:

I build scalable digital infrastructure that powers local communities and expands to uplift our neighbors—removing the technological barriers that keep access slow, corruptible, and uneven.

Not instead of my current work. In addition to it. The same pragmatism, the same clean approach, the same obsession with systems that actually work—just pointed at a bigger problem.

Blaw-Da's community needs:

• A grant distribution system that can't be stolen from
• An identity system that doesn't depend on a notebook
• A way to know fair prices without a middleman
• Tools that work on the phones people actually have, in the languages they actually speak

These aren't separate problems. They're the same problem: opacity. When systems are invisible, corruption thrives. When data doesn't flow, poverty pools.

The Pragmatic Stack

I've been deepening my skills in Go lately. This video gave that work new meaning.

But more important than any specific language is the approach. The tools don't matter if they don't solve the real constraints on the ground.

So here is my pragmatic tech philosophy for this mission:

The stack was always pragmatic. Now it has purpose.

What This Article Is (And Isn't)

This isn't a resignation from client work. It isn't a naive claim that code alone saves people. It isn't me pretending I have answers I don't.

This is a north star.

I'm publishing this so that six months from now, when I'm deep in a debugging session at 2 AM, I can look back and remember why. I'm publishing it so that other engineers who feel the same disconnect—between our skills and our continent's needs—might reach out. I'm publishing it because Blaw-Da sat outside his home and told his story to a phone, and the least I can do is listen, and then build.

Common Objections Addressed

"Isn't this just tech solutionism?"

Technology alone doesn't save anyone. But opaque systems actively harm people. Building transparent, auditable infrastructure doesn't solve corruption by magic—it removes the cover that corruption depends on. When a grant is claimed, the community sees it. When an official steals, there's a record. That's not solutionism. That's accountability.

"Can you really build this as one person?"

No. But I can start. I can build prototypes, find partners, connect with organizations already doing this work. RuDASA showed me what's possible when tech meets advocacy. This is the same lesson, scaled outward.

"What about maintenance and local ownership?"

This is critical. Any system I build must be simple enough that local developers can maintain it. It must run on local hardware. It must not create dependency on me or any outsider. The goal is infrastructure that communities own themselves.

Lessons Learned

1. Friction is signal — If a story stays with you for days, pay attention
2. Manual debt is real — Technical debt assumes systems exist; manual debt assumes they never did
3. Xenophobia misdiagnoses the problem — People aren't the problem; broken systems are
4. Pragmatism scales — The same approach that helps businesses helps communities
5. North stars matter — Write down your mission so you can return to it

A Request

If you're building something similar—identity systems for underserved communities, transparent aid distribution, offline-first tools for rural users—I want to hear from you.

If you're an engineer wondering how your skills connect to something bigger, let's talk.

And if you're Blaw-Da, wherever you are: thank you. Your mango breakfast reached further than you know.

---

The video that sparked this reflection: Life in Malawi by Blaw-Da on Facebook