Journey

How I got here — the long version.

This isn't a list of responsibilities. It's the story of how curiosity turned into a craft, and how writing code turned into building products.

2019Chapter 1

Discovering Programming

Curiosity, a laptop, and Computer Science at Benin

It began while I was studying Computer Science at the University of Benin. I opened a JavaScript tutorial expecting a hobby and found a way of thinking. The first time a few lines of code changed something on a screen, I was hooked.

My earliest projects were rough, but they were mine. I realized software wasn't about syntax — it was about turning an idea into something real that another person could use. That realization never left me.

What I learned

—Momentum beats intensity — small daily steps compounded faster than any cram session.
—Curiosity is a skill you can practice.

HTMLCSSJavaScriptReact

2022Chapter 2

Shipping MVPs with Founders

Contract work at Abinci and Enterscale

My first real work was in the trenches with founders. At Abinci I led the frontend of an MVP from concept to production launch — and watched it help generate real revenue in its first operational cycle. At Enterscale I built the MVP for a team and project management platform.

Code stopped being a solo exercise and became a conversation with a business. I learned that engineering decisions are business decisions, and that shipping the right small thing quickly beats shipping the perfect thing late.

What I learned

—Working next to founders teaches you to translate goals into features.
—An architecture that bends with change is worth more than a clever one that breaks.

ReactNext.jsTypeScriptREST APIs

2023Chapter 3

Becoming a Product Engineer

Soft Web Digital — commerce, fintech, performance

At Soft Web Digital I led development of a multi-currency e-commerce platform with analytics, role-based access, and location-based pricing — and shipped fintech flows like bill payments, trading, and crypto integrations. I improved performance by 25% and felt it move real metrics.

This is where the question I asked myself changed. Not 'how do I build this?' but 'should this exist, and for whom?' I started measuring myself in problems solved instead of features shipped.

What I learned

—Performance is a feature users feel before they can name it.
—Design and business context make you a better engineer, not a distracted one.

Next.jsTypeScriptTailwind CSSGraphQL

2024Chapter 4

Scaling On-Chain Systems

Fend Group — a DEX, a launchpad, and $100M+ in volume

The problems got bigger. At Fend I built and maintained infrastructure for a blockchain DEX processing over $100M in on-chain volume, developed a launchpad with token creation, staking, airdrops, and locking, and led a community-driven platform on the Aptos blockchain.

I learned to care about the unglamorous things — SDKs, bridging, reconciliation, on-chain analytics — that hold everything up. The growth systems I built helped scale the platform from hundreds to thousands of active users.

What I learned

—Crypto's hard problems are distributed-systems problems in disguise.
—You can't fix — or grow — what you can't observe.

TypeScriptReact NativeExpoAptosEVMNode.js

2024Chapter 5

Building My Own Product

Leap — an AI content platform, built solo

I wanted to feel the whole loop, so I built Leap: an AI platform for generating audio, images, and video, with fiat and crypto payments and managed media storage. It collapsed a multi-tool workflow into one place and cut creators' production time sharply.

Being the engineer, designer, and support desk at once is humbling. It made me faster, more decisive, and far more respectful of everyone who does the parts of product I used to ignore.

What I learned

—Talk to users before you open your editor.
—The smallest lovable version is almost always smaller than you think.

Next.jsNode.jsExpressMongoDBZustandOpenAI

2025Chapter 6

AI, and What's Next

Where the craft is heading

AI didn't replace the craft — it raised the ceiling on what one engineer can attempt. I build with it daily and build products on top of it, learning where it's magical and where it quietly lies.

My focus now is trustworthy, product-grade AI experiences and the systems that make them reliable at scale. The frontier is moving fast, and I intend to keep shipping on it.

What I learned

—AI products are trust products first and model products second.
—The interesting work now is orchestration and evaluation, not just prompting.

OpenAIAI WorkflowsReal-time SystemsTypeScript

“I stopped measuring myself in features shipped and started measuring in problems solved.”

— Still the plan

Let's talk

Have an ambitious idea? Let's turn it into a product.

Whether it's a fintech platform, a developer tool, or an AI-powered experience — I love helping teams ship things people enjoy using.

Start a conversation