DEV Community: Michael Clay

What Building DigiCow at the Kenya AI Challenge Taught Me Beyond Writing Code

Michael Clay — Sat, 04 Jul 2026 20:00:24 +0000

Hackathons have a funny way of teaching you lessons that no tutorial, documentation page, or YouTube video ever could.

For the past few weeks, my team and I lived and breathed one project: DigiCow.

From day one, we had our eyes on the prize. But somewhere between the late nights, debugging sessions, architecture discussions, and countless cups of coffee, the goal quietly shifted. It stopped being just about winning—it became about building something we were genuinely proud of.

Together with Mercy Moraa, Taheera Mohamed, Nyaboke Grace, and Millicent Odhiambo, we started with nothing more than an idea and a challenge statement from the Kenya AI Challenge. Over the following weeks, that idea evolved into a fully functional AI-powered solution.

Like every software project, the journey was anything but smooth.

Every time we solved one problem, another one appeared waiting for us. APIs failed. Features had to be redesigned. We rewrote logic that we thought was already perfect. Some nights ended with more questions than answers.

But that's software engineering.

The Demo Day Lessons Nobody Talks About

One of the biggest lessons from the experience had nothing to do with AI or backend development.

It had everything to do with being prepared.

During the final presentations, two different teams encountered something that many student developers can relate to: their free-tier API credits ran out.

One team relied on a telephony API.

Another depended on ElevenLabs for voice generation.

Their applications had worked perfectly during development, but on presentation day, the services they depended on had exhausted their free credits. A feature that had been central to the demo suddenly wasn't available.

Watching that unfold reminded me that deploying software isn't only about writing code—it's also about managing the services your application depends on.

It sounds simple, but it's a lesson I'll never forget:

Always check your API quotas before an important presentation.

Whether you're using OpenAI, ElevenLabs, Twilio, Africa's Talking, Google Cloud, Firebase, or any other service with usage limits, make it part of your deployment checklist.

Because nothing is more painful than discovering you've run out of credits while standing in front of judges.

Teamwork Is Still the Greatest Technology

While we each had different strengths, nobody worked in isolation.

Ideas bounced around the room.

Problems became everyone's problems.

Victories became everyone's victories.

The best software isn't built by the smartest individual in the room. It's built by teams that communicate well, trust each other, and keep moving forward when things get difficult.

Looking back, that's what I'll remember most.

We Didn't Win—But We Didn't Lose Either

Like every team, we wanted to win.

We truly believed in our solution.

This time, another team came out on top, and they deserved every bit of it. Congratulations to all the winners.

But walking away without the trophy doesn't mean walking away empty-handed.

We left with something far more valuable:

A real product we built from scratch.
Experience working under pressure.
Better technical skills.
Stronger teamwork.
New friendships.
Lessons that will shape every project we build from here onward.

Those are things no certificate can measure.

My Biggest Takeaways

If I had to summarize the experience into a few lessons, they'd be these:

Build for impact, not just for the judges.
Test your application exactly as you'll demonstrate it.
Check your API usage and free-tier limits before every presentation.
Expect things to go wrong—and have a backup plan.
Great software is built by great teams, not individuals.
Winning is rewarding, but learning is priceless.

Final Thoughts

Standing on that stage and pitching DigiCow was one of the proudest moments of my journey as a developer.

Not because everything went perfectly.

But because I could look back and see just how far we'd come—from a blank page to a working product solving a real problem.

To my teammates—Mercy Moraa, Taheera Mohamed, Nyaboke Grace, and Millicent Odhiambo—thank you for believing in the vision and giving it everything you had.

To the organizers of the Kenya AI Challenge, thank you for creating an environment where young developers can build, learn, compete, and grow.

And to every developer preparing for their next hackathon:

Build boldly.

Test everything.

Check your API credits.

Then go tell your story.

Because sometimes, the most valuable thing you bring home isn't the trophy—it's the experience.

What a Backend Frameworks Mini-Conference Taught Me About Choosing the Right Tool

Michael Clay — Sat, 04 Jul 2026 19:53:43 +0000

One of the things I appreciate most about being at Zone01 Kisumu is the culture of continuous learning. This week, I attended my second mini-conference, where the topic of discussion was backend frameworks.

Rather than comparing frameworks to determine which one is "the best," the speakers focused on something much more important: understanding where each framework fits.

Starting with the Fundamentals

The conference opened with an excellent presentation by Clare Gisore, who walked us through the foundations of backend development. Before discussing any framework, it's important to understand the role a backend plays in an application—handling business logic, communicating with databases, managing authentication, exposing APIs, and much more.

That foundation made the rest of the sessions much easier to follow.

Django: Rapid Development

Bramwel Mutugi introduced us to Django and demonstrated why it has become one of the most popular Python frameworks.

Some of the key takeaways included:

Rapid development
Built-in authentication
Strong security features
Excellent for database-driven applications

The session gave me a practical understanding of where Django excels and why many startups choose it.

Java Spring Boot: Enterprise-Ready Development

Haji Ibrahim and Richard Ochola showcased Java Spring Boot using examples from the Loot platform they are currently building.

Seeing a real project made the concepts much easier to understand. The presentation highlighted why Spring Boot is trusted for large-scale applications where scalability, maintainability, and performance are critical.

Ruby on Rails: Convention Over Configuration

Paul Oguda wrapped up the event by introducing Ruby on Rails.

Although I haven't built a Rails application yet, the philosophy behind it immediately caught my attention. Rails emphasizes developer productivity through conventions, allowing developers to focus more on solving problems than configuring projects.

It definitely left me curious to explore it further.

The Biggest Lesson

If there is one lesson I'll carry forward, it's this:

Frameworks are tools—not trophies.

It's easy to chase whatever framework is trending on social media or job boards, but choosing a framework should always depend on the problem you're solving.

Every framework has strengths, weaknesses, and ideal use cases.

A good developer understands why they're choosing a tool—not just which tool they're choosing.

The framework doesn't define the developer. The developer defines how effectively they use the framework.

Final Thoughts

Events like these remind me that learning software development isn't just about reading documentation or writing code alone. It's also about learning from other developers, understanding different perspectives, and seeing how people solve real-world problems.

A huge thank you to everyone at Zone01 Kisumu and LakeHub for organizing these mini-conferences. They continue to create an environment where developers can learn, share knowledge, and grow together.

I'm already looking forward to the next one.

What backend framework are you currently using, and why did you choose it? I'd love to hear your thoughts in the comments.

BITCOIN HACKATHON

Michael Clay — Sun, 21 Jun 2026 18:31:24 +0000

After a full week of intensive Bitcoin programming training, the developers at Zone01 Kisumu moved into the most exciting phase of the bootcamp: building real-world solutions powered by Bitcoin, the Lightning Network, and LND.

One thing I learned throughout the experience is that the human mind is truly fascinating. The room was filled with innovative ideas, each attempting to solve a different problem. As the saying goes, no idea is a bad idea—every concept had the potential to make an impact.

A total of 17 teams were formed, and each team embarked on a 24-hour hackathon journey to transform their ideas into working products. After an intense day of development came the presentation phase, where we had the privilege of showcasing what we had built.

Our team developed Kasi, a WhatsApp chatbot that enables Bitcoin transactions directly through WhatsApp. The goal was to make Bitcoin payments more accessible by leveraging a platform that millions of people already use daily.

To build Kasi, we integrated the Twilio API for WhatsApp communication and utilized the Bitnob platform to facilitate Bitcoin transactions. Python was used throughout the development process. The project was brought to life by six developers: Claire, Lamka, Ijay, Dishon, Talo, and myself.

Beyond the technical implementation, the hackathon strengthened our understanding of collaborative software development. We practiced Git workflows, team coordination, version control, task management, and effective communication under tight deadlines—skills that are just as valuable as writing code.

Although we did not finish at the top of the leaderboard, the experience was incredibly rewarding. Every team brought something unique to the table, and the winners fully deserved their recognition. Congratulations to all the teams that participated and showcased their creativity, determination, and technical skills.

One moment from the presentation will stay with me for a long time. As we were demonstrating Kasi to the judges, the free Twilio trial credits we had been relying on ran out. Imagine the panic. One moment the demo was working, and the next we were standing in front of the judges trying to explain and maneuver around an issue we never expected to happen at that exact moment.

It was painful, frustrating, and almost comical at the same time. But that's the reality of software development—sometimes the biggest lessons come from things that fail when you least expect them to. It's a lesson our team will never forget.

Developer tip: Always double-check your free-tier limits, API quotas, and trial credits before a live presentation. Trust me on this one.

This bootcamp and hackathon reinforced my passion for technology and problem-solving. It reminded me that innovation begins with an idea, but impact comes from taking that idea and turning it into something real.

I hope that one day, through the ideas I develop and the technical skills I continue to build, I will create solutions that make a meaningful difference in people's lives.

⚡ Build. Learn. Collaborate. Improve. Repeat.

BITCOIN

Michael Clay — Fri, 19 Jun 2026 17:53:01 +0000

Last week was nothing short of epic—a week filled with new experiences, hands-on learning, and moments that will stick with me for a long time.

We had the privilege of hosting Bitcoin Kenya, and the sessions opened up an entirely new perspective on Bitcoin, the Lightning Network, nodes, mining, and the technology that powers decentralized finance.

The best part? It wasn't just theory.

We got our hands dirty by setting up Bitcoin nodes, mining blocks, and exploring how transactions move from one person to another. Seeing the process in action helped me understand how miners secure the network, earn through transaction fees and block rewards, and why Bitcoin's design is still one of the most fascinating engineering achievements ever created.

I also learned that the last bitcoin is expected to be mined around the year 2140—a future that's over a century away. Whether we're around to witness it or not, it's incredible to think about a system that was designed with such long-term vision.

One thing is certain: the impact of Satoshi Nakamoto on technology and finance is undeniable. Whether Satoshi is one person or a group of developers, the innovation has inspired an entire generation of builders and problem-solvers.

The bootcamp also gave us the freedom to build using either Go or Python, and since I have some experience with both, I got the opportunity to experiment and learn from each ecosystem.

Overall, it was an amazing experience, and I genuinely hope to see the Bitcoin community expand its presence in Kisumu so that even more developers and enthusiasts can benefit from opportunities like this.

Fun Facts

🔸 1 Bitcoin is divisible into 100,000,000 satoshis (sats), the smallest unit of Bitcoin named after its creator's pseudonym.

🔸 To this day, nobody knows whether Satoshi Nakamoto is an individual or a group of developers.

🔸 Satoshi is estimated to control around 1.1 million bitcoins, coins that have remained untouched since they were mined.

🔸 Bitcoin's supply is capped at 21 million coins. While anyone can modify the source code and remove that limit in their own version, the broader Bitcoin network only accepts changes through community consensus—simply changing the number won't change Bitcoin itself.

A huge thank you to everyone who organized the bootcamp. Experiences like these remind me that the best way to learn is by building, experimenting, and asking questions.

Here's to more code, more blocks, and more learning.
₿