Writing

Code problems have answers. You find the bug, you write the fix, you deploy, and it is done. Today I fixed a track filtering issue, corrected a database tagging problem, and pushed a creator attribution feature, all before dinner. The human problems are harder. Leads who have not uploaded their content. Participants sending messages asking what is happening. Mentors and assistants waiting for answers I did not have yet. And somewhere underneath all of that, a voice in my head asking whether I had taken on more than I could handle. Then a friend sent a voice note out of nowhere. Then I called my mom. Thirty eight years of teaching, nine as a headteacher, four as a super head. She told me to slow down. What she said next changed how I am approaching everything.

At 9am I thought the only problems I was going to be solving today were not code related. Maybe someone asking if they could join two tracks at the same time. Maybe a track change request. I was so ready to be IT Support and not a Senior Software Engineer. Then a message came in. One of the leads could not post anything. Four hours before the onboarding call, I had a 500 error, a broken allowlist, and a VARCHAR(50) column that had no business being that small. Here is what happened, what I fixed, and why I am not even a little bit embarrassed about it.

There is a particular kind of stress that comes with launching something you built yourself, for people who are counting on you, with a deadline that does not move. That was my reality in the two weeks leading up to Tech for Tomorrow Bootcamp Cohort 3. We had 215 accepted participants, 38 volunteer instructors and mentors, and a platform that technically existed but had not been tested under real conditions. What followed was six bugs, several late nights, a lot of SQL queries run directly against a production database, and a platform that is now, genuinely, working. This is the honest story of what broke, how I fixed it, and what it means to build infrastructure for a community you run entirely on voluntary hours.

Your bank account is not really yours. The moment money outside your usual pattern lands in it, they freeze it, limit your access, and make you explain yourself before you can touch your own funds. Bitcoin has no manager to report to. The rules are the same for everyone, no exceptions.

It is 3am. I just finished my syllabus. I feel extremely ambitious and motivated. Eight weeks ago I did not know what a UTXO was. Today I am announcing 100 days of Bitcoin code. This is me building from the inside.

My stand on whether bitcoin is the answer to Malawi's problem or if we should keep exploring stable coins

I built an app in one night. I pitched it to five sets of judges. I did not win. And somehow, this is the best I have felt about my career in a very long time.

There is no CEO of Bitcoin. There is no company that owns it. There is no government that controls it. For someone living in a country with a broken currency and an unreliable financial system, that feels like a Christmas present on a Sunday afternoon on 3rd of July

By the end of this article you will understand how Flutter moves users between screens, which widgets make that possible, and how to use them confidently in your own app.

Think about language. Someone born and raised in Malawi may naturally speak Chichewa, and someone born and raised in France naturally speaks French. A native application works in a similar way. it is built using the programming languages, tools, and design principles of a specific operating system.

Corpus Christi is one of my favorite days in the entire liturgical year. It celebrates the Eucharist, which is the heart of Catholic life and one of the most profound gifts our faith has to offer.

I had the bus fare. I had the accommodation. The ticket was the one thing I could not manage. So I wrote an email I almost did not send, made the case for why I deserved to be in the room, and waited. Two organizations said yes. This is the story of what happened next.

I thought Malawi's biggest problem was the missing infrastructure. Turns out, part of the problem is that the infrastructure already exists and most people do not even know about it.

While everyone else at that conference was debating how to scale, how to get compliant, how to reduce friction for the customers they already have, Malawi is still trying to solve a more fundamental question. How does a Malawian exchange kwacha for USDT at all.

I have accounts with National Bank of Malawi, Standard Bank Malawi, and NBS Bank. In my experience, accessing money internationally has been extremely unreliable. Sometimes cards do not work online. Sometimes transactions fail abroad. Sometimes you are limited to very small allocations that disappear almost immediately. You have money. The money exists. But accessing it outside the country becomes its own battle. So eventually, like many travelers, freelancers, and remote workers across Africa, you start relying on informal crypto networks to access liquidity internationally. You send kwacha locally and receive USDT through trusted intermediaries. Sometimes it is instant. Sometimes you wait while liquidity is sourced. Sometimes the rates are painfully high. But when traditional systems fail you, you move toward whatever works. That was me. And if I am being honest, that is still me whenever I travel.

Most developers use final and const… but not everyone actually understands them. This breaks it down in a simple way that finally makes sense.

There are only two places in all of creation where Jesus Christ is 100% present in this complete and glorified way: in heaven, at the right hand of the Father, and in the Eucharist.

I founded Women in Tech Malawi with a hashtag. At the time, I didnt have a strategy or a roadmap. I only had a thought: when someone searches for women in tech from Malawi, my posts should come up. What followed was three years of pretending it was just a community group while quietly running an organisation, mentoring people I had never planned to mentor and fighting an imposter that refused to stay quiet. This is a story of how I stopped running from what I had actually built

I gave myself 90 days to go from zero to job-ready as a blockchain engineer with just a structured roadmap, one project built from the ground up, and a daily log of everything I learn. Day 1 was about understanding what you are actually building on before writing a single line of code: how Ethereum differs from Bitcoin, what a transaction really contains, why gas exists, and how I mapped out the architecture of the project I will be building for the next three months. This is that log.

Most developers build things that work on their machine and stay there. Not because they lack talent or ideas, but because nobody showed them that the gap between a local project and a globally accessible product is smaller than they think. Cloud computing closes that gap. And you are already using it.

A guide for anyone who has been curious about open source but did not know where to begin, drawn from a fireside chat with Amanda Brock and Didas.

Inclusive Fintech Forum 2026 | Day 2 Reflections

Africa's financial infrastructure is being rewritten right now, not in the future. I spent Day 1 of the Inclusive Fintech Forum in the room where that conversation is happening. Here is what I learned.

I packed my entire life into two bags and moved countries in the middle of a crisis. It was impulsive, overwhelming, and the best thing I ever did.

Perfect is an illusion. If there’s always something to improve, then waiting for perfect means waiting forever. The moment I started, I learned more than I ever did while planning.

I was terrified to start freelancing in university. 'I'm not good enough,' I told my friend. Her response changed everything: 'You must start somewhere.' Here's how I built multiple income streams while studying and how you can too.

I went quiet for a while.