About
From feature builder to systems engineer.
I started as a developer who could build and fix web app features. Today I work at the intersection of software engineering, product implementation, workflow design, applied AI, automation, data extraction, and operational problem-solving.
The growth happened across several dimensions at once — from frontend and backend delivery into full product ownership, from building pages into designing workflows and architectures, from coding apps into building AI-powered systems and data pipelines, and from single features into multi-module business platforms.
What makes the experience useful is not the count of tools. It is the kind of system I can take responsibility for: real workflows, operational rules, enterprise integrations, structured data handling, AI-assisted processing, and interfaces that both an administrator and an end user can actually use.
Nearly everything here I built alone — architecture, backend, frontend, deploy and documentation. Where I inherited a codebase, I owned it from that point on. The handful of shared builds, where I took the front end and someone else the back or the reverse, are marked as such in the archive and claim only my half.
I'm not only a React/Node developer, or only an AI tinkerer, or only a scraping engineer. I take a business problem, translate it into a system, and implement the web, backend, automation, AI and data pieces needed to make it work.
Journey
How it went.
Cross-Domain Systems Builder
Operating at the intersection of full-stack engineering, AI systems, mobile delivery, automation, and data pipelines. Driving end-to-end product architecture for Pikora Phase 2 (Flutter + Xano + Azure ML) and owning multi-layer builds from concept to deployment.
AI Systems & Automation Engineering
Expanded into YOLO/ONNX model deployment, RAG pipelines, GPT-powered extraction systems, and production automation (Shopify, CRM, content). Built supplier ingestion engines, scraping pipelines, ERPNext/Odoo evaluations, and owned end-to-end architecture on multi-user platforms.
Full-Stack Product Ownership
Shipped full products end to end — Abaya e-commerce (Next.js + Paystack + S3), Play & Win, and a bulk image platform. Moved from building features to owning auth, payments, dashboards, deployment, and documentation.
Scraping & Data Pipeline Growth
Built stealth scrapers (Etsy, Google Maps, authenticated sites), structured extraction pipelines, OCR-based book extraction, and data normalization systems. Learned to handle anti-bot patterns, session-based auth, and structured output design.
Frontend to Full-Stack Transition
Grew from frontend feature work into backend ownership — Express APIs, MongoDB schemas, auth flows, file uploads, and deployment. Started contributing to Pikora Phase 1 frontend and exploring AI/ML tools.
Foundation: Web Development
Built the initial foundation in React, JavaScript, HTML/CSS, and basic Node.js. Focused on learning component architecture, responsive design, and client-facing delivery.
Principles
What I hold to, regardless of stack.
Ownership over tickets
I think in systems, not tasks. When I take on work I own the problem end to end — from understanding the business need to the deploy and the runbook.
Clarity over cleverness
Code, documentation and architecture that other people can follow. A complex system that only I can operate is a liability I created.
Confidence, not just output
Anything extracted, scored or predicted carries a confidence value. A pipeline that is quietly wrong 20% of the time is worse than one that admits it doesn't know.
Ship, then refine
Working software first, improvement second. Perfectionism that blocks delivery costs more than a shipped system with known trade-offs.
You have a process thatshould be a system.
Tell me what arrives, who has to act on it, and where it currently falls over. That conversation is usually enough to scope the build.