There is an unspoken assumption in global tech circles that serious software only originates in a handful of postal codes. The narrative suggests that unless you are sitting in a sunlit loft in San Francisco, an incubator in Berlin, or a glass tower in Singapore, you are simply a spectator—or at best, outsourced labor implementing someone else’s vision.
Every line of code I compile in Addis Ababa is a quiet rejection of that myth.
Sitting at 2,400 meters above sea level, beneath the eucalyptus-scented air of the Entoto hills, you learn quickly that building software here is different. You do not build in an insulated bubble of effortless infrastructure. You build amidst friction: intermittent connections, erratic power, banking isolation, and the daily noise of a city racing to reinvent itself.
Yet from this exact soil, software can be built that reaches children in nine languages across multiple continents, lands on Amazon bookshelves, and runs on millions of screens. The question is never whether world-class work can come from Ethiopia. The question is: What spirit animates it when it does?
“If your craft only works when the environment is effortless, you haven't mastered your craft—you've merely been pampered by your tools.”
1. The Ancient Ink in Modern Pixels
Ethiopians are not newcomers to information technology. We are an ancient scribal culture.
Centuries before the printing press existed in Europe, monks in Tigray, Gondar, and Gojjam were preparing goat parchment, mixing natural pigments from crushed minerals, and spending decades hand-lettering Ge'ez manuscripts with flawless geometric discipline. They understood something modern software engineers frequently forget: the container must honor the sacredness of the message.
When I design an application, construct an interactive storybook like Mare, or architect a Flutter database layout, I do not see it as disposable consumer software designed to hook attention for twelve seconds. I see it as a direct continuation of that scribal heritage.
A screen is just modern vellum. Code is just digital ink. If our ancestors spent years carving binding leather and hand-inking illuminated manuscripts that survived fires and centuries, why should our standards for a mobile application in 2026 be any less exacting?
2. Friction as a Sanctifying Discipline
It is easy to resent the friction of living and working in an emerging market.
When the power cuts midway through a long build, when internet packages throttle unexpectedly, or when international payment gateways deny your local card, the instinct is frustration. You look at Silicon Valley developers complaining on X about free lunch catering and wonder how much faster you could move with their safety nets.
Over time, however, you realize something liberating: Friction is a crucible.
Friction forces you to become lean. It prevents you from shipping sloppy, 150-megabyte applications because you know what bandwidth actually costs. It forces your code to handle timeouts gracefully because you understand what happens when a cell tower drops. It teaches you to build software that is tough, patient, and self-contained.
“A tree rooted in rocky soil develops deep, stubborn roots. A tree in a greenhouse falls over during its first storm.”
If your application can survive and deliver genuine joy to a child using a cracked, 1GB RAM phone in a regional town with zero cellular signal, it will run like silk on an iPhone 17 Pro in Manhattan. Building from friction does not compromise your standards; it elevates them.
3. The Idol of the "Exit" vs. The Gift of Stewardship
Much of global software development is driven by a hollow liturgy: Raise capital, burn money on customer acquisition, inflate vanity metrics, and exit.
The goal is rarely to serve human beings; the goal is to pass the hot potato to the next round of venture capitalists. The product becomes an instrument of extraction—extracting data, extracting attention, extracting subscription fees.
When you build from a foundation of faith, your perspective shifts entirely. Software is not an extraction scheme; it is an act of stewardship.
You are taking mathematical logic, creative beauty, typography, and narrative, and synthesizing them into a tool that enters someone's private life. An app sits on a mother’s phone. It speaks to a child before bedtime. It helps a student learn or provides solace during a difficult evening.
If that is true, then software is pastoral work in disguise. It demands reverence, honesty, and care. You do not trick users with manipulative dark patterns. You do not trap them in loops of notification anxiety. You build tools that bless them, respect their peace, and leave them better than you found them.
4. Telling Our Own Stories, Unapologetically
For decades, Africa has been portrayed as a consumer of culture, not a producer of it. When African stories were told globally, they were often filtered through external lenses—either framing our world through tragedy and deficit, or flattening our history into generic safari tropes.
Building from Addis Ababa allows us to challenge that dynamic at the root.
When I created Mare, it wasn't an imitation of Western fairy tales. It was born out of a Sunday sermon on the Good Shepherd, grounded in biblical truth, and infused with characters and moral weight that resonate universally precisely because they are authentic.
The world does not need another generic clone of an American productivity app or another derivative casual game. The world is starving for authenticity. It is looking for perspectives rooted in deep soil, rich history, and authentic spiritual conviction.
Principles for Building With Purpose
Reject the "Third-World Discount"
Never use your location as an excuse for poor design, sluggish performance, or broken UX. The standard is excellence, everywhere and always.
Honor the User's Attention
Do not design digital junk food. Build software that respects human dignity, avoids addictive traps, and provides genuine nourishment.
Embrace Local Constraints as Superpowers
Offline-first architectures, ruthless asset compression, and memory discipline aren't handicaps—they are competitive engineering advantages.
Master the Full Stack of Creation
Don't just write functions. Understand typography, illustration, narration, platform economics, and storytelling. Great products are symphonies, not isolated code files.
Work for an Audience of One
When you measure your success by Silicon Valley approval or vanity downloads, you are always insecure. When you build as an offering of faithful stewardship, you are free.
Bloom Where You Are Planted
You do not need to leave Addis Ababa to create something that shifts the world. The tools are here, the heritage is here, and the purpose is clear.
The Mountain and the World
Addis Ababa translates to New Flower. It is a city that has known heartbreak, resilience, renewal, and relentless faith.
As long as there is an electrical current to charge a laptop, a notebook to sketch an idea, and faith to believe that small beginnings matter, world-class software will continue to ship from these hills.
We do not build to escape where we are. We build to demonstrate what is possible from right here.
To build with purpose is to know that your work outlives your metrics.
From Addis Ababa, for the glory of God and the joy of the world.
