This is a somewhat long read.
You already know my name by now. If you don't, just scroll up β It's somewhere on this page.
I believe in learning things the long (often harder) way. Not because I particularly enjoy struggle, but because struggle refines understanding. This website β whatever it is β exists because I believe in documenting my journey. Whether or not it's a wise use of my time is debatable, but it feels right to carve out a space to express my thoughts.
I've done a lot of things; some connected, some not so obviously. I started with code because it was something I could learn on my own, something concrete. It made sense. Over time, that curiosity pulled me into cybersecurity, then into web development, then into project management. Different directions, same mind. I didn't plan it that way. I just kept following what made me curious and what didn't leave me alone.
Most days, I don't have a neat story to tell about how it all fits. I've led teams and also broken things apart just to see how they work. I've written software, built security tools, managed people, and spent hours just thinking. It's not always clear how these experiences relate. But deep down, I believe the dots will connect. Maybe not today, maybe not soon, but eventually.
Right now, I'm still creating the dots.
I've come to accept that not everything I do has to make sense in the moment. That the path can look scattered, and still be a path. There's something freeing in that. I've stopped trying to force it all in a clean narrative. Instead, I'm leaning into the unknown β building, messing up, and trying again. There's a quiet kind of excitement in not knowing where it's all leading (not fear though, just curiosity).
I grew up in rural Nigeria, where access to technology was limited. That reality made the internet feel both miraculous and alien. It also made me think deeply about accessibility β not just in apps, but in knowledge. That part of me is still here, still questioning who gets left out and how we can do better.
I'm not building things to chase trends. I build because I want to understand. I want to solve real problems. I like the space where creativity meets logic β where things either work or they don't. I like that clarity. It's honest.
Somewhere along the line, I started managing projects. Not because I wanted to be in charge, but because I cared about making ideas move forward. I learned to coordinate people, solve messy human problems, and keep things going even when nothing goes as planned. That, too, felt connected to the rest β just in a different way.
Most of what I know, I learned by doing. Reading helps, but nothing sticks like experience. Unfortunately, that means I've made a lot of mistakes. I've built things that didn't work, led projects that could've gone better, and spent hours debugging problems that could've been avoided. But every mistake is a lesson. The internet is filled with passive consumption β content that makes you feel like you're learning without actually teaching you anything. I avoid that. I prefer deep engagement, building things with my own hands, and pushing through the confusion until something clicks.
I don't spend much time thinking about the hottest tech stacks or the latest frameworks. They change too often to matter. I focus on building things in the simplest way possible. Most new things are noise. I care about building useful things; the kind that quietly do their job without needing attention.
I still don't know how it all ties together. I just know I care deeply about the things I do. And that has to mean something.
So for now, I'll keep building, keep learning, keep writing. I'll keep following the questions that won't leave me alone. Maybe someday, I'll look back and the picture will be clear. The dots will connect. And maybe I'll even smile at how unsure I was.
But until then, I'm here. Building, learning, and exploring.
One dot at a time.
You could be anywhere right now, but you're here. And for that, I'm grateful.