8+ years of professional software development. Full-stack applications, APIs, integrations and cloud infrastructure—with independent experiments clearly marked.
Professional experience / Most recent first
Quest History
Every production incident was a boss battle.
Software engineer with 8+ years of professional experience building and maintaining web applications, REST APIs and SaaS products. Strong PHP and Laravel background, complemented by Node.js, NestJS, Vue.js, and hands-on AWS and Azure operations. Dates are shown as supplied, including overlapping engagements. LinkedIn profile
—
AREA 17
Software Engineer
Application delivery and ongoing support within AREA 17’s Care program, alongside hands-on AWS and Azure operations.
PHPLaravelTwill CMSAWSAzure
Responsibilities & contributions
Responsibilities
Built and updated application features using Laravel and Twill CMS.
Maintained multiple client applications, investigated bugs and supported ongoing feature delivery and reliability.
Handled application configuration, database connectivity and production troubleshooting across AWS and Azure environments.
Worked with a distributed team to release updates, resolve operational issues and document application and infrastructure needs.
—
Turing.com
Software Engineer
Remote
Remote software engineering engagement. Specific responsibilities, technologies and accomplishments were not detailed in the supplied summary.
—
Dinerr
Full Stack Developer
Full-stack delivery covering integrations, architecture and application operations.
Responsibilities & contributions
Responsibilities
Built and managed API integrations, application architecture, deployments and servers.
—
Peexoo Technologies
Back End Developer
Laravel REST API development for a photography SaaS platform, including image-recognition features and operational monitoring.
PHPLaravelREST APIsAWS RekognitionAWS CloudWatch
Responsibilities & contributions
Responsibilities
Developed and maintained Laravel REST APIs for the platform.
Implemented server monitoring and logging using AWS CloudWatch.
Improved database performance and reliability; no quantified performance results were supplied.
Documented contributions
Built Findmyface and Lookalike features using Laravel and AWS Rekognition.
—
nextpayday.ng
Full Stack Developer
Web application development and ongoing maintenance of the existing system.
Responsibilities & contributions
Responsibilities
Built and managed the web application and maintained the existing system.
—
GeroCare Solutions Ltd
Full Stack Developer
Full-stack development role. Responsibilities and technologies were not detailed in the supplied summary.
—
Olotu Square
Full Stack Developer
Full-stack development role. Responsibilities and technologies were not detailed in the supplied summary.
—
HostNowNow Limited
Computer Programmer
Computer programming role. Responsibilities and technologies were not detailed in the supplied summary.
Additional contract experience
Verified in the supplied professional summary. Dates are awaiting confirmation and are not placed in the dated timeline.
Dates not suppliedContract engagement
Maribal
Software Engineer
Laravel business applications, legacy-system support, automated testing and deployment workflows.
Translated product requirements into working features and maintained legacy applications.
Created test factories and seeders, and wrote unit and integration tests.
Set up Bitbucket Pipelines for testing and deployments.
Collaborated on application documentation and led project delivery when needed.
Education & professional development
Self-taught software engineer with ongoing practical development in web engineering, cloud infrastructure, testing and automation.
Working language: English.
Technical problem solving / Inspectable work
Boss Battles Defeated
Less lore. More “how did you fix it?”
Professional examples draw on the supplied career summary. Independent portfolio work is labeled separately. Each note distinguishes documented delivery from details still to be written up.
Professional work / AREA 17 Care program
Keep the application moving. Keep production steady.
Client applications needed ongoing feature delivery, bug investigation and operational support across AWS and Azure.
PHPLaravelTwill CMSAWSAzure
Read the engineering notes
Problem
Client applications needed ongoing feature delivery, bug investigation and operational support across AWS and Azure.
Constraints
Multiple maintained applications and a distributed team. Client-specific systems and incident details are intentionally omitted.
Technical approach
Delivered Laravel and Twill CMS updates, investigated application configuration and database connectivity, supported deployments and documented operational needs with the team.
Outcome
Maintained client applications and supported releases and issue resolution. No uptime, incident-resolution or performance figures were supplied.
Engineering takeaway
Detailed incident lessons have not been supplied; this overview stays within the documented role scope.
A photography SaaS platform needed REST APIs and image-recognition functionality.
PHPLaravelREST APIsAWS RekognitionCloudWatch
Read the engineering notes
Problem
A photography SaaS platform needed REST APIs and image-recognition functionality.
Constraints
The supplied summary describes the work at feature level; no customer data, private architecture or measured results are disclosed.
Technical approach
Developed Laravel REST APIs and built Findmyface and Lookalike using AWS Rekognition. Added CloudWatch monitoring and logging, alongside database performance and reliability work.
Outcome
Findmyface and Lookalike were built, and monitoring/logging were implemented. Accuracy, latency and database improvement figures were not supplied.
Engineering takeaway
Implementation tradeoffs and personal lessons need a fuller case-study account; none are inferred here.
Laravel business applications needed feature delivery, legacy support, automated tests and deployment workflows.
Constraints
Contract dates and project-specific details are not supplied. No client identities or private implementation details are disclosed.
Technical approach
Created test factories and seeders, wrote unit and integration tests, and set up Bitbucket Pipelines for testing and deployments. Supported documentation and project delivery.
Outcome
Testing and deployment pipelines were set up, with application features and legacy systems maintained. Coverage and deployment-frequency metrics were not supplied.
Engineering takeaway
A detailed account of tradeoffs and lessons is still to be documented by the creator.
A short browser game needs consistent movement and round timing across different screens and refresh rates.
TypeScriptCanvas 2DReactPage Visibility API
Read the engineering notes
Problem
A short browser game needs consistent movement and round timing across different screens and refresh rates.
Constraints
Thirty-second rounds, three lives, narrow touch screens, keyboard controls and no heavyweight game engine.
Technical approach
Separate the simulation from canvas rendering. Advance it with elapsed time, clamp movement to the playfield and pause the round when the page is hidden. Keep scoring and collision rules testable without rendering.
Outcome
A playable game with keyboard and touch input, life loss, power-ups, pause/restart and local score sharing. Engine and browser tests exercise these behaviors; no player-scale or production metrics are claimed.
Engineering takeaway
A small deterministic simulation makes timing and collision behavior easier to inspect than logic embedded in a render loop.
A media gallery should show real channel content without loading eleven third-party players on arrival.
Next.jsTypeScriptYouTube Data APIServer-side caching
Read the engineering notes
Problem
A media gallery should show real channel content without loading eleven third-party players on arrival.
Constraints
No public API credentials, no invented metadata, vertical Shorts, and optional server-side API integration.
Technical approach
Verify curated IDs against the official channel, cache metadata server-side and render optimized posters. Mount a privacy-enhanced iframe only after a visitor chooses a video; retain an external link for restricted playback.
Outcome
Eleven verified uploads, responsive filtering, click-to-load embeds and a curated fallback. Real featured-video playback and automated player loading were checked locally. The optional API path was tested with mocked responses, not a live credential.
Engineering takeaway
Keep content retrieval separate from playback, and make a provider outage survivable with a verified snapshot.
A competitive gaming platform, with a built web application and deployment workflows prepared for release.
PHPAWS LightsailCaddyMySQLSESS3
Build notes & engineering challenge
Current build direction
Built the web application and deployment workflows. Configured PHP on AWS Lightsail with Caddy, MySQL, queue workers, scheduled tasks, SES email and S3 backups. Implemented responsive interfaces and privacy controls.
Engineering challenge
Coordinating application delivery with server configuration, background processing, scheduled tasks, transactional email and backups.
Current outcome
Web application built and release preparation implemented; updates verified through automated checks and browser review. Public availability and usage metrics have not been verified here.
Concept art illustrates the direction; it is not a product screenshot. These are independent experiments, not completed client engagements. Verified implementation stacks and demos will be added when available.
Got a good problem?
Let’s make something real
I do any work. Especially the interesting kind.Your next side quest starts here ↗