I fix the things that only break in production.

Years of accumulated decisions, real users, and features still landing every month. Custom in-house frameworks, Laravel platforms in daily use, integrations that have to stay in sync with someone else's software.

Selected work

3 of 10

Live personnel location platform

Industrial operations · client system

Two sources feeding one map: reference data out of Oracle, positions from a third-party location service. Positions lived only in cache — because when a tag stops reporting, last known location is the thing you need most.

Reference data flows from Oracle's PL/SQL packages through an OCI8 connection class to the map. Positions flow from a third-party location service into Redis, which also feeds the map. Positions are never written back to Oracle, and the Laravel database layer is not in this path. Laravel DB layer not in this path Oracle PL/SQL packages sites · employees · zones OCI8 connection class no ORM positions never written back Location service third party broadcasts Redis positions, only here no TTL Map one marker per tag live, or last known Reference data flows from Oracle's PL/SQL packages through an OCI8 connection class to the map. Positions flow from a third-party location service into Redis, which also feeds the map. Positions are never written back to Oracle, and the Laravel database layer is not in this path. Laravel DB layer not in this path Oracle PL/SQL packages sites · employees · zones Location service third party broadcasts positions never written back OCI8 connection class no ORM Redis positions, only here no TTL Map one marker per tag live, or last known
The cache has no expiry — a tag that stops reporting still shows where it was last seen.
Laravel Oracle OCI8 Docker Redis Leaflet JavaScript
Read the full case study

Syncware

Attorney–client communication platform Legal software · via Syncware Technologies

Three features inside an existing product: real-time messaging, Zoom meetings created on demand, and a scheduler where attorneys set their own availability. Two people in two timezones, and both have to see the right time.

Scheduler screen titled Set your availability, listing time slots for each day of the week: Monday 9:00am to 1:00pm and 2:00pm to 5:00pm, Tuesday and Thursday 11:00am to 5:00pm, Wednesday 9:00am to 5:00pm, and Friday to Sunday unavailable. Each day has an Add Slot button.
An attorney's weekly availability, as set in the scheduler.
Laravel Pusher Zoom API MySQL JavaScript
Read the full case study

Launchpad

Event platform · nonprofit · 2021–22

Inherited a platform where the site and Salesforce disagreed about who people were. Rebuilt the intake path so new records couldn't drift, then reconciled the existing ones — one user at a time, at login.

How one user was matched to one Salesforce contact An unreconciled user logs in and agrees to sync. The first tier searches Salesforce by email across every candidate email field, which is a strong match. If no email matches, a weaker second tier falls back to first name, last name and address together — this is where the accepted risk sits, because two people at one address sharing a full name would match. Whatever is found is merged through Salesforce's native merge, with the most recent value winning on conflicting fields, leaving one contact linked to the Laravel account with the site's missing data filled in. Unreconciled user logs in and agrees to sync 1 · Search by email across every candidate email field strong match match no email match 2 · Fall back to name and address first name, last name, address together weaker evidence — accepted risk Merge the duplicates Salesforce native merge · most recent value wins One contact, linked to the account missing site data filled from it
A merge cannot be undone. The dashed tier is where that risk sits.
Laravel Livewire Alpine.js Tailwind MySQL Salesforce FormAssembly Authorize.Net
Read the full case study

How I work

Back end

PHP, Laravel, MySQL, Oracle over OCI8, Redis. Integrations with Salesforce, Authorize.Net, Zoom, Pusher and Stripe.

Front end

JavaScript, Livewire, Alpine.js, Vue.js, jQuery, Tailwind CSS, Leaflet.

Infrastructure

Docker, Oracle Linux, Apache, Git.

Inherited code

Reading undocumented systems, working inside in-house frameworks, and writing the documentation that wasn't there. Most of my work is in codebases I didn't start.

What clients say

Osei is a great front end developer. We gave him a variety of tasks and he completed every one of them successfully. Great communication throughout.

Eric Mason — CTO, Equisolve

He was able to fix my issues quickly and accurately and exceeded my expectations in every regard. — Gary Berger, Jitseasy

He had a tremendous attention to detail and provided work that my client was happy with. — Markus Gray, Syncware Technologies

He carefully planned the transition, kept us informed every step of the way, and completed the migration without a hitch. — Kristi Zaha, Orthopedic Spine & Sports Therapy

Osei has an outstanding commitment to delivering high-quality work from the very beginning. — Josh Torres, Omnia Digital

Get in touch

Available for contract — Oct 2026

osiqua@gmail.com
Download résumé (PDF) (opens in a new tab)

Earlier projects and smaller builds are in the archive.