Progression, not résumé
The journey
This is not a story of a perfectly linear career. It is a record of repeatedly learning how systems work, where they fail, and what it takes to improve them.
From foundations to systems building
Chronology supports the story; it does not replace it.
Foundations
Lagos
I attended Apata Memorial School in Lagos and later Atlantic Hall. Mathematics came naturally to me. Early setbacks taught me to keep building, refine my approach, and recognize how rules, constraints, timing, and system design shape outcomes.
Education
Windsor
I moved to Canada and studied computer science at the University of Windsor. Learning across software, people, and execution became increasingly relevant as the problems grew larger than code.
Independent building
Products under real constraints
Independent work became a practical school in understanding needs, building answers, communicating value, and learning that a technically correct product can still fail if the surrounding system is misunderstood.
Industry systems
Performance, reliability, and analytics
Work across complex organizations deepened the focus on performance, reliability, search, analytics, software systems, and the decisions surrounding them. Confidential work remains intentionally unnamed.
Performance engineering
Measure, locate constraints, verify change
Performance work sharpened a way of reasoning about systems: observe real behaviour, determine which signals matter, locate constraints, make a change, and verify what happened.
Current direction
Measurement, simulation, and public systems
The work now spans TraceLayer, NigSim, TraceLayer Lab's Browserapy experiment, civic and community infrastructure, and experimental decision systems. These projects differ in maturity and purpose, but share an interest in making complex behaviour understandable and testable.
The broader direction
The industries and domains changed. The underlying work became clearer.
Measure the system. Model its behaviour. Understand what matters. Act and verify.