2025 Wrapped

I didn't start 2025 with a clear plan.

I started it with curiosity.

The goal for the first few months was simple — do as much as possible. Build things. Try ideas. Learn aggressively. Make mistakes early while the stakes were still low.

Optimizing for Learning

January to April was a period of experimentation. I explored new programming languages, including C#, not because I needed them immediately, but because I wanted to expand how I think about software. Different languages force different mental models, and I was intentionally collecting those perspectives.

At the same time, I started exploring side hustles and freelancing — mainly to understand whether it was a viable path locally.

That experiment didn't last long.

A Sobering Reality Check

Trying to freelance in Zimbabwe was disappointing. I quickly noticed how undervalued software work often is. Extremely low pricing. Cut corners. Rushed deliveries.

After serving just one client, I made the decision to step away. Not because I couldn't compete — but because I wasn't willing to compromise my standards or reduce my work to fit a broken market.

A Better Direction

Not long after, I joined the Codementor DevProjects Challenge — themed "Create a fast and secure blog using JAMstack."

Instead of building for clients, I started building for myself. I created a personal blog — a space to learn in public and think out loud.

March: Hackathon Season

March changed the pace completely. My school hosted two hackathons — one focused on fintech and the other on agritech. I formed and led teams for both.

Fintech Hackathon: We built a peer-to-peer money transfer system using NFC. We had a working prototype. We won first place and a $1,000 cash prize.

Agritech Hackathon: A deeply thought-out idea grounded in real agricultural challenges. We placed third, and that idea became what is now known as AgriLease.

By the end of April, the excitement wasn't about trophies. It was about possibility. We started asking bigger questions: What happens after the hackathon? How do these ideas become real products?

This phase was defined by one question: "What if?"

If the first part of 2025 was about asking "what if?", then April to August was about a much harder question:

"Okay… how do we actually build this?"

Coming off the hackathon wins, there was a lot of excitement — and honestly, a bit of pressure. Winning ideas is intoxicating. But somewhere between the applause and the group photos, reality kicks in: ideas don't scale themselves.

From Hackathon Energy to Real-World Thinking

AgriLease stopped being "that agritech idea we pitched" and started becoming something heavier — something real. I began looking at it less like a project and more like a responsibility.

I spent a lot of time thinking about: Who exactly are we building for? What problem actually hurts the most? What can realistically work in a Zimbabwean context?

This is where romantic ideas meet constraints. Limited access. Infrastructure gaps. Trust issues. Adoption friction. Payment realities.

The Uncomfortable Middle

April to August wasn't flashy. There were no prizes. No big announcements. Just long stretches of thinking, rewriting, discarding, and rethinking again.

• Not every feature deserves to be built first
• Some "cool" ideas are distractions in disguise
• Constraints aren't blockers — they're design inputs

Learning to Lead (Quietly)

I began the year thinking like a developer: "How do I build this?"

By August, my questions sounded more like: "Should this even be built right now?"

That shift came from friction. From tough conversations. From realizing that every technical decision has social, financial, and operational consequences.

Leadership, I learned, often looks like slowing things down so they don't fall apart later.

Building for Context, Not Ideals

One of the biggest lessons: building for Africa requires more than ambition. It requires empathy.

• Trust before scale
• Access before polish
• Reliability before innovation

April to August was about foundations. Quiet work. Uncomfortable work. The kind that doesn't trend online, but determines whether anything meaningful can exist later.

If the earlier parts of 2025 were about exploration and foundations, then September to December was about convergence.

Ideas started meeting reality. Questions started demanding answers. And the work I had been quietly doing began to take clearer shape.

From Thinking to Commitment

By September, I was no longer entertaining ideas casually. Some paths had been tested and abandoned. Others had survived scrutiny, doubt, and time.

AgriLease moved from a concept under evaluation to a direction I was willing to stand behind. Not because everything was figured out — but because enough had been pressure-tested to justify focus.

Structure Over Speed

The last months forced me to confront something uncomfortable: momentum without structure is fragile.

• Roadmaps instead of features
• Systems instead of shortcuts
• Documentation instead of demos
• Long-term sustainability instead of quick wins

Wearing More Hats

I still wrote code, but that was no longer the center of everything. I found myself thinking more about leadership, ownership, decision-making under uncertainty, and the weight of representing something bigger than myself.

Building a product also means building trust — with users, collaborators, and yourself.

Redefining Progress

Earlier in the year, progress looked like more commits, more ideas, more activity.

By the end of the year, progress looked like fewer but better decisions, clearer priorities, stronger foundations.

Not everything moved fast — but what moved, moved with intention.