I work across product, design, engineering, and intelligent systems turning difficult constraints into software people can understand and organizations can rely on.
The problem worth solving
Connects to design + system01 / Selected work
Products shaped across interface, system, and operational reality.
A Windows desktop app for directing coding agents across several projects, where plans, code changes, tests, and delivery decisions stay reviewable by the developer.
Skoolbod’s LGA-wide school-management platform, giving LGA, zonal, school, teacher, and parent users their own workspace over the same school records.
A mobile app connecting administrators, teachers, students, and parents to school records, communication, academic activity, and reporting, with saved information still readable offline.
Turning everyday coding activity into a private, readable record without asking developers to maintain another system.
A mobile learning experience for building practical skills in Yoruba, Igbo, Hausa, and Swahili through lessons, quizzes, and everyday phrases.
02 / How I build
One Product Engineering practice, supported by four disciplines.
Find the decision that changes the product, not merely the next feature.
Make complex workflows feel considered, calm, and learnable.
Build the architecture and interface as one coherent product system.
Use AI where it improves judgment, throughput, or understanding.
03 / A decision is part of the product
Architecture becomes useful when its reasoning remains visible.
Why PostgreSQL over MongoDB?
School operations connect people, roles, classes, terms, assessments, and audit history. The decision optimized for integrity and change - not early schema convenience.
04 / Thinking
Notes on how I make product, design, and engineering decisions.
A retrospective decision note using school software as the example: start with the records the product can never get wrong, then pick the database that protects them.
How I brought structure, reusable components, complete validation, and consistent feedback to an existing codebase in my current role, and how the team adopted the standards.
A retrospective decision record: the two choices that turned a personal script into a product other developers could try.
My current review approach, kept separate from the specific standards a team has agreed to.
In Skoolbod Mobile, saving data on the phone was the easy part. The real work was deciding what people can do offline and showing them how fresh their information is.
What building AwenesOS shows about putting AI to work on real tasks while the person stays in charge.
Skoolbod serves administrators, teachers, students, and parents. Access stays easy to understand when it follows what each person is actually responsible for.
If there is an interesting product, engineering, design, or intelligent-systems problem worth discussing, reach out.