I started with the screen. Then followed the system behind it.

I studied the human body before I studied software.

My first degree was Human Anatomy at the University of Port Harcourt. It had nothing to do with Flutter, distributed systems or API design. That matters, because my path into engineering wasn’t inherited from a computer science classroom.

I had to deliberately learn how computers work, how software is built, and eventually how production systems fail.

CS50 made the switch feel real.

Programming stopped being something I was exploring and became something I could see myself doing seriously. I worked through computer science fundamentals, then moved quickly toward building actual software.

Flutter became my way into production engineering.

Mobile gave me an immediate feedback loop. Architecture mattered because users could feel bad architecture. Networking mattered because requests failed. State management mattered because screens had to remain coherent. Releases mattered because the App Store did not care about excuses.

At Chigisoft I worked across products including Flitaa, RCCG, Pointograph and Eaglesnest. At SendChamp I led mobile delivery for Bodsquare. At QuickCollect I helped rebuild a money-transfer product used across iOS and Android.

The client stopped being enough.

I wanted to understand the systems my applications depended on, so I studied backend engineering with Go and began taking on more server-side responsibility.

That became production work: Go services, MongoDB, Redis, APIs, authentication, realtime systems, provider integrations, Docker and cloud deployments.

On products like JollofDate, the boundary became increasingly irrelevant. A feature might begin in Flutter, continue through a Go service, touch Redis or MongoDB, pass through Twilio or SendGrid, and finish in an admin interface.

Then I started engineering the layer other developers integrate.

At Codematic, my work expanded into developer SDKs. I own SDK implementations across Flutter/Dart, Android/Kotlin, iOS/Swift, Go, PHP and Python.

The interesting problem is not rewriting the same feature six times. It is defining one product behaviour, then making it feel native and reliable in six different ecosystems.

Identity, networking, push notifications, event tracking, realtime messaging, lifecycle management, retries, packaging, documentation and release compatibility all become part of the product.

I was brought into GreenWallet because the system needed to become dependable.

The engagement was intentionally short: three months, alongside the product manager, focused on stabilizing an existing fintech platform.

I took over the backend, worked through its architecture and financial flows, hardened ledger and transaction behaviour, improved reconciliation, strengthened payment-provider integrations and built the operational controls around them.

I also worked alongside an external penetration-testing team, reviewed the vulnerabilities they identified and implemented the engineering remediation across authentication, authorization, webhooks, sessions, rate limiting and sensitive-data handling.

“Flutter developer” became too small a description.

Flutter is still a major part of how I work. But today I am comfortable moving between the application a customer touches, the SDK a developer integrates, the service handling the request, the database preserving its state and the infrastructure responsible for keeping it alive.

I think of that simply as software engineering.