My path was not a straight line. Medicine taught me how to think under uncertainty. Software engineering taught me how to build systems that scale. Leadership taught me how teams create outcomes. Entrepreneurship is where those threads meet.
Chapter 01
Medicine and problem-solving
Training · M.B.B.S, Lagos State University (2012)
I trained as a physician. Medicine demands careful observation, structured thinking, and responsibility for outcomes that affect real people.
That discipline never left. It shaped how I diagnose problems, weigh trade-offs, and stay grounded when systems are complex and stakes are high.
Capabilities developed. Structured problem-solving, decision-making under uncertainty, and responsibility for real-world outcomes.
Chapter 02
Discovering software engineering
Early craft · Web design & application development
I discovered software as another way to solve problems—faster loops, broader reach, and the ability to build tools people use every day.
I learned by building: interfaces, backends, databases, and the quiet infrastructure that makes products reliable.
Capabilities developed. Building interfaces, backends, databases, and reliable application systems.
Chapter 03
Building enterprise products
Bytes Technology · IBAKATV · Gokada
I built and shipped products across enterprise systems, streaming, and logistics—environments where reliability, performance, and delivery under pressure matter.
Those years taught me how organisations actually adopt technology, and how product decisions look different from the inside of a shipping team.
Capabilities developed. Shipping under constraints, product delivery, reliability and maintainability, and understanding organisational technology needs.
Chapter 04
Growing into technical leadership
IBAKATV · SeamlessHR (2021–Present)
Leadership meant more than writing code. It meant architecture, mentoring, clarity of priorities, and helping teams ship with confidence.
At SeamlessHR I contribute as a Technical Lead and Senior Full-Stack Engineer—experience that continues to sharpen how I think about systems, teams, and delivery.
Capabilities developed. Architecture, mentoring, prioritisation, cross-functional communication, and helping teams deliver.
Chapter 05
Understanding a systems gap
Observation → conviction
I kept meeting capable developers who struggled less with ability than with fragmented paths to being seen, trusted, and connected to meaningful work.
That gap looked less like a personal failing and more like missing infrastructure: places to learn in public, collaborate, show evidence, and find opportunity.
Capabilities developed. Applying systems thinking to ecosystem-level problems beyond a single product backlog.
Chapter 06
Founding Africoders
Founder & CEO
Africoders is my response to that gap: a people-first platform where African developers and builders can learn, build, collaborate, showcase real work, and grow careers.
It connects developers, students, professionals, mentors, recruiters, startups, companies, and communities around demonstrated work and durable relationships.
Capabilities developed. Founding and leading a product and community platform with a long-term ecosystem thesis.
Chapter 07
What comes next
Building in public
The work ahead is patient and ambitious: deepen Africoders, keep shipping useful product surfaces, and continue writing and speaking with care.
Medicine and engineering were never disconnected chapters. They prepared me to build with empathy, systems thinking, and a long view.
Capabilities developed. Sustained founder execution alongside selected technical consulting, advisory, and public communication.