How I Got Started
Before software engineering, I was a
graphic designer and a digital artist fascinated by game development. I spent a decent time working with Unity and C# to build interactive experiences, while using ZBrush, Maya, and Blender to create 3D assets.
This creative background taught me patience, attention to detail, and how to think visually about systems—skills that translate directly into how I approach software design today.
How I Think
I value clear trade-offs over rigid rules. No single tool or architecture is universally correct—the right choice depends on context, constraints, and long-term goals.
I'm drawn to problems at the intersection of engineering, product thinking, and developer experience. Whether I'm designing an API or shaping a system architecture, my goal is the same: to build solutions that are simple to adopt, easy to maintain, and durable over time.
What I Work On
Most of my work centers around developer tools, automation, and API-driven platforms. I enjoy exploring how workflows can be simplified and how emerging technologies—particularly in AI and automation—can be applied in practical, developer-friendly ways.
Projects like lazyPR and Formonger grew out of problems I encountered firsthand. They fit naturally into my work without anchoring my identity to any single product.
Location
I'm based in Nigeria. I care about building solutions that are globally relevant while being mindful of local realities such as cost, infrastructure constraints, and accessibility.
Beyond Code
Outside of building software, I'm a gamer and entertainment enthusiast. I believe downtime fuels creativity—some of my best ideas come from stepping away and returning with fresh perspective.
I've also taught at Aptech as a
graphic designer and web developer, sharing what I've learned with aspiring programmers. Working with students at summer camps reminded me why I fell in love with technology in the first place—that moment when something clicks and someone creates something they didn't think they could.
